# CVE-2026-126071: Active Storage: Possible DoS vulnerability in Active Storage proxy mode via storage errors during streaming


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-4v2w-w6g6-f8f8, UBUNTU-CVE-2026-126071

## What is CVE-2026-126071?

CVE-2026-126071 is a medium-severity vulnerability in rails, published on 10 Nov 2026. 

### Official description

Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. From 8.0 until 8.0.5.2 and 8.1.4.1, when Active Storage serves a file through its proxy controllers, ActiveStorage::Streaming#send_blob_stream handles an error from the storage service by calling head to send a 404 or 500 response. If the error occurs after the first chunk has been written, the response is already committed, and head replaces the response body while the server is still reading the original ActionController::Live buffer. That buffer is never closed, so the server thread handling the request blocks until the process restarts. Repeated failed downloads could exhaust the server's threads, possibly resulting in a DoS vulnerability. Applications are affected when they store files on a service that streams a download in several requests, such as Amazon S3, an S3-compatible service or Google Cloud Storage, and draw Active Storage's default routes. The proxy routes are drawn whether or not proxy mode is the default for the application. A file deleted while it is being served, or any other storage error partway through a download, triggers the condition. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime)

## Which versions are affected by CVE-2026-126071?

2 open source packages ship an affected version, including activestorage.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `activestorage` | RubyGems | From 8.0.0.beta1 | 8.0.5.2 |
| `activestorage` | RubyGems | From 8.1.0.beta1 | 8.1.4.1 |

## How do I fix CVE-2026-126071?

Upgrade activestorage to a fixed version for your release line: 8.0.5.2 or 8.1.4.1.

## Is CVE-2026-126071 being exploited?

There is no known exploitation of CVE-2026-126071 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126071 and fix it if it is affected.

What it is: CVE-2026-126071 is a medium-severity vulnerability in rails, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-126071 in the wild and no public exploit code.

Affected packages and fixed versions:
- activestorage (RubyGems): affected from 8.0.0.beta1; fixed in 8.0.5.2
- activestorage (RubyGems): affected from 8.1.0.beta1; fixed in 8.1.4.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126071/ (Markdown: https://insights.sbomify.com/CVE-2026-126071/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126071
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126071
- OSV: https://osv.dev/vulnerability/CVE-2026-126071

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126071/
Summaries are generated and may contain mistakes; the official description above is the record.