Bug 2481895 (CVE-2026-42771) - CVE-2026-42771 openssl: Possible Out of Bounds Read in X509_VERIFY_PARAM_set1_email()
Summary: CVE-2026-42771 openssl: Possible Out of Bounds Read in X509_VERIFY_PARAM_set1...
Keywords:
Status: NEW
Alias: CVE-2026-42771
Deadline: 2026-07-10
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-27 14:21 UTC by OSIDB Bzimport
Modified: 2026-07-14 14:15 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-05-27 14:21:33 UTC
Possible Out of Bounds Read in X509_VERIFY_PARAM_set1_email()

Possible Out of Bounds Read in X509_VERIFY_PARAM_set1_email() (CVE-2026-42771)
Severity: Low

Issue summary: When the X509_VERIFY_PARAM_set1_email is called by an
application to validate a crafted e-mail address, such as during S/MIME
message validation, an out of bounds read can happen.

Impact summary: This out of bounds read will not directly exfiltrate
the data read to the attacker so the most likely result is a crash and
a Denial of Service.

An internal helper function called from X509_VERIFY_PARAM_[set|add]_email()
used a wrong length when validating the local part of an email address.
This could cause the 64 octet limit on the local part of an email address
to be not enforced, or cause an out of bound read and potentially a crash.

The bug is reachable via S-MIME validation with a crafted From: address
supplied in an email message that can potentially cause a crash.

No FIPS modules are affected by this issue as the affected code is outside
the OpenSSL FIPS module boundary.

OpenSSL 4.0 is vulnerable to this issue.

OpenSSL 3.6, 3.5, 3.4, 3.0, 1.1.1, and 1.0.2 are not affected by this issue.

OpenSSL 4.0 users should upgrade to OpenSSL 4.0.1.

This issue was reported by TrendAI Zero Day Initiative on 16th April 2026.

The fix was developed by Bob Beck.


Note You need to log in before you can comment on or make changes to this bug.