Failed X509_verify_cert leaves unverified CA in shared CertManager
A failed X509_verify_cert call permanently plants an unverified attacker CA in the shared CertManager, bypassing certificate validation in every type-blind sibling consumer (native TLS, OCSP, CRL, direct CM verify). This affects version 5.8.4 through 5.9.2 of wolfSSL with the macros (OPENSSL_EXTRA && !NO_CERTS && !WOLFCRYPT_ONLY) defined or built with --enable-opensslextra and the application is specifically making calls to the X509_verify_cert function.
CVE-2026-89135
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-89135
wolfSSL
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "wolfSSL",
"product": "wolfSSL",
"versions": [
{
"status": "affected",
"version": "5.8.4",
"versionType": "semver",
"lessThanOrEqual": "5.9.2"
}
],
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-89135
Source reference:
/cveMetadata/cveId
Publisher severity
medium
Source reference: /containers/cna/metrics
- Event
- #3815 · Revision 1
- Added to Heist Feed
- Publisher date