CVE-2019-5418
KEVRails Ruby on Rails Path Traversal Vulnerability
Description
Rails Ruby on Rails contains a path traversal 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.
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 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NPublishedMar 27, 2019
Last modifiedJun 17, 2026
Added to KEVJul 7, 2025
Remediation dueJul 28, 2025
References
- lists.opensuse.org/opensuse-security-announce/2019-05/msg00011.htmlMailing ListThird Party Advisory
- packetstormsecurity.com/files/152178/Rails-5.2.1-Arbitrary-File-Content-Disclosure.htmlExploitThird Party Advisory
- openwall.com/lists/oss-security/2019/03/22/1Mailing ListMitigation
- access.redhat.com/errata/RHSA-2019:0796Third Party Advisory
- access.redhat.com/errata/RHSA-2019:1147Third Party Advisory
- access.redhat.com/errata/RHSA-2019:1149Third Party Advisory
- access.redhat.com/errata/RHSA-2019:1289Third Party Advisory
- groups.google.com/forum/Permissions Required
- lists.debian.org/debian-lts-announce/2019/03/msg00042.htmlMailing ListThird Party Advisory
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Y43636TH4D6T46IC6N2RQVJTRFJAAYGA/Third Party Advisory
- weblog.rubyonrails.org/2019/3/13/Rails-4-2-5-1-5-1-6-2-have-been-released/Broken LinkPatch
- exploit-db.com/exploits/46585/ExploitThird Party Advisory
0 recent articles mention this CVE
77
Risk assessment · High
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 455 days
- CVSS
- 7.5 HIGH
- EPSS (30-day exploit probability)
- 98.5% · top 1% of all CVEs
- Weakness
- CWE-22
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
Recommended actions
- 1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.