TLS identity forgery via unchecked issuer authority
Published Sep 27, 2026 · Updated Sep 27, 2026
Improper certificate validation in wolfSSL 5.7.2 through 5.9.2 allows remote attackers to impersonate arbitrary TLS identities. The OCSP stapling v2 multi-response client path treats any peer-chain certificate as an issuer without verifying its CA authority. Exploitation requires the v2 status-request feature, OCSP multi mode, and a trusted-chain certificate with its private key; the peer leaf then persists in the context trust store.
Summary
What happened
Improper certificate validation in wolfSSL 5.7.2 through 5.9.2 allows remote attackers to impersonate arbitrary TLS identities. The OCSP stapling v2 multi-response client path treats any peer-chain certificate as an issuer without verifying its CA authority. Exploitation requires the v2 status-request feature, OCSP multi mode, and a trusted-chain certificate with its private key; the peer leaf then persists in the context trust store.
The record
- CVE
- CVE-2026-89102
- Published
- Sep 27, 2026
- Updated
- Sep 27, 2026
- Vendor
- wolfSSL
- Product
- wolfSSL
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 27, 2026CVE publishedPublication date reported by the CVE source.
- Sep 27, 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.7.2 <=5.9.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started