CVE-2026-95184

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

GHSA-prfj-h7xq-vv26 ↗EUVD-2026-95140 ↗

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.
GnuTLS n/a
CWE-400 Uncontrolled Resource Consumption
ETK-2026-1979Zero's internal tracking ID, independent of the CVE number., permanent identifier
2d 19h 31msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+257h09m
0
+2h
+4h
+6h
+8h
+10h

description

GnuTLS 3.8.13 is affected by certificate-validation behavior that can reject legitimate certificates. This can deny service to valid users when affected applications validate their certificates; the evidence does not further specify the triggering conditions.

mitigation

Update from GnuTLS 3.8.13 when a vendor-provided corrected release is available. Until then, reduce exposure by limiting network access to services that rely on affected certificate validation and monitor for unexpected certificate-validation failures.

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.
–
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.17%5th percentile
agent run time
10m
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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-08 00:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-08 00:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1979",
  "cve_id": "CVE-2026-95184",
  "display_id": "CVE-2026-95184",
  "ghsa_id": "GHSA-prfj-h7xq-vv26",
  "euvd_id": "EUVD-2026-95140",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper certificate validation denial of service in GnuTLS",
  "summary": "GnuTLS 3.8.13 is affected by certificate-validation behavior that can reject legitimate certificates. This can deny service to valid users when affected applications validate their certificates; the evidence does not further specify the triggering conditions.",
  "mitigation": "Update from GnuTLS 3.8.13 when a vendor-provided corrected release is available. Until then, reduce exposure by limiting network access to services that rely on affected certificate validation and monitor for unexpected certificate-validation failures.",
  "vendor": null,
  "product": "GnuTLS",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": [
    400
  ],
  "cvss_score": 7.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0017,
  "epss_percentile": 0.0534,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.351603716666666,
  "t0_at": "2026-10-08T00:00:00+00:00",
  "signals": {
    "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://github.com/advisories/GHSA-prfj-h7xq-vv26"
    }
  }
}

published 2026-10-18 14:29Z
last change 2026-10-21 11:38Z

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.