CVE-2025-25199
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.
Scoring
- Severity
- HIGH
- CVSS base score
- 7.5
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS probability
- 1.44%
- CWE
- CWE-401
- Published
- 2025-02-12
- Last modified
- 2026-03-12
Affected products
- microsoft go-crypto-winnative
- microsoft go-crypto-winnative
- microsoft go-crypto-winnative
Weakness type
Related vulnerabilities
- CVE-2026-69781 — Windows DHCP Client Denial of Service Vulnerability
- CVE-2026-69809 — Windows Active Directory Domain Services Denial of Service Vulnerability
- CVE-2026-69497 — Windows DHCP Server Denial of Service Vulnerability
- CVE-2026-69405 — Windows DHCP Server Denial of Service Vulnerability
- CVE-2026-70065 — Windows DHCP Server Denial of Service Vulnerability
- CVE-2026-69588 — Windows TCP/IP Denial of Service Vulnerability
- CVE-2026-16028 — Protocol::HTTP2 versions before 1.14 for Perl allow memory exhaustion via closed streams that stream_state never removes from the connection stream table
- CVE-2026-18313 — rpcapd memory leak in libpcap before 1.10.7