CVE-2026-74892: jahlives openssl_encrypt · Use of Hard-coded Credentials
Affects jahlives openssl_encryptSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 1.4.0 soon.
Data as of 14 Nov 2026, 20:44 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade jahlives openssl_encrypt to 1.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| jahlivesopenssl_encrypt | Affected
| Fixed in
|
AI-suggested
Users should monitor the vendor's communications for an official fix or update to remove the hardcoded secret key. If you cannot patch yet, consider restricting access to the telemetry server and avoid using affected versions in sensitive environments.
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.