How severe is GHSA-2vhw-q7vh-7xv2?

No CVSS score has been assigned to GHSA-2vhw-q7vh-7xv2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2vhw-q7vh-7xv2?

GHSA-2vhw-q7vh-7xv2 affects the following packages: openssl-encrypt (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-2vhw-q7vh-7xv2?

Update openssl-encrypt to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2vhw-q7vh-7xv2 is resolved across your whole dependency graph.

How do I detect GHSA-2vhw-q7vh-7xv2 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl-encrypt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2vhw-q7vh-7xv2 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2vhw-q7vh-7xv2?

O3 pinpoints whether GHSA-2vhw-q7vh-7xv2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2vhw-q7vh-7xv2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2vhw-q7vh-7xv2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2vhw-q7vh-7xv2 published, and has it been updated?

GHSA-2vhw-q7vh-7xv2 was published on April 1, 2026 and was last updated on April 1, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-2vhw-q7vh-7xv2

openssl-encrypt's readiness endpoint leaks database error details to unauthenticated callers

Published

Apr 1, 2026

Updated

Apr 1, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐍openssl-encrypt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The /ready endpoint in openssl_encrypt_server/server.py at lines 159-175 catches database errors and returns the full exception string in the response.

Affected Code

except Exception as e:
    return {"status": "not_ready", "reason": str(e)}

Impact

Database exception messages can leak:

Database hostnames and IP addresses
Connection parameters and port numbers
Driver version information
Potentially database credentials if included in connection string errors

This information is available to unauthenticated callers.

Recommended Fix

Return a generic error message: {"status": "not_ready", "reason": "database unavailable"}
Log the full exception server-side for debugging

Fix

Fixed in commit 7aa8787 on branch releases/1.4.x — replaced str(e) with generic "database check failed" message; full exception logged server-side at WARNING level.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`openssl-encrypt`	all versions	1.4.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl-encrypt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openssl-encrypt to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2vhw-q7vh-7xv2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2vhw-q7vh-7xv2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2vhw-q7vh-7xv2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The `/ready` endpoint in `openssl_encrypt_server/server.py` at **lines 159-175** catches database errors and returns the full exception string in the response. ### Affected Code ```python except Exception as e: return {"status": "not_ready", "reason": str(e)} ``` ### Impact Database exception messages can leak: - Database hostnames and IP addresses - Connection parameters and port numbers - Driver version information - Potentially database credentials if included in connection string errors This information is available to unauthenticated callers. ### Recommended Fix -

O3 Security · Impact-Aware SCA

Is GHSA-2vhw-q7vh-7xv2 in your dependencies?

O3 detects GHSA-2vhw-q7vh-7xv2 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works