Skip to main content
VulnerabilityPublished Updated

CVE-2026-74894: jahlives openssl_encrypt · Improper Authentication

Affects jahlives openssl_encryptSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 1.4.0 as a priority.

Data as of 14 Nov 2026, 20:44 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% 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:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
jahlivesopenssl_encryptAffected
  • <1.4.0
Fixed in
  • 1.4.0

AI-suggested

If you cannot patch yet, restrict access to the affected component and consider additional access controls to mitigate exploitation risk.

Description

openssl_encrypt before 1.4.0 contains an authentication bypass vulnerability in the verify_api_token function that accepts any non-empty Bearer token string without validation. Attackers can upload arbitrary public keys, enumerate all keys, and revoke keys belonging to any user by providing any Bearer token in the Authorization header.

References

Community reviews

Loading reviews…