VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

nokogiri: vulnerability history, versions and safety

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

i
64 vulnerabilities recorded C4 H28 M18 L14
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
14 in the last 12 months

Most recent disclosure 25 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all nokogiri vulnerabilities

Vulert verdict on nokogiri 1.19.4 i

Updated on 23 Oct 2026

Careful: 1.19.4 has 5 known vulnerabilities, and 5 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.19.4 — affected i
  • Vulnerabilities on record 64 over 8 years · 14 in the last year i
  • Latest disclosure 25 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 5 i
  • Stars 6,281 i
  • OpenSSF scorecard 6/10 i
  • Last release 4 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 22 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 nokogiri, 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
1.19.4 18 Jun 2026 H1 M2 MIT No Details →
1.19.3 27 Apr 2026 H1 M3 L7 MIT No Details →
1.19.2 19 Mar 2026 H2 M4 L7 MIT No Details →
1.19.1 16 Feb 2026 H2 M4 L7 MIT No Details →
1.19.0 28 Dec 2025 H2 M5 L7 MIT No Details →
1.18.10 15 Sep 2025 H2 M5 L7 MIT No Details →
1.18.9 21 Jul 2025 H2 M5 L7 MIT No Details →
1.18.8 21 Apr 2025 C1 H2 M5 L7 MIT No Details →
1.18.7 31 Mar 2025 C1 H2 M5 L8 MIT No Details →
1.18.6 24 Mar 2025 C1 H2 M5 L8 MIT No Details →
1.18.5 19 Mar 2025 C1 H2 M5 L8 MIT No Details →
1.18.4 14 Mar 2025 C1 H2 M5 L8 MIT No Details →
1.18.3 18 Feb 2025 C1 H3 M5 L8 MIT No Details →
1.18.2 19 Jan 2025 C1 H3 M5 L10 MIT No Details →
1.18.1 29 Dec 2024 C1 H3 M5 L10 MIT No Details →
1.18.0 25 Dec 2024 C1 H3 M5 L10 MIT No Details →
1.18.0.rc1 16 Dec 2024 C1 H3 M5 L10 MIT No Details →
1.17.2 12 Dec 2024 C1 H3 M5 L10 MIT No Details →
1.17.1 10 Dec 2024 C1 H3 M5 L10 MIT No Details →
1.17.0 08 Dec 2024 C1 H3 M5 L10 MIT No Details →
1.15.7 02 Dec 2024 C1 H3 M5 L10 MIT No Details →
1.16.8 02 Dec 2024 C1 H3 M5 L10 MIT No Details →
1.16.7 27 Jul 2024 C1 H3 M5 L10 MIT No Details →
1.16.6 13 Jun 2024 C1 H3 M5 L10 MIT No Details →
1.16.5 13 May 2024 C1 H3 M5 L10 MIT No Details →
1.16.4 10 Apr 2024 C1 H3 M5 L12 MIT No Details →
1.15.6 16 Mar 2024 C1 H3 M5 L12 MIT No Details →
1.16.3 15 Mar 2024 C1 H3 M5 L12 MIT No Details →
1.16.2 04 Feb 2024 C1 H3 M5 L12 MIT No Details →
1.16.1 03 Feb 2024 C1 H3 M6 L12 MIT No Details →
1.16.0 28 Dec 2023 C1 H3 M6 L12 MIT No Details →
1.16.0.rc1 13 Dec 2023 C1 H3 M5 L12 MIT No Details →
1.15.5 17 Nov 2023 C1 H3 M6 L12 MIT No Details →
1.15.4 11 Aug 2023 C1 H3 M6 L12 MIT No Details →
1.15.3 05 Jul 2023 C1 H3 M6 L12 MIT No Details →
1.15.2 24 May 2023 C1 H3 M6 L12 MIT No Details →
1.14.5 24 May 2023 C1 H3 M6 L12 MIT No Details →
1.15.1 19 May 2023 C1 H3 M6 L12 MIT No Details →
1.15.0 15 May 2023 C1 H3 M6 L12 MIT No Details →
1.14.4 11 May 2023 C1 H3 M6 L12 MIT No Details →
1.14.3 11 Apr 2023 C1 H3 M6 L12 MIT No Details →
1.14.2 13 Feb 2023 C1 H3 M7 L12 MIT No Details →
1.14.1 30 Jan 2023 C1 H3 M7 L12 MIT No Details →
1.14.0 12 Jan 2023 C1 H3 M7 L12 MIT No Details →
1.14.0.rc1 29 Dec 2022 C1 H3 M7 L12 MIT No Details →
1.13.10 08 Dec 2022 C1 H3 M7 L12 MIT No Details →
1.13.9 18 Oct 2022 C1 H4 M7 L12 MIT No Details →
1.13.8 23 Jul 2022 C1 H4 M8 L12 MIT No Details →
1.13.7 12 Jul 2022 C1 H3 M8 L12 MIT No Details →
1.13.6 08 May 2022 C1 H3 M8 L12 MIT No Details →
1.13.5 04 May 2022 C1 H4 M8 L12 MIT No Details →
1.13.4 11 Apr 2022 C1 H5 M8 L12 MIT No Details →
1.13.3 22 Feb 2022 C1 H9 M9 L12 MIT No Details →
1.13.2 21 Feb 2022 C1 H9 M9 L12 MIT No Details →
1.13.1 13 Jan 2022 C1 H11 M9 L12 MIT No Details →
1.13.0 06 Jan 2022 C1 H11 M9 L12 MIT No Details →
1.12.5 27 Sep 2021 C1 H11 M9 L12 MIT No Details →
1.12.4 29 Aug 2021 C1 H12 M9 L12 MIT No Details →
1.12.3 10 Aug 2021 C1 H12 M9 L12 MIT No Details →
1.12.2 04 Aug 2021 C1 H12 M9 L12 MIT No Details →
1.12.1 03 Aug 2021 C1 H12 M9 L12 MIT No Details →
1.12.0 02 Aug 2021 C1 H12 M9 L12 MIT No Details →
1.12.0.rc1 09 Jul 2021 C1 H12 M9 L12 MIT No Details →
1.11.7 03 Jun 2021 C1 H12 M9 L12 MIT No Details →
1.11.6 26 May 2021 C1 H12 M9 L12 MIT No Details →
1.11.5 20 May 2021 C1 H12 M9 L12 MIT No Details →
1.11.4 14 May 2021 C1 H12 M9 L12 MIT No Details →
1.11.3 07 Apr 2021 C1 H14 M11 L12 MIT No Details →
1.11.2 11 Mar 2021 C1 H14 M11 L12 MIT No Details →
1.11.1 06 Jan 2021 C1 H14 M11 L12 MIT No Details →
1.11.0 04 Jan 2021 C1 H14 M11 L12 MIT No Details →
1.11.0.rc4 29 Dec 2020 C1 H14 M12 L12 MIT No Details →
1.11.0.rc3 08 Sep 2020 C1 H14 M12 L12 MIT No Details →
1.10.10 06 Jul 2020 C1 H14 M12 L12 MIT No Details →
1.11.0.rc2 01 Apr 2020 C1 H14 M12 L12 MIT No Details →
1.10.9 01 Mar 2020 C1 H14 M12 L12 MIT No Details →
1.10.8 10 Feb 2020 C1 H14 M12 L12 MIT No Details →
1.11.0.rc1 03 Feb 2020 C1 H14 M12 L12 MIT No Details →
1.10.7 04 Dec 2019 C1 H15 M12 L12 MIT No Details →
1.10.6 04 Dec 2019 C1 H15 M12 L12 MIT No Details →
1.10.5 31 Oct 2019 C1 H15 M12 L12 MIT No Details →
1.10.4 11 Aug 2019 C1 H19 M12 L12 MIT No Details →
1.10.3 22 Apr 2019 C2 H19 M12 L12 MIT No Details →
1.10.2 25 Mar 2019 C3 H19 M12 L12 MIT No Details →
1.10.1 13 Jan 2019 C3 H19 M12 L12 MIT No Details →
1.10.0 04 Jan 2019 C3 H19 M12 L12 MIT No Details →
1.10.0.rc1 03 Jan 2019 C3 H19 M12 L12 MIT No Details →
1.9.1 18 Dec 2018 C3 H19 M12 L12 MIT No Details →
1.9.0 17 Dec 2018 C3 H19 M12 L12 MIT No Details →
1.9.0.rc1 10 Dec 2018 C3 H19 M12 L12 MIT No Details →
1.8.5 05 Oct 2018 C3 H19 M12 L12 MIT No Details →
1.8.4 04 Jul 2018 C3 H20 M12 L12 MIT No Details →
1.8.3 16 Jun 2018 C3 H20 M12 L12 MIT No Details →
1.8.2 29 Jan 2018 C3 H20 M12 L12 MIT No Details →
1.8.1 19 Sep 2017 C3 H21 M13 L12 MIT No Details →
1.8.0 05 Jun 2017 C3 H23 M13 L12 MIT No Details →
1.7.2 09 May 2017 C3 H23 M13 L12 MIT No Details →
1.7.1 20 Mar 2017 C3 H24 M13 L12 MIT No Details →
1.7.0.1 04 Jan 2017 C4 H24 M13 L12 MIT No Details →
1.7.0 27 Dec 2016 C4 H24 M13 L12 MIT No Details →
1.6.8.1 03 Oct 2016 C4 H24 M13 L12 — No Details →
1.6.8 07 Jun 2016 C4 H24 M13 L12 — No Details →
1.6.8.rc3 17 Feb 2016 C4 H25 M13 L12 — No Details →
1.6.7.2 20 Jan 2016 C4 H25 M13 L12 — No Details →
1.6.8.rc2 12 Jan 2016 C4 H25 M13 L12 — No Details →
1.6.8.rc1 17 Dec 2015 C4 H25 M13 L12 — No Details →
1.6.7.1 17 Dec 2015 C4 H25 M14 L12 — No Details →
1.6.7 30 Nov 2015 C4 H26 M14 L12 — No Details →
1.6.7.rc4 22 Nov 2015 C4 H26 M14 L12 — No Details →
1.6.6.4 19 Nov 2015 C4 H26 M14 L12 — No Details →
1.6.6.3 17 Nov 2015 C4 H26 M15 L12 — No Details →
1.6.7.rc3 04 Sep 2015 C4 H26 M14 L12 — No Details →
1.6.7.rc2 31 Aug 2015 C4 H26 M14 L12 — No Details →
1.6.6.2 23 Jan 2015 C4 H26 M15 L12 — No Details →
1.6.6.1 22 Jan 2015 C4 H26 M15 L12 — No Details →
1.6.5 26 Nov 2014 C4 H26 M14 L12 — No Details →
1.6.4.1 07 Nov 2014 C4 H26 M14 L12 — No Details →
1.6.4 05 Nov 2014 C4 H26 M14 L12 — No Details →
1.6.3.1 22 Jul 2014 C4 H26 M14 L12 — No Details →
1.6.3 20 Jul 2014 C4 H26 M14 L12 — No Details →

