sprockets (rubygems) has 2 known vulnerabilities, the worst rated HIGH. Upgrade to 4.0.0.beta8 or later to clear all of them. No malicious-package signal is recorded.
0 direct dependencies
none carry a known advisory
0 packages depend on it
dependents not yet indexed for this ecosystem
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so rubygems packages are not covered.
CVSS v3.0 base score out of 10
chance of exploitation in 30 days, 98th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-pr3h-jjhj-573x, the advisory selected below
Specially crafted requests can be used to access files that exist on the filesystem that is outside an application's root directory, when the Sprockets server…
Full advisory text at GitHub advisory or NVD.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CyberXYZ does not call a package safe in absolute terms. It records 2 known vulnerabilities for sprockets (rubygems), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 2 known vulnerabilities for sprockets (rubygems), the worst rated HIGH. They are GHSA-pr3h-jjhj-573x, GHSA-33pp-3763-mrfp.
4.0.0.beta8 or later clears every advisory recorded for sprockets (rubygems). Check the release you pick before installing it.
Search sprockets in CyberXYZ Check at https://cyberxyz.io/check?q=sprockets. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 11:15 UTC. The most recent advisory here was published 2018-06-20. Updated continuously from NVD, GHSA, OSV and CNA feeds.