CVE-2026-57234

LOWPre-NVD 2.62.6—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% 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, secondary
2.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 2.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Nokogiri is an open source XML and HTML library for the Ruby programming language. Prior to 1.19.4, the NONET parse option, which Nokogiri turns on by default for Nokogiri::XML::Schema (see CVE-2020-26247), was not correctly enforced on the JRuby implementation. As a result, a schema parsed with default options could still cause external resources to be fetched over the network, potentially enabling SSRF or XXE attacks. This vulnerability is fixed in 1.19.4.

CVSS v3
2.6
EG Score
2.6LOWmedium confidence
EG Risk
16
EG Risk 16/100

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
Severity26% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

References (1)

Vendor Advisories for CVE-2026-57234(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 rangeFix by version rangeDependents
ruby-nokogiri1.11.1+dfsg-2 ... 1.19.4+dfsg-1 (33 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-nokogiri1.13.10+dfsg-2 ... 1.19.4+dfsg-1 (17 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-nokogiri1.18.10+dfsg-1 ... 1.19.4+dfsg-1 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-nokogiri1.18.10+dfsg-1 ... 1.19.3+dfsg-1 (6 versions)
  • every version up to 1.19.4+dfsg-1: fixed in 1.19.4+dfsg-1
—
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
nokogiri1.0.0 ... 1.9.1 (194 versions)
  • every version up to 1.19.4: fixed in 1.19.4
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 31× 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 144 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-57234?
CVE-2026-57234 is a low 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, the NONET parse option, which Nokogiri turns on by default for Nokogiri::XML::Schema (see CVE-2020-26247), was not correctly enforced on the JRuby implementation. As a result, a schema parsed with…
When was CVE-2026-57234 disclosed?
CVE-2026-57234 was first published 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-57234 actively exploited?
CVE-2026-57234 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57234?
CVE-2026-57234 has a CVSS base score of 2.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-57234?
A fix for CVE-2026-57234 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57234 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-57234?

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

Book a Demo →Browse All CVEs