Quick answers
- Is CVE-2026-121513 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121513 being exploited in the wild.
- How severe is CVE-2026-121513?
- High severity, with a CVSS score of 7.5, published 3 November 2026.
- Which products and versions are affected?
- D3TN µD3TN v0.15.1 and earlier (master branch at commit ea56c6fb695044b1d05b965b545760ad36da25a1).
- Is there a fix for CVE-2026-121513?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-121513 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-121513?
- Check whether you run D3TN µD3TN at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An off-by-one error in the SPP timecode parser's fractional octet count extraction leads to a heap buffer overflow in the parser state's fractional_buf. The vulnerability exists in the handling of SPP frames with secondary headers and is triggered via a malformed P-field. An unauthenticated attacker on the network can reliably exploit this to cause process termination; no authentication is required and the attack requires only network connectivity to the SPP port.
Affected products
- D3TN µD3TN v0.15.1 and earlier (master branch at commit ea56c6fb695044b1d05b965b545760ad36da25a1)
Timeline
- 2026-11-03: disclosed