Skip to content
Noroxi
CVE-2019-5418· NVD / CVE Program· CNA hackerone

There is a File Content Disclosure vulnerability in Action View <5.2.2.1, <5.1.6.2, <5.0.7.2, <4.2.11.1 and v3 where specially crafted accep

Noroxi assessment

Priority: Now (action score 90/100)

  • CISA has confirmed exploitation in the wild (Jul 7, 2025). Remediation deadline for US federal agencies: Jul 28, 2025.
  • A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
  • Probability of exploitation in the next 30 days: 98.5% (FIRST EPSS); higher than 99.9% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: rails (Debian:12) 2:5.2.2.1+dfsg-1; rails (Debian:8) 2:4.1.8-1+deb8u5; rubygem-actionpack-5_1 (openSUSE:Leap 15.0) 5.1.4-lp150.2.3.1.

Patch today or shut off access. Upgrade to rails (Debian:12) 2:5.2.2.1+dfsg-1; rails (Debian:8) 2:4.1.8-1+deb8u5; rubygem-actionpack-5_1 (openSUSE:Leap 15.0) 5.1.4-lp150.2.3.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS

There is a File Content Disclosure vulnerability in Action View <5.2.2.1, <5.1.6.2, <5.0.7.2, <4.2.11.1 and v3 where specially crafted accept headers can cause contents of arbitrary files on the target system's filesystem to be exposed.

HighCVSS 7.5 · v3.1KEVWeaponized Fix available
Published
Mar 27, 2019
Updated
Jun 16, 2026
EPSS
98.5% · 99th percentile

Report tools

JSON

Action score

90

Now

Patch today or shut off access.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
30 / 30 · Listed
EPSS
30 / 30 · 98.5%

CISA SSVC decision

Exploitation
active
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Jul 7, 2025. That signals real attacks, not theory.

Remediation deadline for US federal agencies: Jul 28, 2025.

Get told when this record changes

  • In CISA KEV: exploitation in the wild confirmed
  • Weaponized exploit exists
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2019-5418

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
rubyonrailsrails
debiandebian linux
redhatcloudforms
opensuseleap
fedoraprojectfedora
redhatsoftware collections

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux8.0
  • fedoraproject fedora30
  • opensuse leap15.0
  • redhat cloudforms4.6
  • redhat cloudforms4.7
  • redhat software collections1.0
  • rubyonrails rails5.2.0 and later · before 5.2.2.1
  • rubyonrails rails5.1.0 and later · before 5.1.6.2
  • rubyonrails rails5.0.0 and later · before 5.0.7.2
  • rubyonrails rails3.0.0 and later · before 4.2.11.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

  • Rails https://github.com/rails/rails

    • 5.2.2.1, 5.1.6.2, 5.0.7.2, 4.2.11.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12railsbefore 2:5.2.2.1+dfsg-12:5.2.2.1+dfsg-1
Debian:8railsbefore 2:4.1.8-1+deb8u52:4.1.8-1+deb8u5
openSUSE:Leap 15.0rubygem-actionpack-5_1before 5.1.4-lp150.2.3.15.1.4-lp150.2.3.1
openSUSE:Leap 15.1rmt-serverbefore 2.6.5-lp151.2.18.22.6.5-lp151.2.18.2
openSUSE:Leap 15.2rmt-serverbefore 2.6.5-lp152.2.3.12.6.5-lp152.2.3.1
openSUSE:Tumbleweedrubygem-actioncable-6.0before 6.0.4.4-1.16.0.4.4-1.1
openSUSE:Tumbleweedrubygem-actionmailbox-6.0before 6.0.4.4-1.16.0.4.4-1.1
openSUSE:Tumbleweedrubygem-actionmailer-6.0before 6.0.4.4-1.16.0.4.4-1.1
openSUSE:Tumbleweedrubygem-actionpack-6.0before 6.0.4.4-1.16.0.4.4-1.1
openSUSE:Tumbleweedrubygem-actiontext-6.0before 6.0.4.4-1.16.0.4.4-1.1
openSUSE:Tumbleweedrubygem-actionview-6.0before 6.0.4.4-1.16.0.4.4-1.1
openSUSE:Tumbleweedrubygem-activejob-6.0before 6.0.4.4-1.16.0.4.4-1.1
openSUSE:Tumbleweedrubygem-activemodel-6.0before 6.0.4.4-1.16.0.4.4-1.1
openSUSE:Tumbleweedrubygem-activerecord-6.0before 6.0.4.4-1.16.0.4.4-1.1
openSUSE:Tumbleweedrubygem-activestorage-6.0before 6.0.4.4-1.16.0.4.4-1.1
openSUSE:Tumbleweedrubygem-activesupport-6.0before 6.0.4.4-1.16.0.4.4-1.1
openSUSE:Tumbleweedrubygem-rails-6.0before 6.0.4.4-1.16.0.4.4-1.1
openSUSE:Tumbleweedrubygem-railties-6.0before 6.0.4.4-1.16.0.4.4-1.1
Red Hat:cloudforms_managementengine:5.10::el7ansible-towerbefore 0:3.4.3-1.el7at0:3.4.3-1.el7at
Red Hat:cloudforms_managementengine:5.10::el7ansible-tower-serverbefore 0:3.4.3-1.el7at0:3.4.3-1.el7at
Red Hat:cloudforms_managementengine:5.10::el7ansible-tower-setupbefore 0:3.4.3-1.el7at0:3.4.3-1.el7at
Red Hat:cloudforms_managementengine:5.10::el7ansible-tower-uibefore 0:3.4.3-1.el7at0:3.4.3-1.el7at
Red Hat:cloudforms_managementengine:5.10::el7ansible-tower-venv-ansiblebefore 0:3.4.3-1.el7at0:3.4.3-1.el7at
Red Hat:cloudforms_managementengine:5.10::el7ansible-tower-venv-towerbefore 0:3.4.3-1.el7at0:3.4.3-1.el7at

