CVE-2026-114605

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

GHSA-45c3-73f7-pv4m ↗EUVD-2026-108227 ↗

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.
pip:dnspython < 2.9.0
fixed in 2.9.0
CWE-674 Uncontrolled Recursion
ETK-2026-1025Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/dnspython
1h 10msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal −14dcve.org publicationwaiting for further signals+0.0d
−10d
−5d

description

dnspython releases before 2.9.0 can consume excessive CPU while decoding DNS names from wire-format messages. An attacker may degrade service or cause denial of service when an application passes untrusted DNS messages to the affected parser.

mitigation

Upgrade dnspython to version 2.9.0 or later. Prioritize systems that parse DNS wire-format data from untrusted sources.

fixed in 2.9.0

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.
no
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-22 16:25Z
Δ 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-09 00:13Z
  2. 2026-10-22 16:25Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1025",
  "cve_id": "CVE-2026-114605",
  "display_id": "CVE-2026-114605",
  "ghsa_id": "GHSA-45c3-73f7-pv4m",
  "euvd_id": "EUVD-2026-108227",
  "status": "published",
  "anchor_state": "anchored",
  "title": "DNS name decompression CPU exhaustion in dnspython",
  "summary": "dnspython releases before 2.9.0 can consume excessive CPU while decoding DNS names from wire-format messages. An attacker may degrade service or cause denial of service when an application passes untrusted DNS messages to the affected parser.",
  "mitigation": "Upgrade dnspython to version 2.9.0 or later. Prioritize systems that parse DNS wire-format data from untrusted sources.",
  "vendor": "pip",
  "product": "pip:dnspython",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 2.9.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "2.9.0"
      ],
      "package_name": "dnspython",
      "purl": "pkg:pypi/dnspython"
    }
  ],
  "cwes": [
    674
  ],
  "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": 8.792351266666667,
  "t0_at": "2026-10-22T16:25:32.509000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-09T00:13:25+00:00",
      "days": -13.675086909722221,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T16:25:32.509000+00:00",
      "url": "https://github.com/rthalley/dnspython/security/advisories/GHSA-45c3-73f7-pv4m"
    }
  }
}

Anchor corroborated by the cve.org commit 91a8447a50fc.

published 2026-10-09 01:50Z
last change 2026-10-22 18:15Z

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.