Certificate identity bypass via overwritten email constraint
Published Mar 6, 2026 · Updated Sep 14, 2026
Improper certificate validation in Go crypto/x509 1.26.0 allows attackers to accept disallowed email identities via crafted chains. Certificate.Verify stores full-email constraints in a map keyed only by the case-sensitive local portion, so a later constraint with the same local portion overwrites an earlier domain. Exploitation requires a trusted CA to issue a chain containing a prohibited or excluded email address, after which verification can accept that identity.
Summary
What happened
Improper certificate validation in Go crypto/x509 1.26.0 allows attackers to accept disallowed email identities via crafted chains. Certificate.Verify stores full-email constraints in a map keyed only by the case-sensitive local portion, so a later constraint with the same local portion overwrites an earlier domain. Exploitation requires a trusted CA to issue a chain containing a prohibited or excluded email address, after which verification can accept that identity.
The record
- CVE
- CVE-2026-27137
- Published
- Mar 6, 2026
- Updated
- Sep 14, 2026
- Vendor
- Red Hat
- Product
- Red Hat Lightspeed for Runtimes
- Classifications
- CWE-295
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 6, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo