Invalid memory access via freed XInclude wrappers
Published Jun 25, 2026 · Updated Jun 25, 2026
Use-after-free in Sparkle Motion Nokogiri before 1.19.4 allows attackers to trigger invalid memory reads or writes during XInclude processing. Node#do_xinclude replaces each xi:include in place, freeing exposed child nodes and namespaces while their live Ruby wrappers retain dangling pointers. Only CRuby is affected, and reachability requires parsing without XInclude, exposing an include-subtree object to Ruby, and then invoking do_xinclude; parse-time XInclude and JRuby are unaffected.
Summary
What happened
Use-after-free in Sparkle Motion Nokogiri before 1.19.4 allows attackers to trigger invalid memory reads or writes during XInclude processing. Node#do_xinclude replaces each xi:include in place, freeing exposed child nodes and namespaces while their live Ruby wrappers retain dangling pointers. Only CRuby is affected, and reachability requires parsing without XInclude, exposing an include-subtree object to Ruby, and then invoking do_xinclude; parse-time XInclude and JRuby are unaffected.
The record
- CVE
- CVE-2026-57438
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- Sparkle Motion
- Product
- Nokogiri
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.19.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo