Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 26.72% for the current model date.
BlackTreeCVE IntelligenceHackerOne · Sprockets
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | ruby-sprockets | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.7.0-1.1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | ruby-sprockets | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.7.0-1.1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | ruby-sprockets | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.7.0-1.1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | ruby-sprockets | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.7.0-1.1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| RubyGemssprockets | ECOSYSTEM: introduced 3.0.0; fixed 3.7.2 | 3.7.2 | OSV record ↗aggregator derived · 16 Feb 2024 |
| RubyGemssprockets | ECOSYSTEM: introduced 4.0.0.beta1; fixed 4.0.0.beta8 | 4.0.0.beta8 | OSV record ↗aggregator derived · 16 Feb 2024 |
| RubyGemssprockets | ECOSYSTEM: introduced 0; fixed 2.12.5 | 2.12.5 | OSV record ↗aggregator derived · 16 Feb 2024 |
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch availableThere 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.
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.
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
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.
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCommon Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 26 Jun 2018 · Last source change 16 Sept 2024, 18:39 UTC · CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Core structured fields are present and their contributing authorities are shown above.