Is css_parser 1.3 vulnerable?
RubyGems · 8 releases from 1.3.0 to 1.3.7 · latest css_parser is 3.4.0 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. css_parser 1.3.7, the last 1.3 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.
bundle update --conservative css_parser # Gemfile: '>= 3.0.0'Is your project on an affected css_parser?
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.3.7
Ruby CSS Parser: SSRF and Local File Disclosure in `CssParser::Parser#read_remote_file`
- Affected
- <3.0.0
- Fixed in
- 3.0.0
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.3.x release
Affected: 1.3.0 to 1.3.7. Latest css_parser: 3.4.0.
| Version | Known advisories |
|---|---|
| css_parser 1.3.7 | CVE-2026-53727, CVE-2026-44312 |
| css_parser 1.3.6 | CVE-2026-53727, CVE-2026-44312 |
| css_parser 1.3.5 | CVE-2026-53727, CVE-2026-44312 |
| css_parser 1.3.4 | CVE-2026-53727, CVE-2026-44312 |
| css_parser 1.3.3 | CVE-2026-53727, CVE-2026-44312 |
| css_parser 1.3.2 | CVE-2026-53727, CVE-2026-44312 |
| css_parser 1.3.1 | CVE-2026-53727, CVE-2026-44312 |
| css_parser 1.3.0 | CVE-2026-53727, CVE-2026-44312 |
Which of your client projects are still on css_parser 1.3?
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.