CVE-2026-74879: jahlives openssl_encrypt · Generation of Error Message Containing Sensitive Information
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 16 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% 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 16 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
If you cannot patch yet, restrict access to the /ready endpoint to trusted users or networks to prevent unauthenticated access. Avoid exposing detailed error messages to unauthenticated callers by implementing proper error handling and sanitization.
Description
A vulnerability in jahlives openssl_encrypt versions before 1.4.0 allows unauthenticated attackers to obtain sensitive information via error messages from the /ready endpoint. The endpoint returns full database exception strings that may include hostnames, IP addresses, connection parameters, and possibly credentials. This information disclosure can be triggered by causing database errors. The vulnerability has a high severity with a CVSS score of 8.7.