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

New CVE Detected

CVE-2026-74879 – Sensitive Information Disclosure – openssl_encrypt (PyPI) before 1.4.0

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

Summary

CVE-2026-74879 is a sensitive information disclosure vulnerability in the openssl_encrypt Python package (published by maintainer jahlives on PyPI). The package’s /ready readiness/health-check endpoint returns full, unfiltered database exception strings to unauthenticated callers, allowing remote attackers to harvest internal infrastructure details simply by triggering a backend database error. The issue is rated HIGH severity and is remotely exploitable without authentication or user interaction.

Technical details

  • Root cause: The /ready endpoint handler (in openssl_encrypt_server/server.py) wraps its database connectivity check in a broad exception handler that returns the raw exception text directly in the HTTP response, e.g. except Exception as e: return {"status": "not_ready", "reason": str(e)}.
  • Trigger conditions: Any condition that causes the backend database connection/query to fail (e.g., DB outage, network partition, misconfiguration, or an attacker-influenced connection state) will cause the exception string to be reflected back in the API response.
  • Attack vector: Network — the /ready endpoint requires no authentication and can be queried by any remote, unauthenticated actor.
  • Impact: Disclosure of sensitive backend information including database hostnames, IP addresses, connection parameters, port numbers, driver/version information, and potentially embedded database credentials contained in connection-string error messages. This information can materially aid follow-on attacks against backend infrastructure. The flaw affects confidentiality only; integrity and availability are not directly impacted.
  • Weakness classification: CWE-209 (Generation of Error Message Containing Sensitive Information) / CWE-201 (Insertion of Sensitive Information Into Sent Data), depending on advisory source.

Affected software

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

Severity

  • CVSS v3.1: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CVSS v4.0: 8.7 (HIGH) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade openssl_encrypt to version 1.4.0 or later, which returns a generic status message (e.g., {"status": "not_ready", "reason": "database unavailable"}) instead of the raw exception text.
  • If patching is not immediately possible:
    • Restrict network access to the /ready endpoint to trusted internal monitoring/orchestration systems only (e.g., via firewall rules, reverse-proxy ACLs, or service mesh policy), rather than exposing it publicly.
    • Place a reverse proxy or API gateway in front of the service to strip or sanitize error payloads before they reach external callers.
    • Monitor and rotate any database credentials that could have been exposed via connection-string error messages, and review logs for repeated probing of the /ready endpoint.

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge