Metrics
Affected Vendors & Products
Mon, 15 Jun 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* cpe:2.3:a:openssl:openssl:4.0.0:-:*:*:*:*:*:* |
Thu, 11 Jun 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-347 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Wed, 10 Jun 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Wed, 10 Jun 2026 08:30:00 +0000
Wed, 10 Jun 2026 08:15:00 +0000
Tue, 09 Jun 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openssl
Openssl openssl |
|
| Vendors & Products |
Openssl
Openssl openssl |
Tue, 09 Jun 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys | |
| Weaknesses | CWE-354 | |
| References |
|
|
Status: PUBLISHED
Assigner: openssl
Published:
Updated: 2026-06-10T16:02:19.675Z
Reserved: 2026-03-26T09:29:36.013Z
Link: CVE-2026-34181
Updated: 2026-06-10T16:00:39.916Z
Status : Analyzed
Published: 2026-06-09T17:17:04.740
Modified: 2026-06-15T18:13:13.673
Link: CVE-2026-34181
OpenCVE Enrichment
Updated: 2026-06-11T02:00:16Z