Cyber Resilience

CVE-2026-55517

Deno ≤ 2.7.5

Published
23 June 2026
Modified
29 June 2026
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
EPSS Score 0.0018 8th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-55517 is a medium-severity Uncaught Exception (CWE-248) vulnerability in Deno Deno. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-8 (Security and Privacy Engineering Principles) and SC-24 (Fail in Known State) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.7.5, a Deno program that opens a client WebSocket connection could be crashed by the remote server. While handling the WebSocket handshake response, Deno parsed the Sec-WebSocket-Protocol and Sec-WebSocket-Extensions response…

more

headers in a way that assumed their bytes were always printable ASCII. A response header containing non-visible-ASCII bytes (0x80-0xFF) caused a panic that aborted the entire Deno process. This vulnerability is fixed in 2.7.5.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-26103Same product: Deno Deno
CVE-2024-27933Same product: Deno Deno
CVE-2026-49411Same product: Deno Deno
CVE-2026-49860Same product: Deno Deno
CVE-2025-48888Same product: Deno Deno
CVE-2024-34346Same product: Deno Deno
CVE-2024-27931Same product: Deno Deno
CVE-2026-32260Same product: Deno Deno
CVE-2025-48934Same product: Deno Deno
CVE-2026-22863Same product: Deno Deno

Affected Assets

deno
deno
≤ 2.7.5

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Security engineering principles include robust exception management to keep the system in a defined state.

Fail-in-known-state reduces the impact when an uncaught exception occurs by preserving a safe condition.

Error handling requirements force structured catching and response to exceptions instead of allowing them to propagate uncaught.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices explicitly require structured exception handling to prevent uncaught exceptions from reaching production.

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.

finds

Security testing can detect uncaught exceptions before production deployment.

prevents

Secure development lifecycle includes exception-handling standards that reduce uncaught exceptions.

prevents

Application security requirements typically mandate robust error and exception handling.

prevents

Secure architecture principles call for centralized, comprehensive exception management.

prevents

Secure coding standards directly require catching and handling exceptions to prevent crashes or leaks.

References