CVE-2026-111943

waiting for further signalsZero needs more public information before it can validate it.

EUVD-2026-106926 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Go standard library crypto/x509 < 1.26.10; >= 1.27.0-0, < 1.27.3
fixed in 1.26.10, 1.27.3
ETK-2026-2258Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 17msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h05m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Go crypto/x509 before 1.26.10 or 1.27.3 can continue to accept certificate chains involving intermediates that should no longer be trusted. An attacker may be able to rely on such a chain where the system trust store has not incorporated the relevant trust removal and the application performs certificate verification.

mitigation

Upgrade Go to 1.26.10 or 1.27.3. Ensure systems also keep their operating-system certificate trust stores current.

fixed in 1.26.10, 1.27.3

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 00:52Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-21 00:52Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-111943

{
  "etk_id": "ETK-2026-2258",
  "cve_id": "CVE-2026-111943",
  "display_id": "CVE-2026-111943",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-106926",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Certificate trust revocation gap in Go crypto/x509",
  "summary": "Go crypto/x509 before 1.26.10 or 1.27.3 can continue to accept certificate chains involving intermediates that should no longer be trusted. An attacker may be able to rely on such a chain where the system trust store has not incorporated the relevant trust removal and the application performs certificate verification.",
  "mitigation": "Upgrade Go to 1.26.10 or 1.27.3. Ensure systems also keep their operating-system certificate trust stores current.",
  "vendor": "Go standard library",
  "product": "crypto/x509",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.26.10",
        ">= 1.27.0-0, < 1.27.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.26.10",
        "1.27.3"
      ],
      "package_name": "crypto/x509",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.180237816666667,
  "t0_at": "2026-10-21T00:52:18.359000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T00:52:18.359000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T00:52:18.359000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111943"
    }
  }
}

published 2026-10-21 01:48Z
last change 2026-10-21 03:59Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.