rubygems package report

Is css_parser safe?

2 known vulnerabilities, worst severity HIGH.

cvss
8.9

how bad it is if exploited, out of 10

epss
0.40%

chance of exploitation in the next 30 days

xyz score
3.3

CyberXYZ composite, out of 10

fig. 01 — GHSA-9pmc-p236-855h, the advisory selected below

// advisories

GHSA-9pmc-p236-855h

HIGHCVE-2026-53727

CssParser::Parser#readremotefile (and therefore loaduri!, and the @import-following branch of addblock!) issues HTTP/HTTPS requests against any host, port and URI it is handed, with no scheme allowlist, no host / IP filtering, and no protection against link-local, loopback or RFC‑1918 addresses. Location: redirects are followed recursively back into the same function, which also services file:// U

Affected
< 3.0.0
Fixed in
3.0.0
Weakness
CWE-918
Published
2026-07-09
Source
github

GHSANVDMITREreferencereferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so rubygems packages are not covered.

Checked 2026-09-22 at 01:39 UTC. The most recent advisory here was published 2026-07-09. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is css_parser safe? rubygems package security report | CyberXYZ