Certificate trust bypass via untrusted intermediate anchoring
Published Jun 25, 2026 · Updated Jun 25, 2026
Improper certificate validation in wolfSSL 5.8.4 through 5.9.1 allows remote attackers to have untrusted chains accepted. The OpenSSL compatibility verifier keeps caller-supplied intermediates in its certificate manager during the trusted-store check, allowing an intermediate to serve as its own trust anchor. Exploitation requires an OPENSSL_EXTRA build and an application that passes untrusted intermediates to X509_verify_cert(); native TLS and DTLS verification are unaffected.
Summary
What happened
Improper certificate validation in wolfSSL 5.8.4 through 5.9.1 allows remote attackers to have untrusted chains accepted. The OpenSSL compatibility verifier keeps caller-supplied intermediates in its certificate manager during the trusted-store check, allowing an intermediate to serve as its own trust anchor. Exploitation requires an OPENSSL_EXTRA build and an application that passes untrusted intermediates to X509_verify_cert(); native TLS and DTLS verification are unaffected.
The record
- CVE
- CVE-2026-11310
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- wolfSSL
- Product
- wolfSSL
- Classifications
- CWE-295
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.8.4 <=5.9.1
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