A failed X509_verify_cert call permanently plants an unverified attacker CA in the shared CertManager, bypassing certificate validation in every… (CVE-2026-89135)
A vulnerability in wolfSSL versions 5.8.4 through 5.9.2 with specific build configurations allows a failed X509_verify_cert call to permanently add an unverified attacker CA to the shared CertManager. This bypasses certificate validation for all consumers relying on the shared CertManager, including native TLS, OCSP, CRL, and direct certificate manager verification. The issue occurs only when the macros OPENSSL_EXTRA, NO_CERTS, and WOLFCRYPT_ONLY are set in a particular way or when built with --enable-opensslextra, and the application explicitly calls X509_verify_cert.
AI Analysis
Technical Summary
CVE-2026-89135 describes a certificate validation bypass in wolfSSL library versions 5.8.4 through 5.9.2 under certain build conditions. When an X509_verify_cert call fails, it incorrectly plants an unverified attacker CA certificate into the shared CertManager. This flaw causes all type-blind sibling consumers of the CertManager to trust the attacker CA, effectively bypassing certificate validation mechanisms across native TLS, OCSP, CRL, and direct certificate manager verification. The vulnerability requires the presence of specific macros (OPENSSL_EXTRA && !NO_CERTS && !WOLFCRYPT_ONLY) or the build flag --enable-opensslextra and explicit use of the vulnerable function.
Potential Impact
This vulnerability allows an attacker to bypass certificate validation by injecting an unverified CA into the shared CertManager. This compromises the trust model of TLS and related certificate validation processes, potentially enabling man-in-the-middle attacks or acceptance of fraudulent certificates. The CVSS 3.1 base score is 6.5 (medium severity), reflecting network attack vector, low attack complexity, no privileges or user interaction required, and impact on confidentiality and integrity but not availability.
Mitigation Recommendations
No official patch or remediation information is provided in the input data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid using the vulnerable wolfSSL versions with the specified build configurations and refrain from calling X509_verify_cert in affected builds.
A failed X509_verify_cert call permanently plants an unverified attacker CA in the shared CertManager, bypassing certificate validation in every… (CVE-2026-89135)
Description
A vulnerability in wolfSSL versions 5.8.4 through 5.9.2 with specific build configurations allows a failed X509_verify_cert call to permanently add an unverified attacker CA to the shared CertManager. This bypasses certificate validation for all consumers relying on the shared CertManager, including native TLS, OCSP, CRL, and direct certificate manager verification. The issue occurs only when the macros OPENSSL_EXTRA, NO_CERTS, and WOLFCRYPT_ONLY are set in a particular way or when built with --enable-opensslextra, and the application explicitly calls X509_verify_cert.
CVSS v3.1
Score 6.5medium
Affected software
pkg:github/wolfssl/wolfsslRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-89135 describes a certificate validation bypass in wolfSSL library versions 5.8.4 through 5.9.2 under certain build conditions. When an X509_verify_cert call fails, it incorrectly plants an unverified attacker CA certificate into the shared CertManager. This flaw causes all type-blind sibling consumers of the CertManager to trust the attacker CA, effectively bypassing certificate validation mechanisms across native TLS, OCSP, CRL, and direct certificate manager verification. The vulnerability requires the presence of specific macros (OPENSSL_EXTRA && !NO_CERTS && !WOLFCRYPT_ONLY) or the build flag --enable-opensslextra and explicit use of the vulnerable function.
Potential Impact
This vulnerability allows an attacker to bypass certificate validation by injecting an unverified CA into the shared CertManager. This compromises the trust model of TLS and related certificate validation processes, potentially enabling man-in-the-middle attacks or acceptance of fraudulent certificates. The CVSS 3.1 base score is 6.5 (medium severity), reflecting network attack vector, low attack complexity, no privileges or user interaction required, and impact on confidentiality and integrity but not availability.
Mitigation Recommendations
No official patch or remediation information is provided in the input data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid using the vulnerable wolfSSL versions with the specified build configurations and refrain from calling X509_verify_cert in affected builds.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-m732-8qwx-39wm
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89135"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6ac139bea43b0b3b89d69d58
Added to database: 10/03/2026, 17:22:06 UTC
Last enriched: 10/03/2026, 17:43:43 UTC
Last updated: 10/03/2026, 23:40:54 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.