CVE-2026-57235

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 65% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 25, 2026
Patch available. Sources: github.
github Patch Available

Possible Out-of-Bounds Read in `Nokogiri::XML::NodeSet#[]` · Advisory · sparklemotion/nokogiri · GitHub

https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-5prr-v3j2-97mh

Vendor 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.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ruby-nokogiri1.11.1+dfsg-2 ... 1.19.4+dfsg-1 (33 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ruby-nokogiri1.13.10+dfsg-2 ... 1.19.4+dfsg-1 (17 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ruby-nokogiri1.18.10+dfsg-1 ... 1.19.4+dfsg-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ruby-nokogiri1.18.10+dfsg-1 ... 1.19.3+dfsg-1 (6 versions)1.19.4+dfsg-1—
RubyGems(1)
PackageVulnerable rangeFixed inDependents
nokogiri1.0.0 ... 1.9.1 (194 versions)1.19.4—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 103× 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.

Showing the most recent 100 of 190 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 00:08 UTCEG score recompute
  3. 2026-08-25 00:08 UTCVendor advisory
  4. 2026-08-24 13:11 UTCEG score recompute
  5. 2026-08-24 13:11 UTCVendor advisory
  6. 2026-08-23 20:22 UTCVendor advisory
  7. 2026-08-23 09:25 UTCEG score recompute
  8. 2026-08-23 09:25 UTCVendor advisory
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 22:27 UTCVendor advisory
  11. 2026-08-22 10:39 UTCEG score recompute
  12. 2026-08-22 10:39 UTCVendor advisory
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 05:09 UTCEG score recompute
  15. 2026-08-21 05:09 UTCVendor advisory
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 18:03 UTCVendor advisory
  18. 2026-08-20 07:05 UTCEG score recompute
  19. 2026-08-20 07:05 UTCVendor advisory
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-19 12:40 UTCVendor advisory
  22. 2026-08-19 01:29 UTCEG score recompute
  23. 2026-08-19 01:29 UTCVendor advisory
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-17 17:10 UTCEG score recompute
Show 75 more
  1. 2026-08-17 17:10 UTCVendor advisory
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 06:11 UTCVendor advisory
  4. 2026-08-16 18:21 UTCEG score recompute
  5. 2026-08-16 18:21 UTCVendor advisory
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 06:25 UTCEG score recompute
  8. 2026-08-16 06:25 UTCVendor advisory
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 19:29 UTCVendor advisory
  11. 2026-08-15 08:32 UTCEG score recompute
  12. 2026-08-15 08:32 UTCVendor advisory
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 21:05 UTCVendor advisory
  15. 2026-08-13 23:11 UTCEG score recompute
  16. 2026-08-13 23:11 UTCVendor advisory
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 12:14 UTCVendor advisory
  19. 2026-08-12 14:21 UTCEG score recompute
  20. 2026-08-12 14:21 UTCVendor advisory
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-12 03:24 UTCVendor advisory
  23. 2026-08-11 16:27 UTCEG score recompute
  24. 2026-08-11 16:27 UTCVendor advisory
  25. 2026-08-11 05:30 UTCEG score recompute
  26. 2026-08-11 05:30 UTCVendor advisory
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-09 19:45 UTCEG score recompute
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-08 21:52 UTCEG score recompute
  31. 2026-08-08 21:52 UTCVendor advisory
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-08 10:55 UTCVendor advisory
  34. 2026-08-07 23:58 UTCEG score recompute
  35. 2026-08-07 23:58 UTCVendor advisory
  36. 2026-08-07 13:01 UTCVendor advisory
  37. 2026-08-07 02:04 UTCVendor advisory
  38. 2026-08-06 15:07 UTCEG score recompute
  39. 2026-08-06 15:07 UTCVendor advisory
  40. 2026-08-06 13:47 UTCEPSS rescore
  41. 2026-08-06 04:07 UTCEG score recompute
  42. 2026-08-06 04:07 UTCVendor advisory
  43. 2026-08-05 19:17 UTCEPSS rescore
  44. 2026-08-05 03:40 UTCVendor advisory
  45. 2026-08-04 16:43 UTCEG score recompute
  46. 2026-08-04 16:43 UTCVendor advisory
  47. 2026-08-04 15:10 UTCEPSS rescore
  48. 2026-08-04 10:39 UTCEPSS rescore
  49. 2026-08-04 05:46 UTCVendor advisory
  50. 2026-08-03 18:49 UTCEG score recompute
  51. 2026-08-03 18:49 UTCVendor advisory
  52. 2026-08-03 10:36 UTCEPSS rescore
  53. 2026-08-02 19:32 UTCVendor advisory
  54. 2026-08-02 08:35 UTCEG score recompute
  55. 2026-08-02 08:35 UTCVendor advisory
  56. 2026-08-02 02:27 UTCEPSS rescore
  57. 2026-08-01 21:38 UTCVendor advisory
  58. 2026-08-01 10:40 UTCEG score recompute
  59. 2026-08-01 10:40 UTCVendor advisory
  60. 2026-08-01 04:16 UTCEPSS rescore
  61. 2026-07-31 23:43 UTCVendor advisory
  62. 2026-07-31 12:11 UTCVendor advisory
  63. 2026-07-31 01:10 UTCEG score recompute
  64. 2026-07-30 16:28 UTCEPSS rescore
  65. 2026-07-30 14:06 UTCEG score recompute
  66. 2026-07-30 14:06 UTCVendor advisory
  67. 2026-07-30 01:30 UTCEPSS rescore
  68. 2026-07-30 01:30 UTCEPSS rescore
  69. 2026-07-30 00:51 UTCVendor advisory
  70. 2026-07-29 13:08 UTCVendor advisory
  71. 2026-07-29 02:10 UTCEG score recompute
  72. 2026-07-29 02:10 UTCVendor advisory
  73. 2026-07-28 15:37 UTCEPSS rescore
  74. 2026-07-28 15:13 UTCVendor advisory
  75. 2026-07-28 01:07 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-57235?
CVE-2026-57235 is a high vulnerability published on June 25, 2026. 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…
When was CVE-2026-57235 disclosed?
CVE-2026-57235 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57235 actively exploited?
CVE-2026-57235 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.7% of all scored CVEs.
What is the CVSS score of CVE-2026-57235?
CVE-2026-57235 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-57235?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57235, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57235

Explore →

Is Your Infrastructure Affected by CVE-2026-57235?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs