CVE-2025-25199 json
BCryptGenerateSymmetricKey memory leak
published 2025-02-12 20 mo ago modified 2026-06-17 4 mo ago also GHSA-29c6-3hcj-89cf , GO-2025-3461 , EUVD-2025-4085
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/microsoft/go-crypto-winnative 0.0.0-20250211154640-f49c8e1379ea
- govulncheck-vulndb openSUSE Tumbleweed 0.0.20250312T181707-1.1
opensuse advisories openSUSE-SU-2025:14889-1
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 20 mo ago
Exploit prediction
1.44% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/microsoft/go-crypto-winnative | <0.0.0-20250211154640-f49c8e1379ea |
0.0.0-20250211154640-f49c8e1379ea |
Affected products
- microsoft go-crypto-winnative
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
References
Sources
- CVE List CVE-2025-25199
- GitHub Advisory GHSA-29c6-3hcj-89cf
- NVD CVE-2025-25199
- OSV GO-2025-3461
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.