CVE-2026-74892General(jahlives / openssl_encrypt)

LOWCVSS 8.7 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

openssl_encrypt versions before 1.4.0 contain a hardcoded default secret key in the standalone telemetry server configuration that is used for API key hashing. Attackers who know this default value can predict or forge API key hashes to compromise telemetry API authentication.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-798

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • openssl_encrypt

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • General: 1 classified signal
  • 1 total mentions across 1 day

Affected systems

Vendors
Products
openssl_encrypt

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-08-17: 1Technical Details · 2026-08-17: 108-17
Signal classification1 categories
General
1100.0%
Referenced assets1 URL
By indicator
Full discourse1 post
  • Vulmon Vulnerability Feed@VulmonFeeds
    General

    CVE-2026-74892 Hardcoded Secret Key in openssl_encrypt Telemetry Server Exposes API Authentication https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-74892

    Post summary

    The post lists CVE-2026-74892, noting a hardcoded secret key in the telemetry server that exposes API authentication, but provides no further details or concrete evidence of exploitation.

    00000138
    4.1K followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appjahlivesopenssl_encrypt-python-

Explore more