Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 7.5 CISA Known Exploited Vulnerability

CVE-2019-5418

Rails Ruby on Rails Path Traversal Vulnerability

Rails Ruby on Rails

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.

CVSS
7.5
HIGH
EPSS
98.5%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
27 Mar 2019
CWE-22

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 7 July 2025. US federal agencies were required to remediate it by 28 July 2025.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 98.5%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

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

Frequently asked questions

Is CVE-2019-5418 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2019-5418.

What does CVE-2019-5418 affect?

CVE-2019-5418 affects Rails Ruby on Rails. 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.

How severe is CVE-2019-5418?

CVE-2019-5418 is rated HIGH with a CVSS base score of 7.5. EPSS puts the probability of exploitation in the next 30 days at 98.5%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 28 July 2025.

How should organisations respond to CVE-2019-5418?

Apply the vendor patch for Rails Ruby on Rails as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.