Active Storage: Possible local file disclosure in video previews and analysis
Published 12 Nov 2026 · Updated 12 Nov 2026
Is your project on an affected activestorage?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=8.1.0.beta1 <8.1.4.1
- Fixed in
- 8.1.4.1
bundle update --conservative activestorage # Gemfile: '>= 8.1.4.1'- Affected
- <8.0.5.2
- Fixed in
- 8.0.5.2
bundle update --conservative activestorage # Gemfile: '>= 8.0.5.2'Details
Impact
Active Storage's VideoPreviewer, VideoAnalyzer and AudioAnalyzer run ffmpeg and ffprobe on a blob's contents without restricting the input format, so FFmpeg selects a demuxer by probing the file. A blob created through a direct upload keeps the content type the client declared, so a client can store an HLS playlist under a video/* or audio/* type. When that blob is previewed or analyzed, the hls demuxer opens the file:// segments that the playlist names, and the preview image or the stored metadata could disclose a local media file that the application process can read and whose path the attacker knows.
Applications that accept uploads from untrusted users and generate video previews, or analyze video or audio attachments with FFmpeg, are affected.
Details
The fixed releases limit the formats FFmpeg may open to common audio and video containers, configured by the new config.active_storage.ffmpeg_allowed_formats setting. Files in other formats no longer preview or receive media metadata; the Active Storage CHANGELOG names some of them and shows how to add a format to the list.
Workarounds
Applications that cannot upgrade can stop Active Storage from running FFmpeg on uploaded files by removing ActiveStorage::Previewer::VideoPreviewer from config.active_storage.previewers, and ActiveStorage::Analyzer::VideoAnalyzer and ActiveStorage::Analyzer::AudioAnalyzer from config.active_storage.analyzers.
Releases
The fixed releases are available at the normal locations.
Patches for those who cannot upgrade at once:
- 8.1: https://github.com/rails/rails/commit/3b1f2627538dc597cd973530c08514a26c2b0282.patch
- 8.0: https://github.com/rails/rails/commit/69aff80d115bbb9d1e82fd6c6f2fd3ddeafb958b.patch
Credit
This issue was responsibly reported by HackerOne researcher w3rmut.
Is GHSA-3f4q-8x5m-76v8 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected activestorage, and gives you the command that fixes it.
More advisories for activestorage
- CriticalCVE-2026-122006Active Storage: Possible arbitrary file write and read in image analysis · 12 Nov 2026
- MediumCVE-2026-126084Active Storage: Unsigned Content-Type in GCS direct uploads with cache_control · 12 Nov 2026
- HighCVE-2026-126186Active Storage: Possible arbitrary file read and remote code execution in video previews, analysis and image processing · 10 Nov 2026
- MediumCVE-2026-126085Active Storage: Possible circumvention of file size limits in Active Storage direct uploads to Google Cloud Storage · 10 Nov 2026
- MediumCVE-2026-126074Active Storage: Possible DoS vulnerability in Active Storage filename handling · 10 Nov 2026
- MediumCVE-2026-126071Active Storage: Possible DoS vulnerability in Active Storage proxy mode via storage errors during streaming · 10 Nov 2026
References
- Linkgithub.com/rails/rails/security/advisories/GHSA-3f4q-8x5m-76v8
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-126188
- Linkgithub.com/rails/rails/commit/3b1f2627538dc597cd973530c08514a26c2b0282
- Linkgithub.com/rails/rails/commit/69aff80d115bbb9d1e82fd6c6f2fd3ddeafb958b
- Packagegithub.com/rails/rails
- Linkgithub.com/rails/rails/releases/tag/v8.0.5.2
- Linkgithub.com/rails/rails/releases/tag/v8.1.4.1
- Linkgithub.com/rubysec/ruby-advisory-db/blob/master/gems/activestorage/GHSA-3f4q-8x5m-76v8.yml
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.