Nokogiri is an open source XML and HTML library for the Ruby programming language. Prior to 1.19.4, XInclude substitution performed by Nokogiri::XML::Node#do_xinclude replaced each in place, freeing the include node along with its children (such as and its descendants) and any namespaces declared on them. If an application had already exposed one of those nodes or namespaces to Ruby, the corresponding Ruby object was left pointing at freed memory. Using the object could result in invalid reads or writes to memory. This vulnerability is fixed in 1.19.4.
CVE-2026-57438
This medium-severity CVE scores 6.6 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 99% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.6
- EG Score
- 6.6(medium)
- EPSS
- 0.7%
- KEV
- Not listed
Published
June 25, 2026
Last Modified
June 26, 2026
Advisory Details (1)
Auto-updated Jun 26, 2026Possible Use-After-Free in XInclude Processing · Advisory · sparklemotion/nokogiri · GitHub
https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-wfpw-mmfh-qq69Vendor Advisories for CVE-2026-57438(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 3× in last 7d / 43× 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-20 17:08 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 09:52 UTCVendor advisory
- 2026-07-14 07:37 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 05:21 UTCVendor advisory
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 02:52 UTCVendor advisory
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 00:38 UTCVendor advisory
- 2026-07-09 22:23 UTCVendor advisory
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 20:09 UTCVendor advisory
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 17:52 UTCVendor advisory
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
Show 18 moreShow fewer
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 15:08 UTCVendor advisory
- 2026-07-05 12:47 UTCVendor advisory
- 2026-07-04 10:31 UTCVendor advisory
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 08:14 UTCVendor advisory
- 2026-07-02 05:59 UTCVendor advisory
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 23:14 UTCEG score recompute▲ 4.40
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 09:42 UTCNVD updateCVSS v3 → 6.6 · severity → MEDIUM
- 2026-06-25 17:49 UTCEG score recompute
- 2026-06-25 17:48 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
Same CWE
10 shownCWE-416
- CVE-2010-3962NVD 8.1EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-0806NVD 8.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-0249NVD 8.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2009-4324NVD 7.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-3328EG 8.8EPSS 98%HIGH
- CVE-2010-1772EG 8.8HIGH
- CVE-2010-1208EG 8.8EPSS 92%HIGH
- CVE-2010-0050EG 8.8EPSS 96%HIGH
- CVE-2010-0378EG 8.8EPSS 93%HIGH
- CVE-2009-3658EG 8.8EPSS 95%HIGH
Frequently asked(5)
What is CVE-2026-57438?
When was CVE-2026-57438 disclosed?
Is CVE-2026-57438 actively exploited?
What is the CVSS score of CVE-2026-57438?
How do I remediate CVE-2026-57438?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57438
Is Your Infrastructure Affected by CVE-2026-57438?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.