CVE-2018-3760

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 27% (97th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 27%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

There is an information leak vulnerability in Sprockets. Versions Affected: 4.0.0.beta7 and lower, 3.7.1 and lower, 2.12.4 and lower. Specially crafted requests can be used to access files that exists on the filesystem that is outside an application's root directory, when the Sprockets server is used in production. All users running an affected release should either upgrade or use one of the work arounds immediately.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
54
EG Risk 54/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
27%
EPSS %ILE
97th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

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

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 26, 2018

Last Modified

November 21, 2024

References (14)

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrh-postgresql95-postgresql-pglogical-0:1.2.1-2.el7cf2018-09-26redhat
redhatrh-ruby23-rubygem-redhat_access_cfme-0:2.0.3-1.el7cf2018-09-04redhat
redhatrh-ror42-rubygem-sprockets-0:3.2.0-5.el72018-07-24redhat
redhatrh-ror50-rubygem-sprockets-0:3.7.1-2.el72018-07-24redhat

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

(7 across 7 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-sprockets—
  • every version up to 3.7.0-1.1: fixed in 3.7.0-1.1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-sprockets—
  • every version up to 3.7.0-1.1: fixed in 3.7.0-1.1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-sprockets—
  • every version up to 3.7.0-1.1: fixed in 3.7.0-1.1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-sprockets—
  • every version up to 3.7.0-1.1: fixed in 3.7.0-1.1
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-sprockets2.12.3-1
  • every version up to 2.12.3-1+deb8u1: fixed in 2.12.3-1+deb8u1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-sprockets3.7.0-1
  • every version up to 3.7.0-1+deb9u1: fixed in 3.7.0-1+deb9u1
—
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
sprockets0.9.0 ... 2.9.4 (58 versions)
  • 3.0.0 up to 3.7.2: fixed in 3.7.2
  • 4.0.0.beta1 up to 4.0.0.beta8: fixed in 4.0.0.beta8
  • every version up to 2.12.5: fixed in 2.12.5
—

Weakness Classification(2)

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

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 130 total refreshes for this CVE.

  1. 2026-10-10 19:55 UTCEPSS rescore
  2. 2026-10-09 20:02 UTCEPSS rescore
  3. 2026-10-08 16:36 UTCEPSS rescore
  4. 2026-10-07 23:42 UTCEPSS rescore
  5. 2026-10-06 15:12 UTCEPSS rescore
  6. 2026-10-05 17:39 UTCEPSS rescore
  7. 2026-10-03 14:21 UTCEPSS rescore
  8. 2026-10-01 19:44 UTCEPSS rescore
  9. 2026-09-30 14:59 UTCEPSS rescore
  10. 2026-09-30 10:01 UTCEG score recompute
  11. 2026-09-29 01:08 UTCOSV refresh
  12. 2026-09-28 13:45 UTCEPSS rescore
  13. 2026-09-27 13:40 UTCEPSS rescore
  14. 2026-09-26 15:53 UTCEPSS rescore
  15. 2026-09-24 13:59 UTCEPSS rescore
  16. 2026-09-24 13:59 UTCEPSS rescore
  17. 2026-09-20 20:10 UTCEPSS rescore
  18. 2026-09-19 15:36 UTCEPSS rescore
  19. 2026-09-18 19:22 UTCEPSS rescore
  20. 2026-09-17 19:22 UTCEPSS rescore
  21. 2026-09-16 05:06 UTCEPSS rescore
  22. 2026-09-15 03:05 UTCEPSS rescore
  23. 2026-09-12 14:56 UTCEPSS rescore
  24. 2026-09-11 14:47 UTCEPSS rescore
  25. 2026-09-11 09:32 UTCEPSS rescore
Show 75 more
  1. 2026-09-09 05:47 UTCOSV refresh
  2. 2026-09-07 15:57 UTCEPSS rescore
  3. 2026-09-06 13:43 UTCEPSS rescore
  4. 2026-09-05 15:24 UTCEPSS rescore
  5. 2026-09-04 13:56 UTCEPSS rescore
  6. 2026-09-04 05:02 UTCEPSS rescore
  7. 2026-09-02 14:07 UTCEPSS rescore
  8. 2026-09-01 13:49 UTCEPSS rescore
  9. 2026-08-28 21:36 UTCEPSS rescore
  10. 2026-08-27 14:21 UTCEPSS rescore
  11. 2026-08-26 14:42 UTCEPSS rescore
  12. 2026-08-25 13:44 UTCEPSS rescore
  13. 2026-08-22 14:07 UTCOSV refresh
  14. 2026-08-21 23:45 UTCEPSS rescore
  15. 2026-08-20 22:51 UTCEPSS rescore
  16. 2026-08-19 17:00 UTCEPSS rescore
  17. 2026-08-18 13:44 UTCEPSS rescore
  18. 2026-08-17 13:43 UTCEPSS rescore
  19. 2026-08-16 14:51 UTCEPSS rescore
  20. 2026-08-16 02:10 UTCEPSS rescore
  21. 2026-08-15 01:26 UTCEPSS rescore
  22. 2026-08-13 21:56 UTCEPSS rescore
  23. 2026-08-12 13:46 UTCEPSS rescore
  24. 2026-08-08 16:32 UTCEPSS rescore
  25. 2026-08-07 16:23 UTCEPSS rescore
  26. 2026-08-06 18:05 UTCOSV refresh
  27. 2026-08-06 13:42 UTCEPSS rescore
  28. 2026-08-05 19:13 UTCEPSS rescore
  29. 2026-08-02 02:23 UTCEPSS rescore
  30. 2026-08-01 04:12 UTCEPSS rescore
  31. 2026-07-30 16:24 UTCEPSS rescore
  32. 2026-07-28 15:32 UTCEPSS rescore
  33. 2026-07-26 14:51 UTCEPSS rescore
  34. 2026-07-26 14:51 UTCEPSS rescore
  35. 2026-07-25 14:14 UTCEPSS rescore
  36. 2026-07-24 14:14 UTCEPSS rescore
  37. 2026-07-24 14:14 UTCEPSS rescore
  38. 2026-07-23 14:15 UTCEPSS rescore
  39. 2026-07-23 01:36 UTCEG score recompute
  40. 2026-07-22 22:16 UTCEG score recompute▼ 1.50
  41. 2026-07-22 14:05 UTCEPSS rescore
  42. 2026-07-21 15:22 UTCEPSS rescore
  43. 2026-07-21 10:18 UTCOSV refresh
  44. 2026-07-20 17:04 UTCEPSS rescore
  45. 2026-07-20 17:04 UTCEPSS rescore
  46. 2026-07-19 14:28 UTCEPSS rescore
  47. 2026-07-19 02:26 UTCEPSS rescore
  48. 2026-07-19 02:26 UTCEPSS rescore
  49. 2026-07-16 16:59 UTCEPSS rescore
  50. 2026-07-16 16:59 UTCEPSS rescore
  51. 2026-07-15 16:55 UTCEPSS rescore
  52. 2026-07-15 16:55 UTCEPSS rescore
  53. 2026-07-15 01:56 UTCEPSS rescore
  54. 2026-07-15 01:56 UTCEPSS rescore
  55. 2026-07-13 22:27 UTCEPSS rescore
  56. 2026-07-13 22:26 UTCEPSS rescore
  57. 2026-07-13 06:10 UTCEPSS rescore
  58. 2026-07-12 05:43 UTCEPSS rescore
  59. 2026-07-11 08:24 UTCEPSS rescore
  60. 2026-07-09 19:06 UTCEPSS rescore
  61. 2026-07-08 15:11 UTCEPSS rescore
  62. 2026-07-06 16:24 UTCEPSS rescore
  63. 2026-07-06 16:24 UTCEPSS rescore
  64. 2026-07-05 02:27 UTCEPSS rescore
  65. 2026-07-04 06:28 UTCEPSS rescore
  66. 2026-07-04 06:28 UTCEPSS rescore
  67. 2026-07-04 05:56 UTCOSV refresh
  68. 2026-07-02 16:54 UTCEPSS rescore
  69. 2026-07-01 15:03 UTCEPSS rescore
  70. 2026-07-01 15:03 UTCEPSS rescore
  71. 2026-06-28 04:53 UTCEPSS rescore
  72. 2026-06-28 04:53 UTCEPSS rescore
  73. 2026-06-27 03:06 UTCEPSS rescore
  74. 2026-06-27 03:06 UTCEPSS rescore
  75. 2026-06-25 13:47 UTCEPSS rescore

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (2 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • GitHub PoCcyberharsh/Ruby-On-Rails-Path-Traversal-Vulnerability-CVE-2018-3760-
    Published Jun 24, 2020
    Open source ↗
  • Nucleihttp/cves/2018/CVE-2018-3760.yaml
    Published Apr 5, 2020

    Ruby On Rails - Local File Inclusion

    Open source ↗
  • GitHub PoCmpgn/CVE-2018-3760
    Published Oct 21, 2019

    Rails Asset Pipeline Directory Traversal Vulnerability

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Same product

1 shown

Debian:11:ruby-sprockets

Same vendor

1 shown

redhat:RHSA-2018:2561

Frequently asked(5)

What is CVE-2018-3760?
CVE-2018-3760 is a high vulnerability published on June 26, 2018. There is an information leak vulnerability in Sprockets. Versions Affected: 4.0.0.beta7 and lower, 3.7.1 and lower, 2.12.4 and lower. Specially crafted requests can be used to access files that exists on the filesystem that is outside an application's root directory, when the Sprockets server is…
When was CVE-2018-3760 disclosed?
CVE-2018-3760 was first published on June 26, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-3760 actively exploited?
CVE-2018-3760 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-3760?
CVE-2018-3760 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2018-3760?
A fix for CVE-2018-3760 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-3760

Explore →

Is Your Infrastructure Affected by CVE-2018-3760?

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

Book a Demo →Browse All CVEs