Skip to main content
VulnerabilityPublished

CVE-2026-126074: rails · Uncaught Exception

Affects railsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 8.1.4.1 or 8.0.5.2 when convenient.

Data as of 10 Nov 2026, 21:07 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.14.3
Patch
Available – fixed in 8.1.4.1, 8.0.5.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade rails to 8.1.4.1 or 8.0.5.2.

Affected software

ProductAffectedFixed in
railsrailsAffected
  • >=8.1 <8.1.4.1
Fixed in
  • 8.1.4.1
railsrailsAffected
  • <8.0.5.2
Fixed in
  • 8.0.5.2

AI-suggested

Upgrade Ruby on Rails Active Storage to version 8.1.4.1 or 8.0.5.2 or later, where this issue is fixed. No other mitigation is required as the fix addresses the root cause.

Description

A vulnerability in Ruby on Rails Active Storage prior to versions 8.1.4.1 and 8.0.5.2 allows an uncaught exception due to NUL bytes in uploaded filenames. This can cause persistent denial of service (DoS) on pages displaying affected attachments until the filename is corrected or the blob is purged. PostgreSQL users are not affected as it rejects such rows.

References

Community reviews

Loading reviews…