CVE-2026-34181

Aliases:DEBIAN-CVE-2026-34181UBUNTU-CVE-2026-34181ALPINE-CVE-2026-34181CGA-2p6j-cvxh-gg7mCGA-5g4c-gpf6-xvxhCGA-6jgq-q8x4-jwm9CGA-mj3g-mrrh-cg33CGA-6mfm-7wxw-mxvqCGA-6xwr-94hq-793pCGA-7h5g-qr4p-wf23CGA-8fq7-p6jh-6g72CGA-chg2-cqqg-v49qCGA-gjf7-p6x7-hc8gCGA-gvv2-j8p7-vfh6CGA-r49g-mphp-66rmCGA-vv4q-xhx2-5wqqCGA-xj66-jrf4-4wpx
Advisory lineage Upstream: 0 Downstream: 12
Analyzed
Published: 09 Jun 2026, 16:03
Last modified:10 Jun 2026, 16:02

Vulnerability Summary

Overall Risk (default)
medium
30/100
CVSS Score
7.4 HIGH
v3.1 (cve.org)
EPSS Score
0.24% LOW
0% probability 0.00%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

09 Jun 2026, 16:03
Published
Vulnerability first disclosed
10 Jun 2026, 16:02
Last Modified
Vulnerability information updated

Description

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.

CVSS Metrics

  • v3.1•HIGH•Score: 7.4CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS Trends

Current EPSS score: 0.24%• Percentile: 15%

Techniques & Countermeasures

  • CWE-354•Improper Validation of Integrity Check Value

    The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.

Affected Systems

  • alpine•openssl

    ≥ 3.4.0, < 3.5.7-r0 | ≥ 3.4.0, < 3.5.7-r0 | ≥ 3.4.0, < 3.5.7-r0

  • chainguard•libcrypto3

    < 3.6.3-r0

  • chainguard•libcrypto3-2.34

    < 3.6.3-r0

  • chainguard•openssl

    < 3.6.3-r0

  • chainguard•openssl-provider-fips-3.4.0

    < 0

  • chainguard•openssl-provider-fips-3.4.0-dbg

    < 0

  • chainguard•openssl-provider-fips-3.6.0

    < 0

  • chainguard•openssl-provider-fips-3.6.0-dbg

    < 0

  • wolfi•libcrypto3

    < 3.6.3-r0

  • wolfi•openssl

    < 3.6.3-r0

  • debian•openssl

    < 3.5.6-1~deb13u2 | < 3.6.3-1

  • ubuntu•edk2

    all | all

  • ubuntu•edk2-hwe

    all

  • ubuntu•nodejs

    all

  • ubuntu•openssl

    < 3.5.3-1ubuntu3.4 | < 3.5.5-1ubuntu3.2

  • openssl•openssl

    ≥ 4.0.0, < 4.0.1 | ≥ 3.4.0, < 3.4.6 | ≥ 3.5.0, < 3.5.7 | ≥ 3.6.0, < 3.6.3 | 4.0.0

References (16)