Skip to main content
VulnerabilityPublished

CVE-2026-83813: DNS Response Spoofing in twisted.names Due to Missing Source Address Validation

Affects TwistedSource GCVE Database

0
Authoritative record:CVE-2026-83813· Low 3.1

Not known to be exploited · CVSS 3.1 Low : upgrade to 26.10.0rc1 when convenient.

Data as of 27 Oct 2026, 15:14 UTC

CVSS 3.1 base score
3.1Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 26.10.0rc1
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade Twisted to 26.10.0rc1.

Affected software

ProductAffectedFixed in
PyPITwistedAffected
  • <26.10.0rc1
Fixed in
  • 26.10.0rc1

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

AI-suggested

A fix is available in Twisted version 26.10.0rc1. Users should upgrade to this version or later to ensure source address validation is implemented and the vulnerability is remediated. No additional mitigation steps are required beyond applying the official fix.

Description

Twisted's DNS client UDP transport (twisted.names.dns.DNSDatagramProtocol) accepts DNS responses based solely on matching the 16-bit transaction ID without validating the source address. This allows an attacker able to send UDP packets to the resolver's port to inject forged DNS responses, enabling off-path DNS response spoofing or cache poisoning. The standard client mitigates this risk by using per-query random source ports, increasing entropy, but the missing source address validation remains a security gap. This affects all versions prior to 26.10.0rc1, where the issue is fixed.

References

Community reviews

Loading reviews…