CVE-2026-57437

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 66% 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: 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, Nokogiri::XML::XPathContext did not keep its source document alive for garbage collection. If an XPathContext outlived its document and the document was collected, evaluating an XPath expression could read invalid memory and potentially segfault. This is only reachable when application code constructs an XPathContext directly and lets the document become unreachable while continuing to use the context. The normal Document#xpath, #css, and related search methods are not affected, and it is not triggerable by malicious document input. This vulnerability is fixed in 1.19.4.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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
Severity53% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 27, 2026
Patch available. Sources: github.
githubMentions a patch (unverified)

Possible Use-After-Free when directly using `NokogirI::XML::XPathContext` beyond document lifetime · Advisory · sparklemotion/nokogiri · GitHub

https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-p67v-3w7g-wjg7

Vendor Advisories for CVE-2026-57437(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(1)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-57437?
CVE-2026-57437 is a medium 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::XPathContext did not keep its source document alive for garbage collection. If an XPathContext outlived its document and the document was collected, evaluating an XPath expression…
When was CVE-2026-57437 disclosed?
CVE-2026-57437 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-57437 actively exploited?
CVE-2026-57437 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57437?
CVE-2026-57437 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-57437?
A fix for CVE-2026-57437 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57437 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-57437

Explore →

Is Your Infrastructure Affected by CVE-2026-57437?

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

Book a Demo →Browse All CVEs