CVE-2026-74894
Jahlives OpenSSL Encrypt authentication bypass
- Published17 Aug 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-74894 being actively exploited?
CVE-2026-74894 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.66%.
How severe is CVE-2026-74894?
CVE-2026-74894 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.66% probability of exploitation.
Which products are affected by CVE-2026-74894?
Affected products include Jahlives OpenSSL Encrypt.
How do I fix CVE-2026-74894?
Upgrade affected software to a fixed version, for example Jahlives OpenSSL Encrypt 1.4.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-74894 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.