The newest 120 of 192 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 7
  • 2019 2
  • 2020 2
  • 2021 2
  • 2022 24
  • 2023 1
  • 2024 4
  • 2025 7
  • 2026 14

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

03 Vulnerabilities

Recorded vulnerabilities for nokogiri

The 5 most severe of 64 vulnerabilities recorded for this package

Search all 64 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-11068: Nokogiri libxslt Protection Mechanism Bypass 9.8 critical 1.10.3 13 May 2022
CVE-2016-4658: Nokogiri XML Parsing Remote Code Execution 9.8 critical 1.7.1 21 Aug 2018
CVE-2019-5477: Arbitrary execution of code in Nokogiri 9.8 critical 1.10.4 19 Aug 2019
CVE-2017-5029: Nokogiri libxslt Integer Overflow Vulnerability 8.8 high 1.7.2 31 Jul 2018
CVE-2021-3518: Nokogiri Implements libxml2 version vulnerable to use-after-free 8.8 high 1.11.4 24 May 2022

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 nokogiri

Is nokogiri safe to use?

Vulert records 64 vulnerabilities for nokogiri in RubyGems: 4 critical, 28 high, 18 medium and 14 low. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is nokogiri's Vulert package health score?

Vulert scores nokogiri 50/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of nokogiri affected?

Yes. 1.19.4, the version you would install today, has 5 known vulnerabilities, and 5 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of nokogiri should I use?

1.19.4 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 nokogiri have?

64 vulnerabilities are recorded for nokogiri in the RubyGems ecosystem: 4 critical, 28 high, 18 medium and 14 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new nokogiri vulnerabilities disclosed?

14 vulnerabilities were recorded for nokogiri in the last 12 months, and the oldest entry in this database dates to 13 Dec 2017. 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 nokogiri 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 nokogiri for upcoming vulnerabilities?

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