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 73% 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

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, 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)
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
27%
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(5)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrubygem-nokogiri-0:1.15.7-3.el9sat2026-08-04redhat
redhatrubygem-nokogiri-0:1.17.2-3.el9sat2026-08-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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 25× in last 7d / 106× 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 180 total refreshes for this CVE.

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

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 0% probability of exploitation in the next 30 days, which ranks it in the top 72.8% of all scored CVEs.
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