Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-74894 – Authentication Bypass – openssl_encrypt (jahlives) before 1.4.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-74894 is a critical authentication bypass vulnerability (CWE-287: Improper Authentication) in the openssl_encrypt Python package maintained by jahlives, distributed via PyPI as openssl-encrypt. The flaw resides in the package’s verify_api_token function, which accepts any non-empty Bearer token string without performing actual validation, allowing an unauthenticated network attacker to impersonate legitimate API clients. The issue carries a CVSS v3.1 base score of 9.8 (Critical) and a CVSS v4.0 base score of 9.3 (Critical).

Technical details

  • Root cause: The verify_api_token function used to authenticate requests to the package’s key server/API components fails to validate the supplied Bearer token — it treats any non-empty string as a valid credential.
  • Trigger conditions: An attacker simply needs to send an HTTP request to an exposed openssl_encrypt API endpoint with an Authorization: Bearer <arbitrary-non-empty-string> header; no legitimate credentials, prior session, or user interaction are required.
  • Attack vector: Network — the vulnerability is remotely exploitable without authentication or privileges.
  • Impact: Successful exploitation allows an attacker to:
    • Upload arbitrary public keys to the key server as if acting on behalf of a legitimate user
    • Enumerate all stored keys in the system
    • Revoke keys belonging to other users, resulting in denial of service or disruption of cryptographic operations relying on those keys
    • Full loss of confidentiality, integrity, and availability for the affected key management functionality

Affected software

  • Product: openssl_encrypt (PyPI package openssl-encrypt), maintained by jahlives
  • Affected versions: All versions prior to 1.4.0
  • Fixed version: 1.4.0 and later

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 Base Score: 9.3 (Critical) — 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

Mitigation and recommended actions

  • Immediate: Upgrade openssl_encrypt to version 1.4.0 or later, which enforces proper Bearer token validation in verify_api_token.
  • If patching is not immediately possible:
    • Restrict network exposure of any openssl_encrypt key server/API components to trusted internal networks only; do not expose these endpoints directly to the internet.
    • Place the affected service behind an authenticating reverse proxy or API gateway that independently validates tokens before requests reach the vulnerable service.
    • Monitor API logs for unexpected key upload, enumeration, or revocation activity as a potential indicator of exploitation.
    • Rotate and re-validate any keys managed through the affected service after patching, since key integrity cannot be assured while the vulnerability was exploitable.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge