How severe is GHSA-29c6-3hcj-89cf?

GHSA-29c6-3hcj-89cf has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-29c6-3hcj-89cf?

GHSA-29c6-3hcj-89cf affects the following packages: github.com/microsoft/go-crypto-winnative (Go). Ecosystems affected: Go.

How do I fix GHSA-29c6-3hcj-89cf?

Update github.com/microsoft/go-crypto-winnative to 0.0.0-20250211154640-f49c8e1379ea or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-29c6-3hcj-89cf is resolved across your whole dependency graph.

How do I detect GHSA-29c6-3hcj-89cf in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/microsoft/go-crypto-winnative. 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-29c6-3hcj-89cf 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-29c6-3hcj-89cf?

O3 pinpoints whether GHSA-29c6-3hcj-89cf 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-29c6-3hcj-89cf actively exploited in the wild?

No public exploit code has been indexed for GHSA-29c6-3hcj-89cf 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.

What is the EPSS score for GHSA-29c6-3hcj-89cf?

GHSA-29c6-3hcj-89cf has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 66th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-29c6-3hcj-89cf published, and has it been updated?

GHSA-29c6-3hcj-89cf was published on February 12, 2025 and was last updated on March 3, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-29c6-3hcj-89cf

HIGH

go-crypto-winnative BCryptGenerateSymmetricKey memory leak

Also known asCVE-2025-25199GO-2025-3461

Published

Feb 12, 2025

Updated

Mar 3, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk66th percentile+0.25%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹github.com/microsoft/go-crypto-winnative

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

Description

Calls to cng.TLS1PRF don't release the key handle, producing a small memory leak every time.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/microsoft/go-crypto-winnative`	all versions	0.0.0-20250211154640-f49c8e1379ea

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/microsoft/go-crypto-winnative. 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 github.com/microsoft/go-crypto-winnative to 0.0.0-20250211154640-f49c8e1379ea or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-29c6-3hcj-89cf 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-29c6-3hcj-89cf 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-29c6-3hcj-89cf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Calls to `cng.TLS1PRF` don't release the key handle, producing a small memory leak every time.

O3 Security · Impact-Aware SCA

Is GHSA-29c6-3hcj-89cf in your dependencies?

O3 detects GHSA-29c6-3hcj-89cf across Go 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