Skip to main content
Mallory
High

OpenSSL PKCS#12 PBMAC1 short HMAC key acceptance allows certificate and private key forgery

IdentifiersCVE-2026-34181CWE-20

CVE-2026-34181 is a low-severity input validation flaw in OpenSSL PKCS#12 file processing. When processing PKCS#12 files that use the Password-Based Message Authentication Code 1 (PBMAC1) integrity mechanism, OpenSSL fails to sufficiently validate the PBMAC1 parameters and accepts files specifying an HMAC key of only one byte. As a result, an attacker can craft an unencrypted PKCS#12 file authenticated with PBMAC1 such that integrity verification succeeds with a 1 in 256 probability, causing the receiving service to accept attacker-controlled certificate and private key material as valid. According to the provided advisory context, affected versions are OpenSSL 4.0.0 before 4.0.1, 3.6.0 before 3.6.3, 3.5.0 before 3.5.7, and 3.4.0 before 3.4.6. The vulnerable code is outside the OpenSSL FIPS module boundary, so FIPS modules are not affected.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause a service that imports or reads PKCS#12 files to accept a forged certificate and private key controlled by the attacker. This enables identity impersonation in workflows that rely on password-authenticated PKCS#12 bundles for certificate/key provisioning or import. The advisory states acceptance occurs with a 1 in 256 probability per crafted file, so repeated attempts may allow practical forgery against exposed services. The issue is described as low severity and does not affect OpenSSL FIPS modules.

Mitigation

If you can’t patch tonight, do this now.

No specific vendor workaround is provided in the supplied content. Practical exposure can be reduced by refusing unencrypted PKCS#12 files, disallowing or filtering PBMAC1-based PKCS#12 inputs where possible, enforcing stronger validation of PKCS#12 integrity parameters before import, and limiting acceptance of PKCS#12 bundles to trusted channels or authenticated users. Systems using OpenSSL FIPS modules are not affected by this specific issue.

Remediation

Patch, then assume compromise.

Upgrade OpenSSL to a fixed release: 4.0.1 or later, 3.6.3 or later, 3.5.7 or later, or 3.4.6 or later, as applicable to the deployed branch. Where OpenSSL is consumed through an operating system or vendor package, apply the corresponding downstream security update from the platform maintainer. Alpine 3.24.1 and other downstream advisories referenced in the content include fixes for this issue.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreebsdFreebsdapplication
OpenSSL Software FoundationOpensslapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.