OpenSSL · OpenSSL · published 2026-06-09

CVE-2026-34181PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys

Routine No exploitation evidence; EPSS 0.4%.

CVE-2026-34181 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 32% of all CVEs. This OpenSSL vulnerability: CVSS 7.4 (v3.1). Fixed upstream in OpenSSL 4.0.1, 3.6.3, 3.5.7, 3.4.6 (+3 more). Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in OpenSSL 4.0.1, 3.6.3, 3.5.7, 3.4.6, 3.0.21, 1.1.1zh, 1.0.2zq.

Patch events

  1. This monthSecurity release

    Crypto libraryOpenSSL

    OpenSSL security fixes: 18 CVEs

    Upgrade to 4.0.13.6.33.5.73.4.63.0.211.1.1zh1.0.2zq

    Why: CVE-2026-34182: EPSS 1.1% with high severity (CVSS 9.1).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (32th pct)FIRST EPSS v2026.06.15
CVSS base score7.4 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →