cve.bz

CVE-2026-126188 Active Storage: Possible local file disclosure in Active Storage video previews and analysis

3.7 lowEPSS 0.3%Fix available

Low (3.7) in rails rails. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in activestorage 8.0.5.2, 8.1.4.1.

On this page
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.

Severity

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 21st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-126188 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126188?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126188?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126188 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126188

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126188](https://cve.bz/cve/badge/CVE-2026-126188.svg)](https://cve.bz/cve/CVE-2026-126188)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126188"><img src="https://cve.bz/cve/badge/CVE-2026-126188.svg" alt="CVE-2026-126188"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
rails>= 8.1, < 8.1.4.1
rails< 8.0.5.2

Fix and patched versions

  • activestorage (RubyGems): fixed in 8.1.4.1, 8.0.5.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-3f4q-8x5m-76v8RubyGemsactivestorage>=8.1.0.beta1 <8.1.4.18.1.4.1
GHSA-3f4q-8x5m-76v8RubyGemsactivestorage<8.0.5.28.0.5.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14railsno fix listedDEBIAN-CVE-2026-126188
Ubuntu24.04:LTS, 26.04:LTS, 26.10 and 4 morerailsno fix listedUBUNTU-CVE-2026-126188

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON