CVE-2026-57236

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 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, calling Document#encoding= with an invalid encoding (e.g., a non-string, or a string containing a null byte) raises an exception, but only after freeing the document's current encoding string without replacing it. The document is left referencing freed memory, so the next call to Document#encoding reads invalid memory, which can cause a segfault or leak freed bytes into a Ruby String. Affects the CRuby (libxml2) implementation only; JRuby is not affected. This vulnerability is fixed in 1.19.4.

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
25.5%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (1)

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

Possible Use-After-Free when `Nokogiri::XML::Document#encoding=` raises an exception · Advisory · sparklemotion/nokogiri · GitHub

https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-5v8h-3h3q-446p

Vendor Advisories for CVE-2026-57236(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
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 11× in last 7d / 75× 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.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 23:20 UTCVendor advisory
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-16 12:18 UTCVendor advisory
  11. 2026-07-16 01:10 UTCVendor advisory
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 14:07 UTCVendor advisory
  15. 2026-07-15 03:00 UTCVendor advisory
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-14 15:56 UTCVendor advisory
  19. 2026-07-14 04:51 UTCVendor advisory
  20. 2026-07-13 22:31 UTCEPSS rescore
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-12 19:39 UTCVendor advisory
  24. 2026-07-12 08:36 UTCVendor advisory
  25. 2026-07-12 05:46 UTCEPSS rescore
Show 50 more
  1. 2026-07-11 21:33 UTCVendor advisory
  2. 2026-07-11 10:31 UTCVendor advisory
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-10 23:29 UTCVendor advisory
  6. 2026-07-10 12:22 UTCVendor advisory
  7. 2026-07-10 01:17 UTCVendor advisory
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-09 14:12 UTCVendor advisory
  11. 2026-07-09 03:09 UTCVendor advisory
  12. 2026-07-08 16:01 UTCVendor advisory
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-08 04:56 UTCVendor advisory
  16. 2026-07-07 17:53 UTCVendor advisory
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-07 06:11 UTCVendor advisory
  20. 2026-07-06 19:06 UTCVendor advisory
  21. 2026-07-06 16:27 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 08:02 UTCVendor advisory
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-06 02:23 UTCEPSS rescore
  26. 2026-07-05 20:59 UTCVendor advisory
  27. 2026-07-05 09:53 UTCVendor advisory
  28. 2026-07-05 02:31 UTCEPSS rescore
  29. 2026-07-05 02:30 UTCEPSS rescore
  30. 2026-07-04 22:49 UTCVendor advisory
  31. 2026-07-04 11:47 UTCVendor advisory
  32. 2026-07-04 06:31 UTCEPSS rescore
  33. 2026-07-04 06:31 UTCEPSS rescore
  34. 2026-07-04 00:41 UTCVendor advisory
  35. 2026-07-03 13:31 UTCVendor advisory
  36. 2026-07-03 02:29 UTCVendor advisory
  37. 2026-07-02 15:24 UTCVendor advisory
  38. 2026-07-02 04:19 UTCVendor advisory
  39. 2026-07-01 17:16 UTCVendor advisory
  40. 2026-07-01 15:07 UTCEPSS rescore
  41. 2026-06-30 23:22 UTCEPSS rescore
  42. 2026-06-29 14:06 UTCEPSS rescore
  43. 2026-06-28 14:07 UTCEPSS rescore
  44. 2026-06-28 11:58 UTCEG score recompute▲ 6.50
  45. 2026-06-28 04:56 UTCEPSS rescore
  46. 2026-06-28 04:56 UTCEPSS rescore
  47. 2026-06-27 03:08 UTCEPSS rescore
  48. 2026-06-26 13:40 UTCNVD updateCVSS v3 → 8.2 · severity → HIGH
  49. 2026-06-25 15:48 UTCEG score recompute
  50. 2026-06-25 15:47 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-57236?
CVE-2026-57236 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, calling Document#encoding= with an invalid encoding (e.g., a non-string, or a string containing a null byte) raises an exception, but only after freeing the document's current encoding string without…
When was CVE-2026-57236 disclosed?
CVE-2026-57236 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-57236 actively exploited?
CVE-2026-57236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57236?
CVE-2026-57236 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-57236?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57236, 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-57236

Explore →

Is Your Infrastructure Affected by CVE-2026-57236?

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

Start Free Scan →Browse All CVEs