Skip to main content
VulnerabilityPublished

CVE-2026-114605: Ggshield · dnspython dns.name.from_wire_parser() excessive CPU use

Affects ggshieldSource GCVE Database

0
Compare
Authoritative record:CVE-2026-114605· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.56.0 soon.

Data as of 30 Oct 2026, 07:16 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.5
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.56.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade ggshield to 1.56.0.

Affected software

ProductAffectedFixed in
Homebrewggshieldpkg:brew/ggshieldOther threatsAffected
  • >=1.50.3 <1.56.0
Fixed in
  • 1.56.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade dnspython to version 1.56.0 or later to remediate this vulnerability. No workarounds are currently known.

Description

A vulnerability in dnspython's dns.name.from_wire_parser() function can cause excessive CPU usage when processing maliciously crafted DNS messages. This can degrade or deny service to applications handling untrusted DNS wire format messages. The issue is fixed in dnspython version 1.56.0. No known workarounds exist.

References

Community reviews

Loading reviews…