+34

Other highest-scoring records for the same primary product.

  • CVE-2016-0752Directory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, anKEV
    89Now
  • CVE-2019-5420A remote code execution vulnerability in development mode Rails <5.2.2.1, <6.0.0.beta3 can allow an attacker to guess the automatically gene
    66This week
  • CVE-2020-8163The is a code injection vulnerability in versions of Rails prior to 5.0.1 that wouldallow an attacker who controlled the `locals` argument o
    60This week

Published before and after this one in the same product

  • ← EarlierCVE-2018-16476Nov 30, 2018 · A Broken Access Control vulnerability in Active Job versions >= 4.2.0 allows an attacker to craft user input which can cause Active Job to d
    31Monitor
  • ← EarlierCVE-2018-16477Nov 30, 2018 · A bypass vulnerability in Active Storage >= 5.2.0 for Google Cloud Storage and Disk services allow an attacker to modify the `content-dispos
    26Monitor
  • Later →CVE-2019-5419Mar 27, 2019 · There is a possible denial of service vulnerability in Action View (Rails) <5.2.2.1, <5.1.6.2, <5.0.7.2, <4.2.11.1 where specially crafted a
    33Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:rails2:5.2.2.1+dfsg-1 · Debian:12Package registry (OSV)
opensuse:rmt-server2.6.5-lp152.2.3.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:rubygem-actioncable-6.06.0.4.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rubygem-actionmailbox-6.06.0.4.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rubygem-actionmailer-6.06.0.4.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rubygem-actionpack-5_15.1.4-lp150.2.3.1 · openSUSE:Leap 15.0Package registry (OSV)
opensuse:rubygem-actionpack-6.06.0.4.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rubygem-actiontext-6.06.0.4.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rubygem-actionview-6.06.0.4.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rubygem-activejob-6.06.0.4.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rubygem-activemodel-6.06.0.4.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rubygem-activerecord-6.06.0.4.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rubygem-activestorage-6.06.0.4.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:ansible-tower0:3.4.3-1.el7at · Red Hat:cloudforms_managementengine:5.10::el7Package registry (OSV)
red hat:ansible-tower-server0:3.4.3-1.el7at · Red Hat:cloudforms_managementengine:5.10::el7Package registry (OSV)
red hat:ansible-tower-setup0:3.4.3-1.el7at · Red Hat:cloudforms_managementengine:5.10::el7Package registry (OSV)
red hat:ansible-tower-ui0:3.4.3-1.el7at · Red Hat:cloudforms_managementengine:5.10::el7Package registry (OSV)
red hat:ansible-tower-venv-ansible0:3.4.3-1.el7at · Red Hat:cloudforms_managementengine:5.10::el7Package registry (OSV)
red hat:ansible-tower-venv-tower0:3.4.3-1.el7at · Red Hat:cloudforms_managementengine:5.10::el7Package registry (OSV)
red hat:cfme0:5.10.3.3-1.el7cf · Red Hat:cloudforms_managementengine:5.10::el7Package registry (OSV)
red hat:cfme-amazon-smartstate0:5.10.3.3-1.el7cf · Red Hat:cloudforms_managementengine:5.10::el7Package registry (OSV)
red hat:cfme-appliance0:5.10.3.3-1.el7cf · Red Hat:cloudforms_managementengine:5.10::el7Package registry (OSV)
red hat:cfme-appliance-common0:5.10.3.3-1.el7cf · Red Hat:cloudforms_managementengine:5.10::el7Package registry (OSV)
red hat:cfme-appliance-debuginfo0:5.10.3.3-1.el7cf · Red Hat:cloudforms_managementengine:5.10::el7Package registry (OSV)
red hat:cfme-appliance-tools0:5.10.3.3-1.el7cf · Red Hat:cloudforms_managementengine:5.10::el7Package registry (OSV)
RubyGems:actionview4.2.11.1Package registry (OSV)
RubyGems:actionview5.0.7.2Package registry (OSV)
RubyGems:actionview5.1.6.2Package registry (OSV)
RubyGems:actionview5.2.2.1Package registry (OSV)
suse:rmt-server2.6.5-3.3.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP2Package registry (OSV)

+1

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1
  • Exploit-DB entry ×1
  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×12

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entrywebapps2019-03-21
Metasploit moduleauxiliary/gather/rails_doubletap_file_readRuby On Rails File Content Disclosure ('doubletap')auxiliary—
Nuclei detection templateNuclei template CVE-2019-5418 —
Proof-of-concept repository on GitHubstars:2012019-03-16
Proof-of-concept repository on GitHubstars:52019-03-18
Proof-of-concept repository on GitHubstars:362019-03-19
Proof-of-concept repository on GitHubstars:1322019-03-23
Proof-of-concept repository on GitHubstars:32019-04-01
Proof-of-concept repository on GitHubstars:02019-10-04
Proof-of-concept repository on GitHubstars:02019-10-24
Proof-of-concept repository on GitHubstars:52019-11-19
Proof-of-concept repository on GitHubstars:22022-10-17

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-11 d
  2. Published
  3. CISA KEV+2294 d
  4. TodayOct 20, 2026+2764 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records