CVE-2026-79769
Nokogiri bug can crash Ruby processes when internal Node clone is misused.
Is CVE-2026-79769 being exploited?
Not confirmed. CVE-2026-79769 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-79769?
CVE-2026-79769 is rated Medium. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-79769?
Yes. A fix has been recorded for CVE-2026-79769. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-79769 affect?
CVE-2026-79769 affects Nokogiri < 1.19.4 (Ruby gem), CRuby (MRI). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-79769?
Upgrade Nokogiri to >= 1.19.4 and audit codepaths using Node#dup/#clone for incorrect args.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Out-of-bounds read can crash the process (denial of service) when Node#initialize_copy_with_args is called with non-Node args; requires programming error; CRuby only.
Patch when possible
- affected< 1.19.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.