HighGHSA-86g5-2wh3-gc9jCVE-2019-5418

Path Traversal in Action View

Published 13 Mar 2019 · Updated 22 Oct 2025

Is your project on an affected actionview?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

actionviewRubyGems
Affected
>=5.2.0 <5.2.2.1
Fixed in
5.2.2.1
Update to the fixed version for your release line, for example:bundle update --conservative actionview # Gemfile: '>= 5.2.2.1'
actionviewRubyGems
Affected
>=4.0.0 <4.2.11.1
Fixed in
4.2.11.1
Update to the fixed version for your release line, for example:bundle update --conservative actionview # Gemfile: '>= 4.2.11.1'
actionviewRubyGems
Affected
>=5.1.0 <5.1.6.2
Fixed in
5.1.6.2
Update to the fixed version for your release line, for example:bundle update --conservative actionview # Gemfile: '>= 5.1.6.2'
actionviewRubyGems
Affected
>=5.0.0 <5.0.7.2
Fixed in
5.0.7.2
Update to the fixed version for your release line, for example:bundle update --conservative actionview # Gemfile: '>= 5.0.7.2'

Details

File Content Disclosure in Action View

Impact ------ There is a possible file content disclosure vulnerability in Action View. Specially crafted accept headers in combination with calls to render file: can cause arbitrary files on the target server to be rendered, disclosing the file contents.

The impact is limited to calls to render which render file contents without a specified accept format. Impacted code in a controller looks something like this:

class UserController < ApplicationController 
  def index 
    render file: "#{Rails.root}/some/file" 
  end 
end 

Rendering templates as opposed to files is not impacted by this vulnerability.

All users running an affected release should either upgrade or use one of the workarounds immediately.

Releases -------- The 6.0.0.beta3, 5.2.2.1, 5.1.6.2, 5.0.7.2, and 4.2.11.1 releases are available at the normal locations.

Workarounds ----------- This vulnerability can be mitigated by specifying a format for file rendering, like this:

class UserController < ApplicationController 
  def index 
    render file: "#{Rails.root}/some/file", formats: [:html] 
  end 
end 

In summary, impacted calls to render look like this:

render file: "#{Rails.root}/some/file" 

The vulnerability can be mitigated by changing to this:

render file: "#{Rails.root}/some/file", formats: [:html] 

Other calls to render are not impacted.

Alternatively, the following monkey patch can be applied in an initializer:

$ cat config/initializers/formats_filter.rb 
# frozen_string_literal: true 

ActionDispatch::Request.prepend(Module.new do 
  def formats 
    super().select do |format| 
      format.symbol || format.ref == "*/*" 
    end 
  end 
end) 

Credits ------- Thanks to John Hawthorn <john@hawthorn.email> of GitHub

Is GHSA-86g5-2wh3-gc9j 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 actionview, and gives you the command that fixes it.

More advisories for actionview

  • MediumCVE-2026-126078Action View: Possible XSS vulnerability in highlight helper · 12 Nov 2026
  • MediumCVE-2026-126070Action View: Possible XSS vulnerability in strip_tags · 12 Nov 2026
  • MediumCVE-2026-126079Action View: Possible XSS vulnerability in text helpers · 12 Nov 2026
  • MediumCVE-2026-126069Action View: Possible XSS vulnerability in tag helpers · 12 Nov 2026
  • LowCVE-2026-33168Rails has a possible XSS vulnerability in its Action View tag helpers · 23 Mar 2026
  • MediumCVE-2023-23913rails-ujs vulnerable to DOM Based Cross-site Scripting contenteditable HTML Elements · 9 Jun 2023
All 17 advisories for actionview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.