CVE-2026-34181
HIGHDescription
Issue Summary: The PKCS#12 file processing fails to perform sufficient input validation for files that use Password-Based Message Authentication Code 1 (PBMAC1) integrity mechanism allowing a certificate and private key forgery. Impact Summary: An attacker impersonating a user can cause a service reading PKCS#12 files to accept forged certificates and private keys with a 1 in 256 probability. If a service accepting PKCS#12 files is using passwords for authenticating the received files, the attacker can create unencrypted PKCS#12 files that use PBMAC1 authentication that specifies an HMAC key of only one byte, allowing them to craft a file that will be accepted with a 1 in 256 probability. That would then cause the service to accept a certificate and private key controlled by the attacker. The FIPS modules are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 14% of all known CVEs.
References
Related Vulnerabilities
Other CWE-354 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-48795 | Medium | 5.9 | 93% | - | Fix |
| CVE-2019-1166 | Medium | 5.9 | 68% | - | - |
| CVE-2024-3596 | Critical | 9.0 | 15% | - | Fix |
| CVE-2020-26141 | Medium | 6.5 | 3.1% | - | Fix |
| CVE-2020-25862 | High | 7.5 | 2.4% | - | Fix |
| CVE-2020-8838 | Medium | 6.4 | 1.6% | - | - |
Common questions
How do I fix CVE-2026-34181?
Published advisories record a fix for 30 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-34181 being actively exploited?
Not that we know of. CVE-2026-34181 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.24% is the estimated probability that it will be exploited in the next 30 days. That is higher than 14% of all scored CVEs.
How severe is CVE-2026-34181?
CVE-2026-34181 has a CVSS v3 base score of 7.4, rated important. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-34181 affect?
Published advisories record a fix for openssl (Debian), openssl (Red Hat / RHEL), openssl (Rocky), openssl-debuginfo (Rocky), and 26 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-34181
Markdown
[](https://tridentstack.com/cve/CVE-2026-34181)HTML
<a href="https://tridentstack.com/cve/CVE-2026-34181"><img src="https://tridentstack.com/cve/badge/CVE-2026-34181.svg" alt="CVE-2026-34181"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-23.