CVE-2026-49017: In OpenStack Swift before 2.36.2 and 2.37.2, s3api middleware enters an infinite loop when processing a tru...
In OpenStack Swift before 2.36.2 and 2.37.2, s3api middleware enters an infinite loop when processing a truncated aws-chunked PUT request body. The StreamingInput class repeatedly appends an empty buffer and re-reads, causing the proxy-server worker handling the request to become permanently unresponsive with increasing CPU and memory consumption. An authenticated attacker can systematically exhaust all proxy-server workers, resulting in denial of service. The defect was introduced in Swift 2.36.0.
Security readout for executives and security teams
This flaw can let a logged-in user make OpenStack Swift proxy workers hang permanently while CPU and memory rise. If enough workers are consumed, object storage using the S3 API can become unavailable. The issue is denial of service, not data theft or code execution. Exposure is most likely in OpenStack Swift deployments running affected 2.36.x or 2.37.x builds with s3api middleware enabled and authenticated users able to send S3 PUT requests. The provided affected-version metadata also lists 2.35.1, but that conflicts with the stated 2.36.0 introduction. Treat as high priority for Swift-backed object storage, especially multi-tenant or externally reachable S3-compatible endpoints. The business risk is storage outage from authenticated abuse. Patch promptly, but do not classify it as confirmed active exploitation based on the provided evidence. Mitigation focus: Upgrade OpenStack Swift to 2.36.2, 2.37.2, or a vendor-supported fixed package.; Review the OpenStack patch references and downstream distribution advisories before rollout.; Prioritize environments exposing Swift s3api to tenants or external authenticated users..
Prepared
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-835: 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.
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-835 · source CWE mapping
Loop with Unreachable Exit Condition ('Infinite Loop')
Loop with Unreachable Exit Condition ('Infinite Loop') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.