package pkcs12: Authentication bypass in Decode functions
Published 17 Aug 2026 · Updated 10 Sept 2026
Is your project on an affected software.sslmate.com/src/go-pkcs12?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=0.6.0 <0.7.2
- Fixed in
- 0.7.2
go get software.sslmate.com/src/go-pkcs12@v0.7.2Details
Decode, DecodeChain, DecodeTrustStore, and ToPEM can incorrectly accept PKCS#12 files which were encoded with the wrong password, due to a failure to reject excessively-short PBMAC1 keys. Users who decode PKCS#12 files from untrusted sources and rely on the password for authentication can be tricked into accepting malicious PKCS#12 files. Users who only decode PKCS#12 files from trusted sources are not affected.
Thanks to Pavol Žáčik (Red Hat) and Alex Gaynor (Anthropic) for finding and reporting the same issue in OpenSSL (CVE-2026-34181).
Is GHSA-mpwr-8vm7-h73f in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected software.sslmate.com/src/go-pkcs12, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.