CVE-2019-5418
CVE-2019-5418 is a high-severity vulnerability (CVSS 3.1 base score 7.5). Rails Ruby on Rails contains a path traversal vulnerability in Action View. CISA added it to the Known Exploited Vulnerabilities catalog on 2025-07-07, with a remediation due date of 2025-07-28 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 98.5% probability of exploitation in the next 30 days, in the 99th percentile of scored CVEs.
Updated
- CVSS 3.1
- 7.5 HIGH
- EPSS
- 98.5% (99th pct)
- CISA KEV
- Exploited
- Published
- 2019-03-27
- Weakness
- CWE-22
Rails Ruby on Rails Path Traversal Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
https://web.archive.org/web/20190313201629/https://weblog.rubyonrails.org/2019/3/13/Rails-4-2-5-1-5-1-6-2-have-been-released/ ; https://nvd.nist.gov/vuln/detail/CVE-2019-5418
Description
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.
Key Findings
as of 2026-11-22- CISA added CVE-2019-5418 to the KEV catalog 2,294 days after its CVE record was published. The median for entries added in 2025 is 26 days.
- It is one of 3 Rails entries in the CISA KEV catalog, and the only one added in 2025.
- Its current EPSS score (98.5%) is higher than that of 85% of CISA KEV entries.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable yes, technical impact partial, 2025-07-17).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| Rails | Rails https://github.com/rails/rails | 5.2.2.1 5.1.6.2 5.0.7.2 4.2.11.1 |
References
12 linksVendor advisories
Exploits & PoCs
Mailing lists
Other references
Record Details
- Publicly disclosed
- 2019-03-13
- Published
- 2019-03-27
- Last updated
- 2025-10-21
- Assigner (CNA)
- hackerone
- Credited to
- -
More from Rails
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.