Cyber Resilience

CVE-2026-55434

DoS in Coder 2.33.0 – 2.33.8

Published
07 July 2026
Modified
08 July 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0031 23th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-55434 is a medium-severity Allocation of Resources Without Limits or Throttling (CWE-770) vulnerability in Coder Coder. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

This vulnerability is AI-related — categorised as Other AI Platforms.

The strongest mitigations our analysis identified map to SC-6 (Resource Availability) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

No EU or UK CSIRT advisories indexed for this CVE.

Vulnerability Data

Coder allows organizations to provision remote development environments via Terraform. Starting in version 2.33.0 and prior to versions 2.33.8 and 2.34.2, AI Bridge provider handlers read request bodies with `io.ReadAll` without a maximum size so an authenticated user with AI…

more

Bridge access could send an arbitrarily large body and exhaust memory. Exploitation requires authenticated access to the AI Bridge endpoints and the impact is limited to availability (denial of service). Versions 2.33.8 and 2.34.2 patch the issue. No known workarounds are available.

CWE(s)

AI Security AnalysisAI

AI Category
Other AI Platforms
Risk Domain
N/A
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: ai, ai, ai

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

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.
Why these techniques?

The vulnerability allows an authenticated user to send an arbitrarily large request body to AI Bridge endpoints, causing memory exhaustion and resulting in a denial of service via application-level resource exhaustion.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-55078Same product: Coder Coder
CVE-2026-55436Same product: Coder Coder
CVE-2026-55435Same product: Coder Coder
CVE-2026-55433Same product: Coder Coder
CVE-2026-55427Same product: Coder Coder
CVE-2026-55075Same product: Coder Coder
CVE-2026-55079Same product: Coder Coder
CVE-2026-55429Same product: Coder Coder
CVE-2026-55431Same product: Coder Coder
CVE-2026-55077Same product: Coder Coder

Affected Assets

coder
coder
2.33.0 — 2.33.8 · 2.34.0 — 2.34.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-6 Resource Availability
  • AC-3 Access Enforcement
Detect
Catch it (NIST detect / respond)
  • SI-4 System Monitoring
Harden
Shrink the surface (DISA STIG)
  • 5 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V15.4.4

Mitigating Controls (NIST 800-53 r5) AI

prevent

SC-6 directly requires the system to protect against resource exhaustion by limiting the amount of memory that can be consumed by a single request, which is the root cause of this unbounded io.ReadAll DoS.

prevent

AC-3 enforces access-control decisions on the AI Bridge endpoints, ensuring only authorized users can reach the vulnerable handler and thereby reducing the attack surface.

detect

SI-4 enables monitoring of anomalous request sizes or memory-consumption patterns that would indicate an attempted resource-exhaustion attack against the AI Bridge.

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.IR-04 mostly match
degrades

Monitoring capacity and taking action to maintain availability directly reduces unchecked resource allocation.

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.

detects

Baseline comparison of CPU, memory and bandwidth usage helps surface uncontrolled resource allocations before they cause service degradation.

prevents

Capacity projections and elasticity measures ensure that allocation requests are bounded and can be throttled, reducing the window in which an attacker can force unbounded resource reservations.

mitigates

Defining retention periods and deletion schedules for backup copies prevents indefinite accumulation of data on storage media without corresponding resource-management controls.

mitigates

Architectural redundancy and automatic failover limit the impact of an attacker who forces excessive allocations, because spare capacity can absorb the load until the primary instance recovers.

none

Documented incident response procedures that include activation of continuity plans and controlled recovery help ensure that resource consumption triggered by an incident is bounded and managed rather than left unbounded.

none

Mandating tested continuity procedures that preserve or replace resource-limiting controls prevents an attacker from exploiting the absence of throttling mechanisms during an outage.

References