NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

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

highCVSS 3.1 7.5GHSA-45c3-73f7-pv4m

dnspython before 2.9.0 follows DNS name compression pointers without a limit in `dns.name.from_wire_parser()`. A crafted DNS message makes the parser burn excessive CPU, which can degrade or take down any application that parses untrusted DNS wire data. Fixed in dnspython 2.9.0. There is no workaround.

Published Oct 27, 2026 · Updated Nov 12, 2026 · Analysis Nov 1, 2026

What an attacker can do

DNS messages compress names by pointing back to earlier bytes in the packet. from_wire_parser() follows those pointers to rebuild a name. Before the fix it set no limit on how many pointers it would follow in a chain, so a message built with long or tangled pointer chains forces a large amount of work for a small packet.

An attacker needs only to get such a message to the parser. That is easy for a service that reads DNS responses from the network, such as a resolver client, scanner, mail server component, or any tool that queries names an attacker influences, and for ones that accept DNS wire-format input. No authentication or interaction is required (CVSS PR:N/UI:N). The effect is availability only: the process slows or stalls, and repeated messages can keep it so. The advisory describes no data exposure or code execution.

Who is affected

dnspython before 2.9.0, in applications that process untrusted DNS wire-format messages, such as responses from a network resolver or packets received from clients. Check:

pip show dnspython

Dnspython is a common transitive dependency. Use pip show dnspython inside each virtualenv or image, or pipdeptree -r -p dnspython to see what pulls it in.

dnspython

Ecosystem
PyPI
Affected
< 2.9.0
Fixed in
2.9.0
Check
pip show dnspython

How to fix it

Upgrade to dnspython 2.9.0:

pip install --upgrade "dnspython>=2.9.0"

The fix adds a cap of 16 compression pointers per name (MAX_COMPRESSION_POINTER_CHAIN = 16). A longer chain raises the new PointerChainTooLong exception, a subclass of FormError. The advisory says there are no known workarounds. Callers that catch FormError already handle the new exception.

How to tell if you were hit

Look for DNS-handling processes with sustained high CPU, slow responses or timeouts that line up with DNS traffic from a particular source. After upgrading, PointerChainTooLong errors in logs mark malformed or hostile messages. The advisory lists no network signature. Capturing the offending packet and checking for deep chains of compression pointers confirms the cause.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Impact

A maliciously crafted DNS message may cause dns.name.from_wire_parser() to use excessive CPU for DNS name decompression. Applications that process untrusted DNS wire form messages with dnspython may be degraded or DoS'd by the extra CPU use required.

Patches

This problem is fixed in dnspython 2.9.0.

Workarounds

There are no known workarounds.

Credit

Evgenios Gkritsis, Department of Informatics, University of Piraeus & Athena Research Center, Greece Constantinos Patsakis, Department of Informatics, University of Piraeus & Athena Research Center, Greece George Stergiopoulos, Department of Informatics, Athens University of Economics and Business, Greece

Credited to eGkritsis, kpatsakis, geostergiop.

Questions

Which dnspython version fixes CVE-2026-114605?

2.9.0. It limits name decompression to 16 compression pointers and raises PointerChainTooLong beyond that.

Is there a workaround?

No. The advisory states there are no known workarounds, so upgrade. You can limit exposure by not parsing DNS messages from untrusted sources.

Does this allow code execution?

No. The advisory describes excessive CPU use, and the CVSS vector shows only availability impact.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More PyPI vulnerabilities

All PyPI entries