Quick answers
- Is CVE-2026-126074 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126074 being exploited in the wild.
- How severe is CVE-2026-126074?
- Medium severity, with a CVSS score of 4.3, published 10 November 2026.
- Which products and versions are affected?
- Rails Active Storage Prior to 8.1.4.1 and 8.0.5.2; activestorage (RubyGems) >= 8.1.0.beta1, < 8.1.4.1, ECOSYSTEM:introduced=8.1.0.beta1,fixed=8.1.4.1.
- Is there a fix for CVE-2026-126074?
- Yes. activestorage (RubyGems): upgrade to 8.1.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126074 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-126074?
- Check whether you run Rails Active Storage or activestorage (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- activestorage (RubyGems): upgrade to 8.1.4.1 or later
bundle update activestorage
Technical details
Active Storage passes user-supplied filenames unmodified to File.basename and File.extname, which raise ArgumentError when encountering NUL bytes. An authenticated attacker can upload a file with an embedded NUL byte to vulnerable databases (SQLite, MySQL/MariaDB), and each subsequent attempt to open, render, or create variants of the blob triggers an exception, resulting in persistent DoS. The fix sanitizes filename parts before processing to eliminate null bytes and invalid byte sequences.
Affected products
- Rails Active Storage Prior to 8.1.4.1 and 8.0.5.2
Identifiers
- CVE-2026-126074
- GHSA-p2pm-g2h6-7j5j
Timeline
- 2026-11-10: disclosed