AI Science Tracker

wolfSSL may accept a forged certificate in a constrained small-verification configuration

wolfSSL embedded SSL/TLS library · AI involvement attributed to Anthropic OSS program (model unspecified)

Finding and attribution

Under WOLFSSL_SMALL_CERT_VERIFY, a signature verification error can be hidden when certificate parsing also returns an error. The documented attack additionally requires a peer-verification callback configured to accept certificate date errors; a crafted self-issued certificate can then pass despite an invalid signature. The vendor says this build option is off by default and lists specific low-resource/TinyTLS configurations. A chain certificate accepted this way may be cached in the context certificate manager.

Product: wolfSSL embedded SSL/TLS library. AI system: Anthropic OSS program (model unspecified). Team / organization: Anthropic and wolfSSL.

CVE identifiers: CVE-2026-94418.

AI and human contribution (source account): wolfSSL explicitly says this finding was found via the Anthropic OSS program. The public advisory does not identify the model or divide discovery and validation responsibilities. Anthropic’s primary OSS Scanner announcement says its scanner finds vulnerabilities with its strongest language models and that the opt-in scanner outputs are fully model-generated without human review or triage. The announcement quotes wolfSSL on results from 74 reports, including five CVEs, but does not map those five to CVE identifiers; model/version attribution for this individual case therefore remains unspecified.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: wolfSSL publicly announced version 5.9.4 and its security fixes on 2026-09-28. The itemized vendor catalog attributes this finding to the Anthropic OSS program. No exploitation-in-the-wild or zero-day claim is made. The public AI-program provenance account is Anthropic’s OSS Scanner announcement dated 2026-10-08; the wolfSSL disclosure date remains 2026-09-28.

Remediation status: fix documented. wolfSSL lists 5.9.4 as fixed. The issue requires both the documented build configuration and a callback accepting date errors; affected deployments with a cached forged chain may need to restart the context or process.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 28 Sep 2026. AI attribution dated 8 Oct 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Low · highest recorded score 2.3. Documented technical effects: authentication bypass.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • CVE-2026-94418: CVSS 4.0 · 2.3 (Low) · CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · Assessment scenarios: GENERAL. wolfSSL (CNA; CVE Program record) · checked 16 Nov 2026.

CVE-2026-94418: authentication bypass.
Prerequisites / affected scope: Requires WOLFSSL_SMALL_CERT_VERIFY; a self-signed certificate can obscure signature failure when parsing also fails, allowing forged certificates to be accepted. Include config-specific excluded builds as condition..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: wolfSSL lists 5.9.4 as fixed. The issue requires both the documented build configuration and a callback accepting date errors; affected deployments with a cached forged chain may need to restart the context or process.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases