CVE-2026-57434

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 61% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: 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 contains a bug when calling certain methods on allocated-but-uninitialized native wrapper classes that inherit from Nokogiri::XML::Node. This caused a NULL pointer dereference that could crash the process. This vulnerability is fixed in 1.19.4.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
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

Null Pointer Dereference calling methods on uninitialized wrapper classes · Advisory · sparklemotion/nokogiri · GitHub

https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-9cv2-cfxc-v4v2

Vendor Advisories for CVE-2026-57434(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 13× in last 7d / 48× 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 210 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-57434?
CVE-2026-57434 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, Nokogiri contains a bug when calling certain methods on allocated-but-uninitialized native wrapper classes that inherit from Nokogiri::XML::Node. This caused a NULL pointer dereference that could…
When was CVE-2026-57434 disclosed?
CVE-2026-57434 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-57434 actively exploited?
CVE-2026-57434 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 60.9% of all scored CVEs.
What is the CVSS score of CVE-2026-57434?
CVE-2026-57434 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-57434?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57434, 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-57434

Explore →

Is Your Infrastructure Affected by CVE-2026-57434?

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

Start Free Scan →Browse All CVEs