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

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: 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::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.3(medium)
EG Risk
28(Track)
EG Risk 28/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
Severity53% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (1)

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

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 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(1)

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

Data Freshness Timeline

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

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

Related CVEs(same vendor + 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 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-57437 actively exploited?
CVE-2026-57437 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 66.9% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57437, 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-57437

Explore →

Is Your Infrastructure Affected by CVE-2026-57437?

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

Start Free Scan →Browse All CVEs