Nokogiri versions before 1.19.4 contain a possible invalid (out-of-bounds) memory read in the protected internal Node#initialize_copy_with_args helper behind Node#dup and #clone, which unwrapped its source argument as an xmlNode without a type check. If application code calls this protected method with a non-Node argument (e.g., a Namespace), it reads an xmlNs out of bounds, crashing the process. This is only triggerable by a programming error and cannot be triggered by untrusted input or normal use of the public API. Only CRuby is affected. Version 1.19.4 adds a type check and raises TypeError.
CVE-2026-79769
Score 5.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 5.5; sources differ by 0.0.
- 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
- 5.5
- EG Score
- 5.5(high)
- EG Risk
- 40(Track)EG Risk 40/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 computedSeverity55% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 26, 2026
Advisory Details (1)
Auto-updated Aug 25, 2026Possible invalid memory read when calling `Nokogiri::XML::Node#initialize_copy_with_args` with incorrect argument type · Advisory · sparklemotion/nokogiri · GitHub
https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-g9g8-vgvw-g3vfVendor Advisories for CVE-2026-79769(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 3 ecosystems)
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 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 69× 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-09-19 07:52 UTCEG score recompute
- 2026-09-19 07:52 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 07:23 UTCEG score recompute
- 2026-09-18 07:23 UTCGHSA enrichment
- 2026-09-17 06:53 UTCEG score recompute
- 2026-09-17 06:53 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 06:11 UTCEG score recompute
- 2026-09-16 06:11 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 05:41 UTCEG score recompute
- 2026-09-15 05:40 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 04:15 UTCEG score recompute
- 2026-09-14 04:15 UTCGHSA enrichment
- 2026-09-13 03:46 UTCEG score recompute
- 2026-09-13 03:46 UTCGHSA enrichment
- 2026-09-12 03:16 UTCEG score recompute
- 2026-09-12 03:16 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 02:46 UTCEG score recompute
- 2026-09-11 02:46 UTCGHSA enrichment
Show 44 moreShow fewer
- 2026-09-10 02:15 UTCGHSA enrichment
- 2026-09-09 01:45 UTCEG score recompute
- 2026-09-09 01:44 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 01:14 UTCEG score recompute
- 2026-09-08 01:14 UTCGHSA enrichment
- 2026-09-07 00:45 UTCEG score recompute
- 2026-09-07 00:45 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 00:13 UTCEG score recompute
- 2026-09-06 00:13 UTCGHSA enrichment
- 2026-09-04 23:41 UTCEG score recompute
- 2026-09-04 23:41 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 22:14 UTCGHSA enrichment
- 2026-09-02 21:20 UTCEG score recompute
- 2026-09-02 21:20 UTCGHSA enrichment
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 20:49 UTCEG score recompute
- 2026-09-01 20:49 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 20:19 UTCGHSA enrichment
- 2026-08-30 19:49 UTCEG score recompute
- 2026-08-30 19:49 UTCGHSA enrichment
- 2026-08-30 19:18 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 19:19 UTCEG score recompute
- 2026-08-29 19:19 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 18:47 UTCGHSA enrichment
- 2026-08-27 18:11 UTCEG score recompute
- 2026-08-27 18:11 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 17:23 UTCEG score recompute
- 2026-08-26 17:23 UTCGHSA enrichment
- 2026-08-26 16:23 UTCEG score recompute
- 2026-08-26 16:23 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 16:24 UTCEG score recompute
- 2026-08-25 15:30 UTCEG score recompute
- 2026-08-25 15:29 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-79769?
When was CVE-2026-79769 disclosed?
Is CVE-2026-79769 actively exploited?
What is the CVSS score of CVE-2026-79769?
How do I remediate CVE-2026-79769?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-79769
Is Your Infrastructure Affected by CVE-2026-79769?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.