Skip to content
vulnerability

CVE-2019-5418

7.5
High
KEV · Exploited in wildEPSS 99%Patch available

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.

exploited
Yes, in CISA KEV since 7 Jul 2025fix by 28 Jul 2025 (CISA deadline for US federal agencies)public exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 98.5%
Published 27 Mar 2019Analysed here 2 Nov 2026CVSS scored by CISA

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
server-sideruntimeWAF can block: yesAV · networkCWE-22· Path Traversal

Can a WAF block it? Yes. The attack uses specially crafted HTTP Accept headers to cause file content disclosure, which can be detected by matching unusual or malformed Accept header values that normal users do not send. A WAF rule can match specially crafted Accept headers. No tracked WAF vendor has published a rule for this CVE yet, so you would write it yourself.

What a custom rule would match: specially crafted Accept headers

Also consider: patch · custom WAF rule · canonical path validation

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopeunchangedconfidentialityhighintegritynoneavailabilitynone
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
common questions

Is CVE-2019-5418 being exploited?

Yes. CVE-2019-5418 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2019-5418?

CVE-2019-5418 is rated High with a CVSS score of 7.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2019-5418?

Yes. A fix has been recorded for CVE-2019-5418. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2019-5418 affect?

CVE-2019-5418 affects rubyonrails:rails, debian:debian_linux, redhat:cloudforms, opensuse:leap, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
rubyonrails:railsdebian:debian_linuxredhat:cloudformsopensuse:leapfedoraproject:fedoraredhat:software_collections
affected versions
Rails https://github.com/rails/rails
  • affected5.2.2.1
  • affected5.1.6.2
  • affected5.0.7.2
  • affected4.2.11.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Public exploit code: 1 on Exploit-DB · 1 Metasploit module · 12 GitHub proofs of concept · 1 Nuclei template

Exploit-DB
Metasploit
Nuclei
GitHub proofs of concept
+8 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
yes
technical impact
partial

Assessed by CISA 17 Jul 2025 (SSVC 2.0.3).

timeline

  1. 16 Mar 2019First public exploit or proof of concept
  2. 27 Mar 2019Published · 12 days later
  3. 7 Jul 2025Added to CISA KEV (exploited in the wild) · 2,293 days (about 6 years) later
  4. 17 Jul 2025CISA SSVC assessment: exploitation active · 10 days later
  5. 28 Jul 2025CISA remediation due date (US federal agencies) · 11 days later
  6. 21 Oct 2025CVE record last updated · 86 days (about 3 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later

also known as

GHSA-86g5-2wh3-gc9j
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
14 references in the CVE record: 6 advisories, 1 exploit, 7 links
Show 6 more

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved