Skip to main content
VulnerabilityPublished

CVE-2026-83813: twisted · Origin Validation Error

Affects twistedSource CVE Database V5

0

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

Data as of 26 Oct 2026, 14:00 UTC

CVSS 3.1 base score
3.1Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.7.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.7.0rc1.

Affected software

ProductAffectedFixed in
twistedtwistedAffected
  • <26.7.0rc1
Fixed in
  • 26.7.0rc1

AI-suggested

Upgrade Twisted to version 26.7.0rc1 or later, where this origin validation error is fixed. Applications should avoid reusing DNSDatagramProtocol instances to reduce exposure. No other vendor advisories or patches are indicated. Patch status is confirmed fixed in 26.7.0rc1.

Description

Twisted versions prior to 26.7.0rc1 have an origin validation error in twisted.names.dns.DNSDatagramProtocol. The protocol accepts UDP DNS responses based solely on matching transaction IDs without verifying the source host and port. This flaw allows an attacker who can send packets to the resolver's listening port with a correct transaction ID to inject forged DNS answers. Such forgery can redirect hostname resolution, potentially enabling mail interception, server-side request forgery, or man-in-the-middle attacks. The issue is fixed in version 26.7.0rc1.

References

Community reviews

Loading reviews…