CVE-2025-25199
go-crypto-winnative Go crypto backend for Windows using …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/microsoft/go-crypto-winnative/commit/f49c8e1379ea4b147d5bff1b3be5b0ff45792e41
- github.com/microsoft/go-crypto-winnative/security/advisories/GHSA-29c6-3hcj-89cf
- nvd.nist.gov/vuln/detail/CVE-2025-25199
- github.com/advisories/GHSA-29c6-3hcj-89cf
- nvd.nist.gov/vuln/detail/CVE-2025-25199
- cve.org/CVERecord?id=CVE-2025-25199
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.