CVE-2026-97313

validatingZero is analyzing and reversing it now.

GHSA-9p2q-wv22-f9q8 ↗EUVD-2026-107256 ↗

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.
ISC BIND 9 >= 9.16.0, <= 9.18.50; >= 9.20.0, <= 9.20.29; >= 9.21.0, <= 9.21.26; >= 9.11.3-S1, <= 9.18.50-S1; >= 9.20.9-S1, <= 9.20.29-S1
CWE-617 Reachable Assertion
ETK-2026-2326Zero's internal tracking ID, independent of the CVE number., permanent identifier
1mrunning
evidencecurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0hvalidating
0
+1h
+2h
+3h
+4h

description

Affected BIND 9 releases can terminate unexpectedly when handling certain DNS query traffic. An attacker may deny DNS service if recursive queries are allowed and the server uses at least two RPZ zones with different recursive-only settings.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Restrict recursive-query access to trusted clients and avoid mixed recursive-only settings across RPZ zones. Monitor vendor updates and upgrade when a fixed release is published.

check
building now
exploit
not yet
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.
–
agent run time
1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 12:47Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-10-21 12:47Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2326",
  "cve_id": "CVE-2026-97313",
  "display_id": "CVE-2026-97313",
  "ghsa_id": "GHSA-9p2q-wv22-f9q8",
  "euvd_id": "EUVD-2026-107256",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Denial of service in ISC BIND 9 RPZ handling",
  "summary": "Affected BIND 9 releases can terminate unexpectedly when handling certain DNS query traffic. An attacker may deny DNS service if recursive queries are allowed and the server uses at least two RPZ zones with different `recursive-only` settings.",
  "mitigation": "Restrict recursive-query access to trusted clients and avoid mixed `recursive-only` settings across RPZ zones. Monitor vendor updates and upgrade when a fixed release is published.",
  "vendor": "ISC",
  "product": "BIND 9",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 9.16.0, <= 9.18.50",
        ">= 9.20.0, <= 9.20.29",
        ">= 9.21.0, <= 9.21.26",
        ">= 9.11.3-S1, <= 9.18.50-S1",
        ">= 9.20.9-S1, <= 9.20.29-S1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "BIND 9",
      "purl": null
    }
  ],
  "cwes": [
    617
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 45.517722733333336,
  "t0_at": "2026-10-21T12:47:28.499000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T12:47:28.499000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T12:47:28.499000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-97313"
    }
  }
}

published 2026-10-21 14:43Z
last change 2026-10-21 16:24Z

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.