How severe is GHSA-mpwr-8vm7-h73f?

No CVSS score has been assigned to GHSA-mpwr-8vm7-h73f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mpwr-8vm7-h73f?

GHSA-mpwr-8vm7-h73f affects the following packages: software.sslmate.com/src/go-pkcs12 (Go). Ecosystems affected: Go.

How do I fix GHSA-mpwr-8vm7-h73f?

Update software.sslmate.com/src/go-pkcs12 to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mpwr-8vm7-h73f is resolved across your whole dependency graph.

How do I detect GHSA-mpwr-8vm7-h73f in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for software.sslmate.com/src/go-pkcs12. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-mpwr-8vm7-h73f if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-mpwr-8vm7-h73f?

O3 pinpoints whether GHSA-mpwr-8vm7-h73f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mpwr-8vm7-h73f actively exploited in the wild?

No public exploit code has been indexed for GHSA-mpwr-8vm7-h73f yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-mpwr-8vm7-h73f published, and has it been updated?

GHSA-mpwr-8vm7-h73f was published on August 17, 2026 and was last updated on August 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-mpwr-8vm7-h73f

GHSA-mpwr-8vm7-h73f is a security vulnerability in software.sslmate.com/src/go-pkcs12. O3 Security confirms whether GHSA-mpwr-8vm7-h73f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

package pkcs12: Authentication bypass in Decode functions

Also known asGO-2026-5052

Published

Aug 17, 2026

Updated

Aug 17, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 17, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹software.sslmate.com/src/go-pkcs12

Real-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

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).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`software.sslmate.com/src/go-pkcs12`	≥ 0.6.0&&< 0.7.2	0.7.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for software.sslmate.com/src/go-pkcs12. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update software.sslmate.com/src/go-pkcs12 to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mpwr-8vm7-h73f 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.
How O3 protects you
O3 pinpoints whether GHSA-mpwr-8vm7-h73f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mpwr-8vm7-h73f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`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](https://openssl-library.org/news/vulnerabilit

O3 Security · Impact-Aware SCA

Is GHSA-mpwr-8vm7-h73f in your dependencies?

O3 detects GHSA-mpwr-8vm7-h73f across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works