Is css_parser 1.2 vulnerable?

RubyGems · 6 releases from 1.2.1 to 1.2.6 · latest css_parser is 3.4.0 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. css_parser 1.2.6, the last 1.2 release, is affected by 2 known security advisories (1 high, 1 medium), including CVE-2026-53727, CVE-2026-44312. Upgrade to 3.0.0 or later to fix all of them.

Upgrade with:bundle update --conservative css_parser # Gemfile: '>= 3.0.0'

Is your project on an affected css_parser?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting css_parser 1.2.6

  • HighCVE-2026-53727GHSA-9pmc-p236-855h9 Jul 2026

    Ruby CSS Parser: SSRF and Local File Disclosure in `CssParser::Parser#read_remote_file`

    Affected
    <3.0.0
    Fixed in
    3.0.0
  • MediumCVE-2026-44312GHSA-ff6c-w6qf-7xqc7 May 2026

    CSS Parser: Improper Certificate Validation allows MITM injection of remote CSS content

    Affected
    >=2.0.0 <2.1.0 · <1.22.0
    Fixed in
    1.22.0, 2.1.0

Every css_parser 1.2.x release

Affected: 1.2.1 to 1.2.6. Latest css_parser: 3.4.0.

VersionKnown advisories
css_parser 1.2.6CVE-2026-53727, CVE-2026-44312
css_parser 1.2.5CVE-2026-53727, CVE-2026-44312
css_parser 1.2.4CVE-2026-53727, CVE-2026-44312
css_parser 1.2.3CVE-2026-53727, CVE-2026-44312
css_parser 1.2.2CVE-2026-53727, CVE-2026-44312
css_parser 1.2.1CVE-2026-53727, CVE-2026-44312

Which of your client projects are still on css_parser 1.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact css_parser version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other css_parser versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.