Skip to main content
VulnerabilityPublished

CVE-2026-126186: rails · Reliance on File Name or Extension of Externally-Supplied File

Affects railsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 8.1.4.1 or 8.0.5.2 soon.

Data as of 10 Nov 2026, 21:34 UTC

CVSS 3.1 base score
8.8High
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.18.8
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:H/I:H/A:H

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 Rails to version 8.1.4.1 or 8.0.5.2 or later, where this vulnerability is fixed. No other specific mitigations are indicated by the vendor advisory. Applications should avoid using vulnerable Rails versions when accepting untrusted uploads for media processing.

Description

A vulnerability in Rails Active Storage prior to versions 8.1.4.1 and 8.0.5.2 allows attackers who control uploaded filenames to influence file processing by ffprobe, ffmpeg, and ImageMagick. This can lead to disclosure of files or remote code execution if certain conditions are met, such as using an FFmpeg build with AviSynth support. The issue is fixed in versions 8.1.4.1 and 8.0.5.2.

References

Community reviews

Loading reviews…