dnspython dns.name.from_wire_parser() excessive CPU use

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-114605: 0.47% estimated exploitation activity in the next 30 days; percentile 40.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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

Published by the source

27 Oct 2026, 15:37 UTC

Last modified by the source

27 Oct 2026, 15:47 UTC

Source last checked

28 Oct 2026, 06:10 UTC

1. Revision 2 · amended · 28 Oct 2026

   Amended from osv record GHSA-45c3-73f7-pv4m

2. Revision 1 · created · 27 Oct 2026

   Published from ghsa record GHSA-45c3-73f7-pv4m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-114605

Advisory: dnspython dns.name.from_wire_parser() excessive CPU use
IDs: CVE-2026-114605, GHSA-45c3-73f7-pv4m
Record: https://patchnext.com/advisories/cve-2026-114605 (revision 2, source checked 28 Oct 2026, 06:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: dnspython 2.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI dnspython: affected < 2.9.0; fixed in 2.9.0

## Suggested inspection (read-only)
- `python -m pip show dnspython`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dnspython.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-45c3-73f7-pv4m (OSV record GHSA-45c3-73f7-pv4m lists affected ranges: PyPI dnspython >=0 <2.9.0 (fixed))
- Verified: https://github.com/advisories/GHSA-45c3-73f7-pv4m (GitHub-reviewed advisory GHSA-45c3-73f7-pv4m lists affected ranges: PyPI dnspython >=0 <2.9.0)

Commands are suggestions: review each one before running it.