How severe is CVE-2018-3760?

CVE-2018-3760 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-3760?

CVE-2018-3760 affects the following packages: sprockets (RubyGems), sprockets (RubyGems), sprockets (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2018-3760?

Update sprockets to version 3.7.2 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is CVE-2018-3760 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2018-3760, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-3760?

CVE-2018-3760 has an EPSS (Exploit Prediction Scoring System) score of 93.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2018-3760?

CVE-2018-3760 is classified as Path Traversal (CWE-22), Information Exposure (CWE-200). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2018-3760?

A Nuclei detection template exists for CVE-2018-3760, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2018-3760 published, and has it been updated?

CVE-2018-3760 was published on June 26, 2018 and was last updated on March 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

CVE-2018-3760

HIGH

Sprockets path traversal leads to information leak

Also known asGHSA-pr3h-jjhj-573x

Published

Jun 26, 2018

Updated

Mar 15, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

93.9%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

💎sprockets💎sprockets💎sprockets

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`sprockets`	≥ 3.0.0&&< 3.7.2	3.7.2
💎RubyGems	`sprockets`	≥ 4.0.0.beta1&&< 4.0.0.beta8	4.0.0.beta8
💎RubyGems	`sprockets`	all versions	2.12.5

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

There is an information leak vulnerability in Sprockets. Versions Affect…

github.comAwesomePocJun 2020

There is an information leak vulnerability in Sprockets. Versions Affect…

github.comGithubOct 2019

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-3760 in your stack?

O3 detects CVE-2018-3760 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works

CVSS Score

7.5/10

CVSS v3 base score

Vector breakdown

AV:Attack Vector

Network

AC:Attack Complexity

Low

PR:Privileges Required

None

UI:User Interaction