CVE-2026-74894openssl_encrypt before 1.4.0 Authentication Bypass via Bearer Token
Updated under an hour ago ()
Does this affect you?
It affects jahlives openssl_encrypt. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 9.8 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- CWE-287
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- VulnCheck
- NVD analysis
- Analyzed
- Record last updated
- Oct 1, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
jahlives openssl_encrypt jahlives:openssl_encrypt (from the name) | before 1.4.0; 1.4.0 not affected | CNA record |
jahlives openssl_encrypt jahlives:openssl_encrypt | before 1.4.0 | NVD |
References
- https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-4g2c-wpgj-49w8vendor-advisory, mitigation
- https://www.vulncheck.com/advisories/openssl-encrypt-before-authentication-bypass-via-bearer-tokenthird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.