CVE-2025-25199 is a high-severity (CVSS 7.5) CWE-401 vulnerability in github.com/microsoft/go-crypto-winnative. A fix is available for github.com/microsoft/go-crypto-winnative — see the affected versions and patch details below.
BCryptGenerateSymmetricKey memory leak
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-25199.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/microsoft/go-crypto-winnativeReal-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
go-crypto-winnative Go crypto backend for Windows using Cryptography API: Next Generation (CNG). Prior to commit f49c8e1379ea4b147d5bff1b3be5b0ff45792e41, calls to cng.TLS1PRF don't release the key handle, producing a small memory leak every time. Commit f49c8e1379ea4b147d5bff1b3be5b0ff45792e41 contains a fix for the issue. The fix is included in versions 1.23.6-2 and 1.22.12-2 of the Microsoft build of go, as well as in the pseudoversion 0.0.0-20250211154640-f49c8e1379ea of the github.com/microsoft/go-crypto-winnative Go package.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/microsoft/go-crypto-winnative | all versions | 0.0.0-20250211154640-f49c8e1379eago get github.com/microsoft/go-crypto-winnative@v0.0.0-20250211154640-f49c8e1379ea |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/microsoft/go-crypto-winnative, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2025-25199 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.
Frequently Asked Questions
Is CVE-2025-25199 in your dependencies?
Find it across Go, including transitive dependencies.