CVE-2025-8183: µD3TN · NULL Pointer Dereference
Affects µD3TNSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubd3tn/ud3tnpkg:github/d3tn/ud3tnOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Given the absence of an official patch at the time of disclosure, European organizations should implement several practical mitigations: 1) Network-level filtering: Restrict and monitor incoming traffic to µD3TN endpoints, especially from untrusted or external networks, to reduce exposure to remote attacks. 2) Input validation and sanitization: If possible, configure µD3TN or its environment to validate endpoint identifiers and reject malformed or unexpected inputs before processing. 3) Service isolation and redundancy: Deploy µD3TN services in isolated environments or containers to limit the blast radius of a crash, and implement redundancy or failover mechanisms to maintain availability during an attack. 4) Monitoring and alerting: Establish monitoring for µD3TN service crashes or abnormal behavior to detect potential exploitation attempts promptly. 5) Vendor engagement: Maintain communication with D3TN GmbH for updates on patches or mitigations, and apply official fixes as soon as they become available. 6) Incident response preparation: Develop and test response plans for DoS scenarios affecting µD3TN to minimize operational impact. These steps go beyond generic advice by focusing on network segmentation, proactive input handling, and operational resilience tailored to the nature of this vulnerability.
Description
NULL Pointer Dereference in µD3TN via non-singleton destination Endpoint Identifier allows remote attacker to reliably cause DoS