CVE-2026-95210

validatedZero produced an exploit or a check.

GHSA-9mfx-g534-q3pc ↗EUVD-2026-95139 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
GnuTLS n/a
CWE-295 Improper Certificate Validation
ETK-2026-1977Zero's internal tracking ID, independent of the CVE number., permanent identifier
+11dTTV
28mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0dcheck available+11dagent stopped
0
+5d
+10d

description

GnuTLS 3.8.13 may accept certificates containing invalid extensions during certificate validation. An attacker able to present such a certificate could cause an affected application to treat it as acceptable.

mitigation

Restrict affected applications to trusted endpoints and add independent certificate-policy checks where feasible. Monitor GnuTLS release guidance and upgrade when a corrected version is identified.

check
available
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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.12%1st percentile
agent run time
28m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-08 00:00Z
Δ 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 check: a technique exists and was validated, 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-08 00:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1977",
  "cve_id": "CVE-2026-95210",
  "display_id": "CVE-2026-95210",
  "ghsa_id": "GHSA-9mfx-g534-q3pc",
  "euvd_id": "EUVD-2026-95139",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper certificate validation in GnuTLS 3.8.13",
  "summary": "GnuTLS 3.8.13 may accept certificates containing invalid extensions during certificate validation. An attacker able to present such a certificate could cause an affected application to treat it as acceptable.",
  "mitigation": "Restrict affected applications to trusted endpoints and add independent certificate-policy checks where feasible. Monitor GnuTLS release guidance and upgrade when a corrected version is identified.",
  "vendor": null,
  "product": "GnuTLS",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": [
    295
  ],
  "cvss_score": 9.1,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0012,
  "epss_percentile": 0.0197,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 27.9018233,
  "t0_at": "2026-10-08T00:00:00+00:00",
  "signals": {
    "check": {
      "at": "2026-10-18T17:08:35.515935+00:00",
      "days": 10.71429995295139,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T00:00:00+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-08T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T00:00:00+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-95210"
    }
  }
}

published 2026-10-18 14:28Z
last change 2026-10-21 01:51Z

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.