Home › Intelligence › Brief
VULNERABILITY BRIEF🟠 High Vulnerability

Path Traversal in Ruby on Rails Action View (CVE‑2019‑5418) Enables File Disclosure

A Rails Action View vulnerability (CVE‑2019‑5418) lets attackers craft Accept headers to render arbitrary server files. The issue affects all pre‑5.2.3 releases and underscores the need for robust access‑control validation and audit‑ready logging for compliance teams.

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 nvd.nist.gov
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
2 sector(s)
✅
Actions
4 recommended
📰
Source
nvd.nist.gov

Path Traversal in Ruby on Rails Action View (CVE‑2019‑5418) Enables File Disclosure

What It Is — Ruby on Rails’ Action View component mishandles specially‑crafted Accept headers combined with render file: calls, allowing an attacker to traverse directories and render arbitrary files from the server’s filesystem.

Exploitability — Publicly disclosed; proof‑of‑concept code exists; CVSS v3.1 base score 7.5 (High). No known active exploit campaigns, but the vulnerability is trivial to trigger on unpatched installations.

Affected Products — Ruby on Rails (all versions prior to 5.2.3, 6.0.0‑rc1).

Why It Matters for Trust & Control Assurance

  • Access‑control hygiene – The flaw bypasses normal file‑access controls, highlighting the need for strict validation of user‑supplied paths and headers.
  • Continuous evidence – Detecting unauthorized file reads requires logging of render calls and file‑access events, feeding into a defensible audit trail.
  • Framework alignment – Remediating this issue satisfies the Access Control control objective on the Verisq Common Framework, which maps to many standards (e.g., NIST CSF 2.0 Identify‑Asset Management).

Recommended Actions

  • Upgrade Rails to 5.2.3 or later (or the latest 6.x release).
  • Review code for any custom render file: usage and enforce whitelist‑based path validation.
  • Enable detailed logging for Action View rendering and monitor for anomalous file‑access patterns.
  • Conduct a rapid control‑mapping exercise to confirm that the “Access Control – File Integrity” objective is evidenced in your compliance artifacts.

Source: CISA KEV – CVE‑2019‑5418

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2019-5418 ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Misconfigurations are control gaps in disguise.

Verisq AI Trust Operations turns findings like this into mapped controls with continuous evidence, keeping your audit readiness current instead of point-in-time.

Map your controls with Verisq AI Trust Operations →