Process crash via unchecked copy-source type
Published Aug 25, 2026 · Updated Aug 26, 2026
Type confusion in Nokogiri before 1.19.4 on CRuby allows a process crash when application code passes a non-Node copy source. The protected initialize_copy_with_args helper unwraps its source as an xmlNode without checking its Ruby object type, so a Namespace is read as an out-of-bounds xmlNs. The condition requires application code to misuse a protected internal method; untrusted input and normal public-API use cannot trigger it.
Summary
What happened
Type confusion in Nokogiri before 1.19.4 on CRuby allows a process crash when application code passes a non-Node copy source. The protected initialize_copy_with_args helper unwraps its source as an xmlNode without checking its Ruby object type, so a Namespace is read as an out-of-bounds xmlNs. The condition requires application code to misuse a protected internal method; untrusted input and normal public-API use cannot trigger it.
The record
- CVE
- CVE-2026-79769
- Published
- Aug 25, 2026
- Updated
- Aug 26, 2026
- Vendor
- Sparkle Motion
- Product
- Nokogiri
- Classifications
- CWE-843
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 26, 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=0 <1.19.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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