swift: In OpenStack Swift before 2.36.2 and 2.37.2, s3api middleware enters an infinite loop when processing a truncated aws...
CVE-2026-49017 is fixed in 7 products on 1 platform, first by python3-swift 2.37.1-0ubuntu2.1, released May 26, 2026. It is not reported as exploited. Patch Radar priority: Routine.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| python3-swift · Ubuntu 26.04.1 LTS (resolute) | 2.37.1-0ubuntu2.1 | python3-swift 2.37.1-0ubuntu2.1 | May 26, 2026 |
| swift · Debian 13.5 (trixie) | 2.35.1-0+deb13u2 | DEBIAN-CVE-2026-49017 | Jun 24, 2026 |
| swift · Debian 14 | 2.37.1-4 | DEBIAN-CVE-2026-49017 | Jun 24, 2026 |
| swift · Ubuntu 26.04.1 LTS (resolute) | 2.37.1-0ubuntu2.1 | swift 2.37.1-0ubuntu2.1 | May 26, 2026 |
| swift-account · Ubuntu 26.04.1 LTS (resolute) | 2.37.1-0ubuntu2.1 | swift-account 2.37.1-0ubuntu2.1 | May 26, 2026 |
| swift-container · Ubuntu 26.04.1 LTS (resolute) | 2.37.1-0ubuntu2.1 | swift-container 2.37.1-0ubuntu2.1 | May 26, 2026 |
| swift-object · Ubuntu 26.04.1 LTS (resolute) | 2.37.1-0ubuntu2.1 | swift-object 2.37.1-0ubuntu2.1 | May 26, 2026 |
| swift-object-expirer · Ubuntu 26.04.1 LTS (resolute) | 2.37.1-0ubuntu2.1 | swift-object-expirer 2.37.1-0ubuntu2.1 | May 26, 2026 |
| swift-proxy · Ubuntu 26.04.1 LTS (resolute) | 2.37.1-0ubuntu2.1 | swift-proxy 2.37.1-0ubuntu2.1 | May 26, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.