CVE-2014-0130

CRITICALNVD 7.59.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.5 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.5 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2017-0180 (ENISA EUVD) · GHSA-6x85-j5j2-27jx (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 54%CVSS: 7.5Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Directory traversal vulnerability in actionpack/lib/abstract_controller/base.rb in the implicit-render implementation in Ruby on Rails before 3.2.18, 4.0.x before 4.0.5, and 4.1.x before 4.1.1, when certain route globbing configurations are enabled, allows remote attackers to read arbitrary files via a crafted request.

CVSS v3
7.5
EG Score
9.0CRITICALhigh confidence
EG Risk
74
EG Risk 74/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
54%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.5 HIGH.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
54% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2014-0130

Published

May 7, 2014

Last Modified

April 21, 2026

Advisory Details (3)

Auto-updated Nov 9, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2014-0130
Web page

PSIRT.COM — Product Security Incident Response Team

http://www.securityfocus.com/bid/67244

Vendor Advisories for CVE-2014-0130(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatruby193-rubygem-railties-1:3.2.17-1.el6sam2014-11-17redhat
redhatruby193-rubygem-actionpack-1:3.2.13-8.el6cf2014-06-30redhat
redhatruby193-rubygem-actionpack-1:3.2.8-5.5.el62014-05-15redhat
rubygemsactionpack @ 3.2.18 (fixes >= 3.0.0, < 3.2.18)—ghsa
rubygemsactionpack @ 4.0.5 (fixes >= 4.0.0, < 4.0.5)—ghsa
rubygemsactionpack @ 4.1.1 (fixes >= 4.1.0, < 4.1.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-actionpack-3.23.2.6-6, 3.2.6-6+deb7u1
  • every version up to 3.2.6-6+deb7u2: fixed in 3.2.6-6+deb7u2
—
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
actionpack4.1.0
  • 3.0.0 up to 3.2.18: fixed in 3.2.18
  • 4.0.0 up to 4.0.5: fixed in 4.0.5
  • 4.1.0 up to 4.1.1: fixed in 4.1.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 20× in last 7d / 67× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 1,189 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,089 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 23:57 UTCEchelonGraph re-scored
  2. 2026-11-12 23:57 UTCVendor advisory
  3. 2026-11-12 23:57 UTCGHSA enrichmentGHSA-6x85-j5j2-27jx · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-12 16:26 UTCEPSS rescoreEPSS 54% · 99th percentile
  5. 2026-11-12 00:09 UTCEchelonGraph re-scored
  6. 2026-11-12 00:09 UTCVendor advisory
  7. 2026-11-12 00:09 UTCGHSA enrichmentGHSA-6x85-j5j2-27jx · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-11-11 16:27 UTCEPSS rescoreEPSS 54% · 99th percentile
  9. 2026-11-11 00:22 UTCEchelonGraph re-scored
  10. 2026-11-11 00:22 UTCVendor advisory
  11. 2026-11-11 00:21 UTCGHSA enrichmentGHSA-6x85-j5j2-27jx · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-11-10 16:29 UTCEPSS rescoreEPSS 54% · 99th percentile
  13. 2026-11-10 00:33 UTCEchelonGraph re-scored
  14. 2026-11-10 00:33 UTCVendor advisory
  15. 2026-11-10 00:33 UTCGHSA enrichmentGHSA-6x85-j5j2-27jx · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-11-09 16:26 UTCEPSS rescoreEPSS 54% · 99th percentile
  17. 2026-11-09 00:46 UTCEchelonGraph re-scored
  18. 2026-11-09 00:46 UTCVendor advisory
  19. 2026-11-09 00:46 UTCGHSA enrichmentGHSA-6x85-j5j2-27jx · GitHub severity HIGH · GitHub CVSS 7.5
  20. 2026-11-08 00:58 UTCEchelonGraph re-scored
  21. 2026-11-08 00:58 UTCVendor advisory
  22. 2026-11-08 00:58 UTCGHSA enrichmentGHSA-6x85-j5j2-27jx · GitHub severity HIGH · GitHub CVSS 7.5
  23. 2026-11-07 16:28 UTCEPSS rescoreEPSS 54% · 99th percentile
  24. 2026-11-07 01:10 UTCEchelonGraph re-scored
  25. 2026-11-07 01:10 UTCVendor advisory
Show 75 more
  1. 2026-11-07 01:10 UTCGHSA enrichmentGHSA-6x85-j5j2-27jx · GitHub severity HIGH · GitHub CVSS 7.5
  2. 2026-11-06 16:27 UTCEPSS rescoreEPSS 54% · 99th percentile
  3. 2026-11-06 01:20 UTCEchelonGraph re-scored
  4. 2026-11-06 01:20 UTCVendor advisory
  5. 2026-11-06 01:20 UTCGHSA enrichmentGHSA-6x85-j5j2-27jx · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-05 16:27 UTCEPSS rescoreEPSS 54% · 99th percentile
  7. 2026-11-05 01:33 UTCEchelonGraph re-scored
  8. 2026-11-05 01:33 UTCVendor advisory
  9. 2026-11-05 01:33 UTCGHSA enrichmentGHSA-6x85-j5j2-27jx · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-11-04 16:27 UTCEPSS rescoreEPSS 54% · 99th percentile
  11. 2026-11-04 01:45 UTCEchelonGraph re-scored
  12. 2026-11-04 01:45 UTCVendor advisory
  13. 2026-11-04 01:45 UTCGHSA enrichmentGHSA-6x85-j5j2-27jx · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-11-03 16:31 UTCEPSS rescoreEPSS 54% · 98th percentile
  15. 2026-11-03 01:57 UTCEchelonGraph re-scored
  16. 2026-11-03 01:57 UTCVendor advisory
  17. 2026-11-03 01:57 UTCGHSA enrichmentGHSA-6x85-j5j2-27jx · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-11-02 02:10 UTCEchelonGraph re-scored
  19. 2026-11-02 02:10 UTCVendor advisory
  20. 2026-11-02 02:10 UTCGHSA enrichmentGHSA-6x85-j5j2-27jx · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-11-01 08:50 UTCGHSA enrichmentGHSA-6x85-j5j2-27jx · GitHub severity HIGH · GitHub CVSS 7.5
  22. 2026-11-01 08:50 UTCEchelonGraph re-scored
  23. 2026-11-01 02:21 UTCEchelonGraph re-scored
  24. 2026-11-01 02:21 UTCVendor advisory
  25. 2026-10-31 16:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  26. 2026-10-31 02:33 UTCEchelonGraph re-scored
  27. 2026-10-31 02:33 UTCVendor advisory
  28. 2026-10-30 16:27 UTCEPSS rescoreEPSS 54% · 98th percentile
  29. 2026-10-30 02:46 UTCEchelonGraph re-scored
  30. 2026-10-30 02:46 UTCVendor advisory
  31. 2026-10-29 16:27 UTCEPSS rescoreEPSS 54% · 98th percentile
  32. 2026-10-29 02:59 UTCEchelonGraph re-scored
  33. 2026-10-29 02:59 UTCVendor advisory
  34. 2026-10-28 16:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  35. 2026-10-28 03:11 UTCEchelonGraph re-scored
  36. 2026-10-28 03:11 UTCVendor advisory
  37. 2026-10-27 16:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  38. 2026-10-27 03:22 UTCEchelonGraph re-scored
  39. 2026-10-27 03:22 UTCVendor advisory
  40. 2026-10-26 03:32 UTCVendor advisory
  41. 2026-10-25 20:05 UTCEchelonGraph re-scored
  42. 2026-10-25 16:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  43. 2026-10-25 03:43 UTCEchelonGraph re-scored
  44. 2026-10-25 03:43 UTCVendor advisory
  45. 2026-10-24 16:27 UTCEPSS rescoreEPSS 54% · 98th percentile
  46. 2026-10-24 03:55 UTCEchelonGraph re-scored
  47. 2026-10-24 03:55 UTCVendor advisory
  48. 2026-10-23 16:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  49. 2026-10-23 04:08 UTCEchelonGraph re-scored
  50. 2026-10-23 04:08 UTCVendor advisory
  51. 2026-10-22 04:16 UTCEchelonGraph re-scored
  52. 2026-10-22 04:16 UTCVendor advisory
  53. 2026-10-21 16:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  54. 2026-10-21 04:29 UTCEchelonGraph re-scored
  55. 2026-10-21 04:29 UTCVendor advisory
  56. 2026-10-20 16:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  57. 2026-10-20 04:42 UTCEchelonGraph re-scored
  58. 2026-10-20 04:42 UTCVendor advisory
  59. 2026-10-19 16:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  60. 2026-10-19 04:53 UTCEchelonGraph re-scored
  61. 2026-10-19 04:53 UTCVendor advisory
  62. 2026-10-18 05:06 UTCEchelonGraph re-scored
  63. 2026-10-18 05:06 UTCVendor advisory
  64. 2026-10-17 16:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  65. 2026-10-17 05:19 UTCEchelonGraph re-scored
  66. 2026-10-17 05:19 UTCVendor advisory
  67. 2026-10-16 16:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  68. 2026-10-16 05:31 UTCEchelonGraph re-scored
  69. 2026-10-16 05:31 UTCVendor advisory
  70. 2026-10-15 16:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  71. 2026-10-15 05:41 UTCEchelonGraph re-scored
  72. 2026-10-15 05:41 UTCVendor advisory
  73. 2026-10-14 16:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  74. 2026-10-14 05:51 UTCEchelonGraph re-scored
  75. 2026-10-14 05:51 UTCVendor advisory

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoComarkurt/cve-2014-0130
    Published May 8, 2014

    cve-2014-0130 rails directory traversal vuln

    Open source ↗

Frequently asked(6)

What is CVE-2014-0130?
CVE-2014-0130 is a critical-severity vulnerability; its CVE record was published on May 7, 2014. Directory traversal vulnerability in actionpack/lib/abstract_controller/base.rb in the implicit-render implementation in Ruby on Rails before 3.2.18, 4.0.x before 4.0.5, and 4.1.x before 4.1.1, when certain route globbing configurations are enabled, allows remote attackers to read arbitrary files…
When was CVE-2014-0130 made public?
CVE-2014-0130 was made public on May 6, 2014: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on May 7, 2014. EchelonGraph's copy of the record carries a last-modified date of April 21, 2026; the record at its source may have been updated since.
Is CVE-2014-0130 actively exploited?
Yes. CISA added CVE-2014-0130 to the Known Exploited Vulnerabilities catalog on March 25, 2022, affecting Rails Ruby on Rails. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2014-0130?
CVE-2014-0130 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2014-0130?
CVE-2014-0130 affects Rails Ruby on Rails. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2014-0130?
A fix for CVE-2014-0130 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2014-0130 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2014-0130

Explore →

Is Your Infrastructure Affected by CVE-2014-0130?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.