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.
CVE-2026-57434
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 72% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 28.2%
- KEV
- Not listed
Published
June 25, 2026
Last Modified
June 26, 2026
Advisory Details (1)
Auto-updated Jun 26, 2026Null Pointer Dereference calling methods on uninitialized wrapper classes · Advisory · sparklemotion/nokogiri · GitHub
https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-9cv2-cfxc-v4v2Vendor 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
(1 across 1 ecosystem)
RubyGems(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nokogiri | 1.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 10× in last 7d / 71× 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.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 04:38 UTCVendor advisory
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 03:23 UTCVendor advisory
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 14:55 UTCVendor advisory
- 2026-07-15 02:28 UTCVendor advisory
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 14:00 UTCVendor advisory
- 2026-07-14 01:32 UTCVendor advisory
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 00:36 UTCVendor advisory
- 2026-07-12 12:08 UTCVendor advisory
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 23:41 UTCVendor advisory
Show 46 moreShow fewer
- 2026-07-11 11:14 UTCVendor advisory
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 22:45 UTCVendor advisory
- 2026-07-10 10:18 UTCVendor advisory
- 2026-07-09 21:49 UTCVendor advisory
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 09:22 UTCVendor advisory
- 2026-07-08 20:53 UTCVendor advisory
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 08:26 UTCVendor advisory
- 2026-07-07 19:59 UTCVendor advisory
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 07:31 UTCVendor advisory
- 2026-07-06 18:55 UTCVendor advisory
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 06:27 UTCVendor advisory
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 18:00 UTCVendor advisory
- 2026-07-05 05:31 UTCVendor advisory
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 17:01 UTCVendor advisory
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 04:32 UTCVendor advisory
- 2026-07-03 15:58 UTCVendor advisory
- 2026-07-03 03:29 UTCVendor advisory
- 2026-07-02 15:02 UTCVendor advisory
- 2026-07-02 02:34 UTCVendor advisory
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 14:07 UTCVendor advisory
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 11:23 UTCEG score recompute▲ 5.80
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 13:40 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
- 2026-06-25 15:48 UTCEG score recompute
- 2026-06-25 15:47 UTCNVD updatefirst tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 94%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Frequently asked(5)
What is CVE-2026-57434?
When was CVE-2026-57434 disclosed?
Is CVE-2026-57434 actively exploited?
What is the CVSS score of CVE-2026-57434?
How do I remediate CVE-2026-57434?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57434
Is Your Infrastructure Affected by CVE-2026-57434?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.