dbcve.org
OpenSSLFramework / library

CVE-2026-34181

HIGH · 7.4 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 3.4.6 / 3.5.7 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenSSLFramework / library
Affected:>= 3.4.0, < 3.4.6>= 3.5.0, < 3.5.7>= 3.6.0, < 3.6.3= 4.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.4.6 / 3.5.7 / 3.6.3 or later
Fixed in 3.4.63.5.73.6.3
Vendor patch github.com →
Recommended fix High confidence

OpenSSL 3.4.6+ (for 3.4.x users), 3.5.7+ (for 3.5.x users), 3.6.3+ (for 3.6.x users), or 4.0.1+ (for 4.0.0 users)

  1. 1. Identify the currently installed OpenSSL version by running 'openssl version' or checking your system's package manager
  2. 2. Determine which branch of OpenSSL you are using (3.4.x, 3.5.x, 3.6.x, or 4.0.0) from the version output
  3. 3. For OpenSSL 3.4.x: upgrade to version 3.4.6 or later (e.g., apt-get install libssl3.4.6, yum update openssl, or rebuild from source)
  4. 4. For OpenSSL 3.5.x: upgrade to version 3.5.7 or later
  5. 5. For OpenSSL 3.6.x: upgrade to version 3.6.3 or later
  6. 6. For OpenSSL 4.0.0: upgrade to version 4.0.1 or later when available
  7. 7. Verify the upgrade was successful by running 'openssl version' and confirming the new version number
  8. 8. Test any PKCS#12 file processing functionality in your applications to ensure normal operation
Caveat OpenSSL minor version upgrades are typically backward compatible; however, review the release notes for any deprecation notices or behavioral changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34181 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34181 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data