CVE-2008-4126

What it is

PyDNS (aka python-dns) before 2.3.1-5 in Debian GNU/Linux does not use random source ports for DNS requests and does not use random transaction IDs for DNS retries, which makes it easier for remote attackers to spoof DNS responses, a different vulnerability than CVE-2008-1447. NOTE: this vulnerability exists because of an incomplete fix for CVE-2008-4099.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

2.2% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2008-09-18 17:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 22:57 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.2% in the next 30 days (EPSS).
• Severity: 6.4 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2008-09-18 17:59 UTC

Last modified

2026-06-16 22:57 UTC

Exploit probability

2.2% · EPSS, next 30 days

Weakness

CWE-16

Record status

Modified

Affected

• Debian python-dns ≤ 2.3.1-4
• Debian python-dns 2.3.0-1
• Debian python-dns 2.3.0-2
• Debian python-dns 2.3.0-3
• Debian python-dns 2.3.0-4
• Debian python-dns 2.3.0-5
• Debian python-dns 2.3.0-5.1
• Debian python-dns 2.3.0-6

Attack profile CVSS 2.0 · 6.4

Attack vector

Network

Complexity

Low

Authentication

None

Confidentiality

None

Integrity

Partial

Availability

Partial

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2008-4126.md and follow it. Check whether this project is affected by CVE-2008-4126. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge