Active Storage: Possible local file disclosure in Active Storage video previews and analysis
- Exploited
- No known exploitation
- Fix
- Fixed in 8.1.4.1, 8.0.5.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 8.1.4.1, 8.0.5.2.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 38/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Active Storage's video preview and audio/video analysis features can be made to read local files. A remote attacker without logging in can upload a crafted file that causes a readable local media file to be disclosed, if the attacker knows its path.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. Prior to 8.0.5.2 and from 8.1 until 8.1.4.1, Active Storage's ActiveStorage::Previewer::VideoPreviewer, ActiveStorage::Analyzer::VideoAnalyzer, and ActiveStorage::Analyzer::AudioAnalyzer pass uploaded blob contents to FFmpeg without restricting the demuxer. A direct upload can retain a client-declared video/* or audio/* content type for an HLS playlist. FFmpeg content probing selects the hls demuxer, which opens attacker-named file:// segments when the blob is previewed or analyzed. Applications that accept untrusted uploads and generate video previews or analyze video or audio attachments can disclose a local media file readable by the application process when the attacker knows its path. This issue is fixed in versions 8.0.5.2 and 8.1.4.1.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach17/20Affects Ruby on Rails (a widely deployed server, runtime, framework or database)
- Severity3.7/10CVSS 3.7
- No patch0/5No signal
What would change the score
- Would score about 83 if added to CISA KEV
- Would score about 78 if CISA's SSVC rates exploitation active
- Would score about 43 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 8.1.4.1, 8.0.5.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126188 (Active Storage: Possible local file disclosure in Active Storage video previews and analysis), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-126188 (entry last updated 2026-11-10): Affected: - rails rails: from 8.1, fixed in 8.1.4.1; fixed in 8.0.5.2 Fixed versions: 8.1.4.1, 8.0.5.2. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-126188 is not listed as of cve.now's last read. This KEV status is for CVE-2026-126188 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/rails/rails/security/advisories/GHSA-3f4q-8x5m-76v8 - https://github.com/rails/rails/commit/3b1f2627538dc597cd973530c08514a26c2b0282 - https://github.com/rails/rails/commit/69aff80d115bbb9d1e82fd6c6f2fd3ddeafb958b - https://github.com/rails/rails/releases/tag/v8.0.5.2 - https://github.com/rails/rails/releases/tag/v8.1.4.1 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-126188 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-126188.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- rails rails
From 8.1 · fixed in 8.1.4.1; fixed in 8.0.5.2
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
Other links · 4
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126188
Is CVE-2026-126188 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-126188?
rails: from 8.1 before 8.1.4.1; before 8.0.5.2.Source: cve.now feed data
How do I fix CVE-2026-126188?
Upgrade to a fixed version: 8.1.4.1, 8.0.5.2.Source: cve.now feed data