CVE-2025-8183 json
NULL Pointer Dereference in µD3TN
published last yr. modified 4mo ago also EUVD-2025-22582 , PYSEC-2025-182
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
NULL Pointer Dereference in µD3TN via non-singleton destination Endpoint Identifier allows remote attacker to reliably cause DoS
Patch / fix
- D3TN GmbH µD3TN 0.14.3
Is CVE-2025-8183 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- gitlab.com https://gitlab.com/d3tn/ud3tn/-/issues/255 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | pyd3tn | <=0.14.3 |
no fix listed |
Affected products
- D3TN GmbH µD3TN
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
-
gitlab.com
/d3tn/ud3tn/-/issues/255
issue-tracking, permissions-required, exploit, report
Sources
- CVE List CVE-2025-8183
- NVD CVE-2025-8183
- OSV PYSEC-2025-182
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.