Medium Memory corruption

CVE-2026-79769 — Nokogiri before 1.19.4 Invalid Memory Read via initialize_copy_with_args

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.

Published Aug 25, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (medium)+3
Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Sparklemotion

Nokogiri

CVSS base

5.5

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Sparklemotion Nokogiri).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Sparklemotion	Nokogiri	< 1.19.4	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.7	CVSS 4.0	High	—	—	disclosure@vulncheck.com via NIST National Vulnerability Database
8.7	CVSS 4.0	High	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP
5.5	CVSS 3.1	Medium	1.8	3.6	disclosure@vulncheck.com via NIST National Vulnerability Database
5.5	CVSS 3.1	Medium	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-843 · Type Confusion

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.

endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

2026
Affected products added · sparklemotion/nokogiri
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
CVSS changed · 5.5
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Deferred
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Aug 25, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

2 on the record

github.com/sparklemotion/nokogiri/security/advisories/GHSA-g9g8-vgvw-g3vf
vendor-advisory, NIST National Vulnerability Database
www.vulncheck.com/advisories/nokogiri-before-invalid-memory-read-via-initialize-copy-wi
third-party-advisory, NIST National Vulnerability Database

Elsewhere on this site

Sparklemotion
every CVE for this vendor

Memory corruption
same class

CWE-843
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-79770 Nokogiri before 1.19.3 ReDoS via CSS selector tokenizer Aug 25, 2026
Medium CVE-2026-79771 Nokogiri before 1.19.3 Memory Leak via XSLT Transform Aug 25, 2026
Medium CVE-2026-79772 Nokogiri before 1.19.1 Unchecked Return Value canonicalize Aug 25, 2026
Medium CVE-2026-57438 Nokogiri: Possible Use-After-Free in XInclude Processing Jun 25, 2026
Medium CVE-2026-57436 Nokogiri: Possible Use-After-Free when setting `Document#root=` to an invalid node type Jun 25, 2026
Medium CVE-2026-57437 Nokogiri: Possible Use-After-Free when directly using `NokogirI::XML::XPathContext` beyond document lifetime Jun 25, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-79769 is "Nokogiri before 1.19.4 Invalid Memory Read via initialize_copy_with_args", rated Medium. It affects Nokogiri (Sparklemotion); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.