CVE-2026-40613
Coturn Project Coturn ≤ 4.10.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2026-40613 is a high-severity Incorrect Type Conversion or Cast (CWE-704) vulnerability in Coturn Project Coturn. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 37% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-40613 is a vulnerability in Coturn, a free open source implementation of TURN and STUN servers, affecting versions prior to 4.10.0. The issue stems from unsafe pointer casts in the STUN/TURN attribute parsing functions within ns_turn_msg.c, where uint8_t pointers are cast to uint16_t pointers without alignment checks. Processing a crafted STUN message with odd-aligned attribute boundaries triggers misaligned memory reads, which on ARM64 (AArch64) architectures with strict alignment enforcement results in a SIGBUS signal that terminates the turnserver process.
An unauthenticated remote attacker can exploit this vulnerability by sending a single crafted UDP packet to any ARM64 Coturn deployment, causing an immediate denial-of-service crash of the turnserver process. The CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) reflects its network accessibility, low complexity, and high availability impact with no privileges required.
The Coturn GitHub security advisory (GHSA-j662-9wcj-mf36) confirms the vulnerability and states it is fixed in version 4.10.0, recommending users upgrade to this release or later to mitigate the issue.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-24228
Vulnerability Data
Coturn is a free open source implementation of TURN and STUN Server. Prior to 4.10.0, the STUN/TURN attribute parsing functions in coturn perform unsafe pointer casts from uint8_t * to uint16_t * without alignment checks. When processing a crafted STUN…
more
message with odd-aligned attribute boundaries, this results in misaligned memory reads at ns_turn_msg.c. On ARM64 architectures (AArch64) with strict alignment enforcement, this causes a SIGBUS signal that immediately kills the turnserver process. An unauthenticated remote attacker can crash any ARM64 coturn deployment by sending a single crafted UDP packet. This vulnerability is fixed in 4.10.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds incorrect type conversions or casts.
Requiring documented development standards and tools can mandate safe typing, casting rules, and compiler checks that stop the weakness from being introduced.
Security engineering principles can require type-safe design and casting practices that structurally avoid incorrect conversions.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent type-conversion flaws via coding standards, reviews, and testing.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can uncover type-conversion defects before release.
Secure development lifecycle includes type-safety reviews that reduce incorrect casts.
Application security requirements can mandate strong typing and safe casting rules.
Secure architecture principles discourage unsafe type conversions in design.
Secure coding standards directly forbid or detect incorrect type casts.