VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

css_parser: vulnerability history, versions and safety

css_parser is a package in the RubyGems ecosystem. Vulert records 2 vulnerabilities for it across 64 releases, from May 2026 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 09 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all css_parser vulnerabilities

Vulert verdict on css_parser 3.3.0 i

Updated on 23 Oct 2026

Good news: 3.3.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 67/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 3.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.3.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 09 Jul 2026 i
  • Highest CVSS 8.9 i
  • With no published fix 0 i
  • Stars 299 i
  • OpenSSF scorecard 2/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for css_parser, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.3.0 07 Oct 2026 none MIT — Details →
3.2.0 20 Sep 2026 none MIT — Details →
3.1.0 09 Sep 2026 none MIT — Details →
3.0.0 01 Jun 2026 none MIT — Details →
1.22.0 07 May 2026 H1 MIT Yes Details →
2.2.0 07 May 2026 H1 MIT Yes Details →
2.1.0 28 Apr 2026 H1 MIT Yes Details →
2.0.0 23 Feb 2026 H1 M1 MIT Yes Details →
1.21.1 09 Mar 2025 H1 M1 MIT Yes Details →
1.21.0 13 Dec 2024 H1 M1 MIT Yes Details →
1.20.0 12 Dec 2024 H1 M1 MIT Yes Details →
1.19.1 13 Oct 2024 H1 M1 MIT Yes Details →
1.19.0 23 Aug 2024 H1 M1 MIT Yes Details →
1.17.1 07 Apr 2024 H1 M1 MIT Yes Details →
1.17.0 06 Apr 2024 H1 M1 MIT Yes Details →
1.16.0 01 Sep 2023 H1 M1 MIT Yes Details →
1.15.0 29 Aug 2023 H1 M1 MIT Yes Details →
1.14.0 09 Jan 2023 H1 M1 MIT Yes Details →
1.13.0 29 Dec 2022 H1 M1 MIT Yes Details →
1.12.0 16 Sep 2022 H1 M1 MIT Yes Details →
1.11.0 14 Dec 2021 H1 M1 MIT Yes Details →
1.10.0 27 Jul 2021 H1 M1 MIT Yes Details →
1.9.0 04 Feb 2021 H1 M1 MIT Yes Details →
1.8.0 21 Jan 2021 H1 M1 MIT Yes Details →
1.7.1 01 Dec 2019 H1 M1 MIT Yes Details →
1.7.0 11 Feb 2019 H1 M1 MIT Yes Details →
1.6.0 08 Sep 2017 H1 M1 MIT Yes Details →
1.5.0 19 Apr 2017 H1 M1 MIT Yes Details →
1.5.0.pre2 14 Mar 2017 H1 M1 MIT Yes Details →
1.5.0.pre 13 Mar 2017 H1 M1 MIT Yes Details →
1.4.10 09 Mar 2017 H1 M1 MIT Yes Details →
1.4.9 22 Feb 2017 H1 M1 MIT Yes Details →
1.4.8 03 Feb 2017 H1 M1 MIT Yes Details →
1.4.7 29 Nov 2016 H1 M1 MIT Yes Details →
1.4.6 20 Oct 2016 H1 M1 MIT Yes Details →
1.4.5 28 Jun 2016 H1 M1 MIT Yes Details →
1.4.4 27 Jun 2016 H1 M1 MIT Yes Details →
1.4.3 27 Jun 2016 H1 M1 MIT Yes Details →
1.4.2 17 Jun 2016 H1 M1 MIT Yes Details →
1.4.1 21 Mar 2016 H1 M1 MIT Yes Details →
1.4.0 16 Mar 2016 H1 M1 MIT Yes Details →
1.3.7 22 Sep 2015 H1 M1 MIT Yes Details →
1.3.6 29 Jan 2015 H1 M1 MIT Yes Details →
1.3.5 24 Aug 2013 H1 M1 MIT Yes Details →
1.3.4 13 Mar 2013 H1 M1 MIT Yes Details →
1.3.3 13 Mar 2013 H1 M1 MIT Yes Details →
1.3.2 13 Mar 2013 H1 M1 MIT Yes Details →
1.3.1 13 Mar 2013 H1 M1 MIT Yes Details →
1.3.0 13 Mar 2013 H1 M1 MIT Yes Details →
1.2.6 12 Jan 2012 H1 M1 — Yes Details →
1.2.5 08 Sep 2011 H1 M1 — Yes Details →
1.2.4 08 Sep 2011 H1 M1 — Yes Details →
1.2.3 08 Sep 2011 H1 M1 — Yes Details →
1.2.2 07 Sep 2011 H1 M1 — Yes Details →
1.2.1 07 Sep 2011 H1 M1 — Yes Details →
1.1.9 01 Apr 2011 H1 M1 — Yes Details →
1.1.8 30 Mar 2011 H1 M1 — Yes Details →
1.1.7 29 Mar 2011 H1 M1 — Yes Details →
1.1.6 26 Mar 2011 H1 M1 — Yes Details →
1.1.5 21 Jan 2011 H1 M1 — Yes Details →
1.1.4 11 Nov 2010 H1 M1 — Yes Details →
1.1.3 03 Nov 2010 H1 M1 — Yes Details →
1.1.2 28 Oct 2010 H1 M1 — Yes Details →
1.1.1 26 Oct 2010 H1 M1 — Yes Details →
1.0.1 21 Feb 2010 H1 M1 — Yes Details →
1.0.0 22 Dec 2009 H1 M1 — Yes Details →
0.9.0 25 Jul 2009 H1 M1 — Yes Details →
0.9.1 25 Jul 2009 H1 M1 — Yes Details →

All 68 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for css_parser

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-53727: css_parser Package Suffers from SSRF and Local File Disclosure Vulnerability 8.9 high 3.0.0 09 Jul 2026
CVE-2026-44312: CSS Parser Improper Certificate Validation Leads to MITM CSS Injection 5.8 medium 2.1.0 07 May 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About css_parser

Is css_parser safe to use?

Vulert records 2 vulnerabilities for css_parser in RubyGems: 0 critical, 1 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is css_parser's Vulert package health score?

Vulert scores css_parser 67/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of css_parser affected?

No. 3.3.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of css_parser should I use?

3.3.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does css_parser have?

2 vulnerabilities are recorded for css_parser in the RubyGems ecosystem: 0 critical, 1 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new css_parser vulnerabilities disclosed?

2 vulnerabilities were recorded for css_parser in the last 12 months, and the oldest entry in this database dates to 07 May 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of css_parser are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor css_parser for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the css_parser version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.