Nokogiri is an open source XML and HTML library for the Ruby programming language. Prior to 1.19.4, Nokogiri’s CRuby native extension could leave a Ruby wrapper pointing to freed memory when replacing the value of an XML attribute. If Ruby code had already accessed an attribute child node, Nokogiri::XML::Attr#value= could free the underlying native child node while the wrapper remained reachable through the document node cache. A later use of the freed child node or a Ruby GC mark could dereference an invalid pointer, causing an invalid read and a possible segfault. This vulnerability is fixed in 1.19.4.
CVE-2026-57435
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 62% 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)
- 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 computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 38%
- KEV
- Not listed
Published
June 25, 2026
Last Modified
June 26, 2026
Advisory Details (1)
Auto-updated Jun 26, 2026Possible Use-After-Free when setting an attribute value via `Nokogiri::XML::Attr#value=` or `#content=` · Advisory · sparklemotion/nokogiri · GitHub
https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-phwj-rprq-35ppVendor Advisories for CVE-2026-57435(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ruby-nokogiri | 1.11.1+dfsg-2 ... 1.19.4+dfsg-1 (33 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ruby-nokogiri | 1.13.10+dfsg-2 ... 1.19.4+dfsg-1 (17 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ruby-nokogiri | 1.18.10+dfsg-1 ... 1.19.4+dfsg-1 (7 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ruby-nokogiri | 1.18.10+dfsg-1 ... 1.19.3+dfsg-1 (6 versions) | 1.19.4+dfsg-1 | — |
RubyGems(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nokogiri | 1.0.0 ... 1.9.1 (194 versions) | 1.19.4 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 95× 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 176 total refreshes for this CVE.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 01:43 UTCEG score recompute
- 2026-08-25 01:43 UTCVendor advisory
- 2026-08-24 13:11 UTCEG score recompute
- 2026-08-24 13:11 UTCVendor advisory
- 2026-08-24 00:18 UTCVendor advisory
- 2026-08-23 11:45 UTCEG score recompute
- 2026-08-23 11:45 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 23:12 UTCVendor advisory
- 2026-08-22 10:39 UTCEG score recompute
- 2026-08-22 10:39 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 08:12 UTCEG score recompute
- 2026-08-21 08:12 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 19:39 UTCVendor advisory
- 2026-08-20 07:05 UTCEG score recompute
- 2026-08-20 07:05 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 14:14 UTCVendor advisory
- 2026-08-19 01:29 UTCEG score recompute
- 2026-08-19 01:29 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-17 06:11 UTCVendor advisory
- 2026-08-16 16:43 UTCEG score recompute
- 2026-08-16 16:43 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 04:10 UTCEG score recompute
- 2026-08-16 04:10 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 15:37 UTCVendor advisory
- 2026-08-15 03:04 UTCEG score recompute
- 2026-08-15 03:04 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 14:31 UTCVendor advisory
- 2026-08-14 01:59 UTCEG score recompute
- 2026-08-14 01:59 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 13:26 UTCVendor advisory
- 2026-08-13 00:53 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 12:21 UTCVendor advisory
- 2026-08-11 23:45 UTCEG score recompute
- 2026-08-11 23:45 UTCVendor advisory
- 2026-08-11 11:12 UTCEG score recompute
- 2026-08-11 11:12 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 21:33 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 20:28 UTCEG score recompute
- 2026-08-08 20:28 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 19:23 UTCEG score recompute
- 2026-08-07 19:23 UTCVendor advisory
- 2026-08-07 06:50 UTCVendor advisory
- 2026-08-06 18:16 UTCEG score recompute
- 2026-08-06 18:16 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 05:43 UTCEG score recompute
- 2026-08-06 05:43 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 22:15 UTCEG score recompute
- 2026-08-04 22:15 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 08:58 UTCVendor advisory
- 2026-08-03 20:25 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 18:19 UTCVendor advisory
- 2026-08-02 05:47 UTCEG score recompute
- 2026-08-02 05:47 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 17:13 UTCVendor advisory
- 2026-08-01 04:40 UTCEG score recompute
- 2026-08-01 04:40 UTCVendor advisory
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 16:03 UTCVendor advisory
- 2026-07-31 03:15 UTCEG score recompute
- 2026-07-31 03:15 UTCVendor advisory
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 14:06 UTCEG score recompute
- 2026-07-30 14:06 UTCVendor advisory
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 00:51 UTCVendor advisory
- 2026-07-29 09:54 UTCVendor advisory
- 2026-07-28 21:21 UTCEG score recompute
- 2026-07-28 21:21 UTCVendor advisory
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 05:58 UTCVendor advisory
- 2026-07-27 17:24 UTCEG score recompute
- 2026-07-27 17:24 UTCVendor advisory
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 03:46 UTCVendor advisory
- 2026-07-26 15:09 UTCEG score recompute
- 2026-07-26 15:09 UTCVendor advisory
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-57435?
When was CVE-2026-57435 disclosed?
Is CVE-2026-57435 actively exploited?
What is the CVSS score of CVE-2026-57435?
How do I remediate CVE-2026-57435?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57435
Is Your Infrastructure Affected by CVE-2026-57435?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.