CVE-2026-34827: Rack: Algorithmic-Complexity DoS in Rack::Multipart::Parser
Rack is a modular Ruby web server interface. From versions 3.0.0.beta1 to before 3.1.21, and 3.2.0 to before 3.2.6, Rack::Multipart::Parser#handle_mime_head parses quoted multipart parameters such as Content-Disposition: form-data; name="..." using repeated String#index searches combined with String#slice! prefix deletion. For escape-heavy quoted values, this causes super-linear processing. An unauthenticated attacker can send a crafted multipart/form-data request containing many parts with long backslash-escaped parameter values to trigger excessive CPU usage during multipart parsing. This results in a denial of service condition in Rack applications that accept multipart form data. This issue has been patched in versions 3.1.21 and 3.2.6.
Security readout for executives and security teams
Plain-English summary
This flaw can let an unauthenticated remote attacker make affected Rack-based Ruby applications consume excessive CPU while parsing specially formed multipart form requests. The likely business impact is service degradation or outage on applications that accept multipart form data, such as upload or form submission endpoints.
Executive priority
Treat as a high-priority availability risk for affected public Ruby applications. Patch exposed multipart-handling services promptly, with greatest urgency for unauthenticated upload or form endpoints supporting customer-facing operations.
Technical view
Rack::Multipart::Parser#handle_mime_head in affected Rack versions performs repeated string searches and prefix deletions while parsing quoted multipart parameters. Escape-heavy quoted values can trigger super-linear processing, causing algorithmic-complexity denial of service during multipart/form-data parsing.
Likely exposure
Exposure is most likely in Ruby applications using Rack versions 3.0.0.beta1 through before 3.1.21, or 3.2.0 through before 3.2.6, where the application accepts multipart/form-data requests. Internet-facing, unauthenticated upload or form endpoints are higher priority.
Exploitation context
The source bundle does not show KEV listing or cited evidence of active exploitation. The described attack is network reachable, low complexity, unauthenticated, and affects availability, not confidentiality or integrity.
Researcher notes
The key condition is parser reachability, not just dependency presence. Validate the exact Rack version loaded at runtime and whether multipart parsing occurs before authentication or request rejection. Evidence provided supports patched versions but does not establish active exploitation.
Mitigation direction
Upgrade Rack to 3.1.21, 3.2.6, or later patched versions.
Redeploy all services bundling an affected Rack version.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Inefficient Algorithmic Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.