How severe is GHSA-4fcv-w3qc-ppgg?

No CVSS score has been assigned to GHSA-4fcv-w3qc-ppgg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4fcv-w3qc-ppgg?

GHSA-4fcv-w3qc-ppgg affects the following packages: openssl (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-4fcv-w3qc-ppgg?

Update openssl to 0.10.72 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4fcv-w3qc-ppgg is resolved across your whole dependency graph.

How do I detect GHSA-4fcv-w3qc-ppgg in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4fcv-w3qc-ppgg 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-4fcv-w3qc-ppgg?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4fcv-w3qc-ppgg can be triaged on real exposure rather than presence alone.

Is GHSA-4fcv-w3qc-ppgg actively exploited in the wild?

No public exploit code has been indexed for GHSA-4fcv-w3qc-ppgg 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-4fcv-w3qc-ppgg published, and has it been updated?

GHSA-4fcv-w3qc-ppgg was published on April 4, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-4fcv-w3qc-ppgg — openssl

Fix: sfackler/rust-openssl#2390

GHSA-4fcv-w3qc-ppgg is a security vulnerability in openssl. A fix is available for openssl — see the affected versions and patch details below.

rust-openssl Use-After-Free in `Md::fetch` and `Cipher::fetch`

Also known asRUSTSEC-2025-0022

Published

Apr 4, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀openssl

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

Description

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`openssl`	≥ 0.10.39&&< 0.10.72	0.10.72`cargo update -p openssl --precise 0.10.72`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openssl to 0.10.72 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4fcv-w3qc-ppgg 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4fcv-w3qc-ppgg can be triaged on real exposure rather than presence alone.

Tailored to GHSA-4fcv-w3qc-ppgg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

When a `Some(...)` value was passed to the `properties` argument of either of these functions, a use-after-free would result. In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to `CString::drop`'s behavior). The maintainers thank [quitbug](https://github.com/quitbug/) for reporting this vulnerability to us.

O3 Security · Impact-Aware SCA

Is GHSA-4fcv-w3qc-ppgg in your dependencies?

O3 Security finds GHSA-4fcv-w3qc-ppgg across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works