# CVE-2026-94418: Signature failure masked by date error under WOLFSSL_SMALL_CERT_VERIFY > Attackers can bypass certificate signature verification in wolfSSL when using specific low-resource configurations and date-error overriding callbacks. - **Severity:** Low 2.3 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 27 Sep 2026 - **Updated:** 29 Sep 2026 - **Also known as:** AZL-105182, DEBIAN-CVE-2026-94418, GHSA-q4rg-xp99-jj6q, UBUNTU-CVE-2026-94418 ## What is CVE-2026-94418? CVE-2026-94418 is a low-severity vulnerability in Wolfssl Wolfssl, published on 27 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Under WOLFSSL_SMALL_CERT_VERIFY, ProcessPeerCertParse() runs the certificate signature check separately from the parse to keep peak memory down, then merges the two results, but it merged the signature result back only when the parse returned 0, so any parse error hid it. ParseCertRelative() reaches its validity-date, name-constraint and critical-extension checks only after ConfirmSignature() has passed, so splitting the signature check out inverts the precedence that makes "override date errors" a sound policy, and ASN_SIG_CONFIRM_E is never surfaced anywhere. The attacker needs no key material from the real PKI and no CA compromise: a self-made certificate carrying the expected subject name, the trusted CA's subject as its issuer, arbitrary bytes where the signature goes, a validity window in the past and the attacker's own key pair is sufficient. Affected builds define WOLFSSL_SMALL_CERT_VERIFY, which is off by default, is not set implicitly by any platform or preset header, and is not reachable from any CMake option; the autotools routes are --enable-lowresource, --enable-leantls, --enable-tinytls13=cert and --enable-tinytls13=mutualauth, and examples/configs/user_settings_embedded.h reaches it through WC_CFG_SMALL_CERT_VERIFY, which ships as 0, while neither --enable-all nor --enable-distro enables it at all. The application must additionally install a verify callback through wolfSSL_CTX_set_verify() or wolfSSL_set_verify() with WOLFSSL_VERIFY_PEER that returns 1 for ASN_BEFORE_DATE_E or ASN_AFTER_DATE_E; wolfSSL ships this exact shape as myVerify() in wolfssl/test.h under VERIFY_OVERRIDE_DATE_ERR, which examples/client -D selects. An application with no callback, or whose callback returns preverify for date errors, still fails the handshake, and wolfSSL_CertManagerVerifyBuffer() and wc_CheckCertSignature() report ASN_SIG_CONFIRM_E correctly in the same binary. TLS 1.2 and TLS 1.3 are affected in both directions, and DTLS reaches the same function; where the forged certificate is a chain certificate the callback's consent causes it to be cached in the WOLFSSL_CTX certificate manager, so an exposed deployment must restart the context or the process rather than merely reconnect. Weakness: CWE-347 (Improper Verification of Cryptographic Signature) ## Which versions are affected by CVE-2026-94418? It affects 1 product. Products: Wolfssl Wolfssl. ## How do I fix CVE-2026-94418? No fix has been published for CVE-2026-94418 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-94418 being exploited? There is no known exploitation of CVE-2026-94418 in the wild and no public exploit code. ## Other vulnerabilities in Wolfssl Wolfssl - [CVE-2024-5991](https://insights.sbomify.com/CVE-2024-5991/): Buffer overread in domain name matching (critical 10.0) - [CVE-2021-37155](https://insights.sbomify.com/CVE-2021-37155/): Security feature bypass in n/a (critical 9.8) - [CVE-2020-36177](https://insights.sbomify.com/CVE-2020-36177/): Memory corruption in n/a (critical 9.8) - [CVE-2014-2896](https://insights.sbomify.com/CVE-2014-2896/): Memory corruption in n/a (critical 9.8) - [CVE-2014-2897](https://insights.sbomify.com/CVE-2014-2897/): Memory corruption in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-94418 and fix it if it is affected. What it is: CVE-2026-94418 is a low-severity vulnerability in Wolfssl Wolfssl, published on 27 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-94418 in the wild and no public exploit code. Affected product: Wolfssl Wolfssl. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-94418/ (Markdown: https://insights.sbomify.com/CVE-2026-94418/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-94418 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-94418 - OSV: https://osv.dev/vulnerability/CVE-2026-94418 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-94418/ Summaries are generated and may contain mistakes; the official description above is the record.