CVE-2026-74894: openssl_encrypt before 1.4.0 Authentication Bypass via Bearer Token

Published Aug 17, 2026
·
Updated

opensslencrypt before 1.4.0 contains an authentication bypass vulnerability in the verifyapitoken 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.

Affected Software

1 affected component
OpenSSL openssl_encrypt<1.4.0

Event History

Aug 17, 2026
CVE Published
via MITRE·11:04 AM
Data Sourced
via MITRE·11:04 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:16 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-74894?

CVE-2026-74894 has a critical severity rating of 9.8.

2

What is the main issue with CVE-2026-74894?

CVE-2026-74894 allows for an authentication bypass due to the verify_api_token function's failure to validate non-empty Bearer tokens.

3

How do I fix CVE-2026-74894?

To mitigate CVE-2026-74894, upgrade to a version of openssl_encrypt that is 1.4.0 or later.

4

What are the potential impacts of CVE-2026-74894?

CVE-2026-74894 can lead to unauthorized access where attackers can upload and manage public keys of any user.

5

Who is affected by CVE-2026-74894?

Any user or application relying on openssl_encrypt versions before 1.4.0 is potentially affected by CVE-2026-74894.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203