Nokogiri is an open source XML and HTML library for the Ruby programming language. Prior to 1.19.4, Nokogiri::XML::NodeSet#[] (and its alias #slice) checked the requested index against the node set's bounds using a 32-bit-truncated copy of the index. A large negative index could pass the check and then be used at full width, reading outside the node set's storage. On CRuby this is an out-of-bounds read that typically crashes the process; on JRuby it is not memory-unsafe but returns an incorrect node. This vulnerability is fixed in 1.19.4.
CVE-2026-57235
This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EPSS
- 25.1%
- KEV
- Not listed
Published
June 25, 2026
Last Modified
June 26, 2026
Advisory Details (1)
Auto-updated Jun 25, 2026Possible Out-of-Bounds Read in `Nokogiri::XML::NodeSet#[]` · Advisory · sparklemotion/nokogiri · GitHub
https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-5prr-v3j2-97mhVendor Advisories for CVE-2026-57235(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 40× in last 7d / 56× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 06:11 UTCEG score recompute
- 2026-07-07 06:11 UTCVendor advisory
- 2026-07-06 19:10 UTCEG score recompute
- 2026-07-06 19:10 UTCVendor advisory
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 08:10 UTCEG score recompute
- 2026-07-06 08:10 UTCVendor advisory
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 21:11 UTCEG score recompute
- 2026-07-05 21:11 UTCVendor advisory
- 2026-07-05 10:14 UTCEG score recompute
- 2026-07-05 10:13 UTCVendor advisory
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 23:16 UTCEG score recompute
- 2026-07-04 23:16 UTCVendor advisory
- 2026-07-04 12:19 UTCEG score recompute
- 2026-07-04 12:19 UTCVendor advisory
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 01:22 UTCEG score recompute
- 2026-07-04 01:22 UTCVendor advisory
- 2026-07-03 14:25 UTCEG score recompute
Show 31 moreShow fewer
- 2026-07-03 14:25 UTCVendor advisory
- 2026-07-03 03:28 UTCEG score recompute
- 2026-07-03 03:28 UTCVendor advisory
- 2026-07-02 16:31 UTCEG score recompute
- 2026-07-02 16:31 UTCVendor advisory
- 2026-07-02 05:33 UTCEG score recompute
- 2026-07-02 05:33 UTCVendor advisory
- 2026-07-01 18:36 UTCEG score recompute
- 2026-07-01 18:36 UTCVendor advisory
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 07:39 UTCEG score recompute
- 2026-07-01 07:39 UTCVendor advisory
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 20:42 UTCEG score recompute
- 2026-06-30 09:43 UTCEG score recompute
- 2026-06-29 22:46 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 11:48 UTCEG score recompute
- 2026-06-29 00:51 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 13:54 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 02:56 UTCEG score recompute
- 2026-06-27 15:59 UTCEG score recompute
- 2026-06-27 05:02 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 18:03 UTCEG score recompute▲ 1.90
- 2026-06-26 13:40 UTCNVD updateCVSS v3 → 8.2 · severity → HIGH
- 2026-06-25 15:48 UTCEG score recompute
- 2026-06-25 15:47 UTCNVD updatefirst tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 93%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Same CWE
10 shownCWE-190 · CWE-125
- CVE-2009-0947EG 9.8CRITICAL
- CVE-2005-1141EG 9.8CRITICAL
- CVE-2005-0102EG 9.8CRITICAL
- CVE-2002-0391EG 9.8EPSS 99%CRITICAL
- CVE-2002-0639EG 9.8EPSS 97%CRITICAL
- CVE-1999-0006EG 9.8EPSS 96%CRITICAL
- CVE-2011-1823NVD 7.8EG 9.0 KEVEPSS 99%HIGH
- CVE-2011-0663EG 8.8EPSS 98%HIGH
- CVE-2010-2753EG 8.8EPSS 93%HIGH
- CVE-2010-0130EG 8.8EPSS 94%HIGH
Frequently asked(5)
What is CVE-2026-57235?
When was CVE-2026-57235 disclosed?
Is CVE-2026-57235 actively exploited?
What is the CVSS score of CVE-2026-57235?
How do I remediate CVE-2026-57235?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-57235
Is Your Infrastructure Affected by CVE-2026-57235?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.