CVE-2026-19630

validatingZero is analyzing and reversing it now.
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.11.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-407 Inefficient Algorithmic Complexity
ETK-2026-2320Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 19mrunning
synthesiscurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0mvalidating
0
+30min
+60min
+90min

description

BIND 9 resolvers in the listed affected release ranges can consume excessive CPU time and memory while processing specially structured inbound DNS messages. An attacker able to send such messages to a vulnerable resolver can degrade its availability.

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

mitigation

Limit network access to affected resolver services and restrict recursive queries to trusted clients where feasible. Monitor resolver resource use and apply an upstream update when a fixed release is available.

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
1h 19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 12:41Z
Δ 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:41Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2320",
  "cve_id": "CVE-2026-19630",
  "display_id": "CVE-2026-19630",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Resource exhaustion in ISC BIND 9 DNS message processing",
  "summary": "BIND 9 resolvers in the listed affected release ranges can consume excessive CPU time and memory while processing specially structured inbound DNS messages. An attacker able to send such messages to a vulnerable resolver can degrade its availability.",
  "mitigation": "Limit network access to affected resolver services and restrict recursive queries to trusted clients where feasible. Monitor resolver resource use and apply an upstream update when a fixed release is available.",
  "vendor": "ISC",
  "product": "BIND 9",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 9.11.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": [
    407
  ],
  "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": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-10-21T12:41:04.379000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T12:41:04.379000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T12:41:04.379000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-19630"
    }
  }
}

published 2026-10-21 13:02Z
last change 2026-10-21 14:01Z

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.