What is GHSA-4FCV-W3QC-PPGG?

GHSA-4FCV-W3QC-PPGG is a medium-severity use after free vulnerability in openssl (rust), affecting versions >= 0.10.39, < 0.10.72. It is fixed in 0.10.72. Memory is accessed after it has been freed, leading to undefined behavior in native code.

Which versions of openssl are affected by GHSA-4FCV-W3QC-PPGG?

openssl (rust) versions >= 0.10.39, < 0.10.72 is affected.

Is there a fix for GHSA-4FCV-W3QC-PPGG?

Yes. GHSA-4FCV-W3QC-PPGG is fixed in 0.10.72. Upgrade to this version or later.

Is GHSA-4FCV-W3QC-PPGG exploitable, and should I be worried?

Whether GHSA-4FCV-W3QC-PPGG is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-4FCV-W3QC-PPGG is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-4FCV-W3QC-PPGG in openssl

Q: Which versions of openssl are affected by GHSA-4FCV-W3QC-PPGG?

openssl (rust) versions >= 0.10.39, < 0.10.72 is affected.

Q: Is there a fix for GHSA-4FCV-W3QC-PPGG?

Yes. GHSA-4FCV-W3QC-PPGG is fixed in 0.10.72. Upgrade to this version or later.

Q: Is GHSA-4FCV-W3QC-PPGG exploitable, and should I be worried?

Whether GHSA-4FCV-W3QC-PPGG is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-4FCV-W3QC-PPGG is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-4FCV-W3QC-PPGG?

Upgrade openssl to 0.10.72 or later.

Summary

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

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.

Impact

Memory is accessed after it has been freed, leading to undefined behavior in native code. Typical impact: memory corruption, crash, or potential code execution.

Affected versions

openssl (>= 0.10.39, < 0.10.72)

Security releases

openssl → 0.10.72 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade openssl to 0.10.72 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-4FCV-W3QC-PPGG? GHSA-4FCV-W3QC-PPGG is a medium-severity use after free vulnerability in openssl (rust), affecting versions >= 0.10.39, < 0.10.72. It is fixed in 0.10.72. Memory is accessed after it has been freed, leading to undefined behavior in native code.
Which versions of openssl are affected by GHSA-4FCV-W3QC-PPGG? openssl (rust) versions >= 0.10.39, < 0.10.72 is affected.
Is there a fix for GHSA-4FCV-W3QC-PPGG? Yes. GHSA-4FCV-W3QC-PPGG is fixed in 0.10.72. Upgrade to this version or later.
Is GHSA-4FCV-W3QC-PPGG exploitable, and should I be worried? Whether GHSA-4FCV-W3QC-PPGG is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-4FCV-W3QC-PPGG is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-4FCV-W3QC-PPGG? Upgrade openssl to 0.10.72 or later.

Other vulnerabilities in openssl

CVE-IDSeverityPackage summary

CVE-2026-45784Mediumopenssl: rust-openssl: Potential out-of-bounds write in `CipherCtxRef::cipher_update_inplace` for AES-KW-PAD ciphers CVE-2026-44662Mediumopenssl: rust-openssl vulnerable to heap buffer overflow when encrypting with AES key-wrap-with-padding CVE-2026-42327Highopenssl: rust-openssl has undefined behavior in X509Ref::ocsp_responders for certificates with non-UTF-8 OCSP URLs CVE-2026-41676Highopenssl: rust-openssl: Deriver::derive and PkeyCtxRef::derive can overflow short buffers on OpenSSL 1.1.1 CVE-2026-41677Lowopenssl: rust-opennssl has an Out-of-bounds read in PEM password callback when returning an oversized length