CVE-2026-11310 - X.509 trust-chain bypass in the OpenSSL compatibility certificate verifier (wolfSSL_X509_verify_cert())

CVE-2026-11310 + X.509 trust-chain bypass in the OpenSSL compatibility certificate verifier (wolfSSL_X509_verify_cert()) + High + 2026-06-25

One-sentence business risk

Broken authentication or authorization can expose tenant data and administrator actions, which buyers treat as a release blocker.

Research notes

  • Root cause: X.509 trust-chain bypass in the OpenSSL compatibility certificate verifier (wolfSSL_X509_verify_cert()).
  • Affected versions: before the trusted-store check, so an untrusted intermediate could anchor the path itself.
  • Fixed / safe versions: Vendor-fixed release or mitigation named by the upstream advisory.
  • Public exploit / PoC signal: the consulted NVD/GHSA/vendor sources describe the trigger class; treat it as reproducible until patched.
  • CVSS: 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Exact vulnerable code pattern

if verify_certificate(chain) == OK: trust_peer()

Fixed / mitigated code pattern

verify hostnames, negotiated certificate type, revocation markers, and trusted anchors

Dependency or runtime update:

rg -n "wolfssl|OpenSSL|X509|ML-KEM|X25519" .
# update vendored library/submodule/package to the fixed vendor release and rebuild

Step-by-step integration guide

  1. Inventory wolfssl across source, lockfiles, SBOMs, container images, CI images, and deployment manifests.
  2. Upgrade to Vendor-fixed release or mitigation named by the upstream advisory or apply the exact vendor patch referenced below.
  3. Replace the vulnerable cert-validation pattern with the fixed pattern and fail closed on malformed input.
  4. Add a regression test that exercises the advisory trigger and proves the request is rejected, bounded, or authorized.
  5. Deploy through canary, monitor security logs and resource metrics, then remove temporary edge blocks only after all runtimes are fixed.

Alternative mitigations

  • Disable the vulnerable feature path while the package/runtime update rolls out.
  • Add WAF or reverse-proxy rules for traversal tokens, prototype-polluting keys, oversized frames, shell metacharacters, or unauthenticated tool calls matching the trigger class.
  • Restrict internal egress, rotate exposed secrets, and revoke affected tokens/keys if the vulnerability can disclose config, logs, JWT secrets, proxy credentials, or PKI material.
  • For admin/API authorization issues, temporarily require elevated roles and explicit ownership checks at the gateway.

Detection signature

id: cve-2026-11310-x-509-trust-chain-bypass-in-the-openssl-compatib
source: NVD
dependency_or_product: "wolfssl"
affected: "before the trusted-store check, so an untrusted intermediate could anchor the path itself"
fixed: "Vendor-fixed release or mitigation named by the upstream advisory"
signals:
  - "cert-validation"
  - "../"
  - "__proto__"
  - "tools/call"
  - "wp_ajax_nopriv"
  - "pickle.loads"
  - "shell command construction"
action: "upgrade, add regression test, and verify deploy artifact"

Copy-paste skill

You are remediating CVE-2026-11310 (X.509 trust-chain bypass in the OpenSSL compatibility certificate verifier (wolfSSL_X509_verify_cert())) in this repository.

Find every affected dependency, runtime, image, service configuration, and reachable code path. Upgrade or patch to Vendor-fixed release or mitigation named by the upstream advisory. Replace the vulnerable cert-validation pattern with a fail-closed implementation, add a regression test for the trigger shape, and update deployment/SBOM artifacts. If this repository does not control the affected runtime, create TRIAGE.md naming the owner, affected version, fixed version, and blocking decision.

Keywords, affected tech stack, and revenue tags

  • Keywords: CVE-2026-11310, cert-validation, wolfssl, NVD.
  • Affected tech stack: c/c++.
  • Revenue tags: sellable_to_fintech, enterprise_blocker, high_priority_sla.

References