Skip to main content
Mallory
Medium

Out-of-bounds read in OpenSSL X509_VERIFY_PARAM_set1_email()

IdentifiersCVE-2026-42771CWE-125· Out-of-bounds Read

CVE-2026-42771 is a low-severity out-of-bounds read in OpenSSL's email address validation logic used by X509_VERIFY_PARAM_set1_email() and X509_VERIFY_PARAM_add1_email(). An internal helper function invoked by these APIs uses an incorrect length when validating the local part of an email address. As a result, the 64-octet limit for the local part may not be enforced correctly, and processing a crafted email address can cause an out-of-bounds read. The issue is reachable in application flows that validate email addresses through these APIs, including S/MIME message validation when a crafted From: address is supplied in an email message. OpenSSL states the affected 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 trigger an out-of-bounds read that most likely results in process instability, a crash, and denial of service. According to the provided advisory, the issue does not directly exfiltrate the data read to the attacker.

Mitigation

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

No specific vendor workaround is provided in the supplied content. As an interim measure, reduce exposure by limiting or hardening application paths that perform S/MIME validation or otherwise pass untrusted email address data into X509_VERIFY_PARAM_set1_email() or X509_VERIFY_PARAM_add1_email(), and monitor for crashes triggered by malformed From: addresses.

Remediation

Patch, then assume compromise.

Upgrade OpenSSL to a vendor-fixed release. The provided context indicates fixes were issued as part of the 9 June 2026 OpenSSL security releases; organizations should deploy the patched version provided by OpenSSL or their downstream distributor for the affected branch.
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
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 activity

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