CVE-2026-79769
CVE-2026-79769 · Nokogiri before 1.19.4 Invalid Memory Read via initialize_copy_with_args
CVSS 8.7 · High · EPSS 0.3% · Fix available
Compare with your installed version
Affected products and known fixed versions are public information. Compare them with your installed version.
- nokogiriUpdate to 1.19.4
- ruby-nokogiri Debian 13No fix published
- ruby-nokogiri Debian 14Update to 1.19.4+dfsg-1
- ruby-nokogiri Ubuntu Pro 14.04 LTSNo fix published
- and 6 more
Check the installed version:
dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="ruby-nokogiri"'Assess your server’s risks
The free check gives you a rating and a risk summary by technology stack, without signing up. It does not answer whether this particular vulnerability affects you.
Monitoring matches public information against your servers’ software. Detailed findings for your servers include the order of updates.
curl -fsSL https://patchfirst.dev/check.sh | shChannels carry general technology news; monitoring reports new findings on your servers in your dashboard, through browser notifications, in Telegram or via a webhook.
This page contains facts from public vulnerability sources. Check the original advisory before updating.
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
- Updated
Stack: system
Affected products and versions
nokogiri
- Versions
- ≥ 0, < 1.19.4: Affected (semver)
- 1.19.4: Not affected (semver)
Update to 1.19.4
ruby-nokogiri Debian 13
- Versions
- 1.18.10+dfsg-1
- 1.18.10+dfsg-2
- 1.18.10+dfsg-3
- 1.18.2+dfsg-1
- 1.19.1+dfsg-1
- 1.19.3+dfsg-1
All versions (7)
- 1.19.4+dfsg-1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
ruby-nokogiri Debian 14
- Versions
- 1.18.10+dfsg-1
- 1.18.10+dfsg-2
- 1.18.10+dfsg-3
- 1.18.2+dfsg-1
- 1.19.1+dfsg-1
- 1.19.3+dfsg-1
- Affected ranges
- ECOSYSTEM: < 1.19.4+dfsg-1
Update to 1.19.4+dfsg-1
ruby-nokogiri Ubuntu Pro 14.04 LTS
- Versions
- 1.5.9-2
- 1.5.9-3
- 1.6.0-1
- 1.6.1+ds-1
- 1.6.1+ds-1ubuntu0.1~esm1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
ruby-nokogiri Ubuntu 16.04 LTS
- Versions
- 1.6.6.2+ds-2build2
- 1.6.6.3-1
- 1.6.7-1
- 1.6.7.1-1
- 1.6.7.2-3
- 1.6.7.2-3build1
All versions (7)
- 1.6.7.2-3ubuntu0.1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
ruby-nokogiri Ubuntu 18.04 LTS
- Versions
- 1.8.0-1
- 1.8.1-1
- 1.8.1-1build1
- 1.8.2-1build1
- 1.8.2-1ubuntu0.1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
ruby-nokogiri Ubuntu Pro 20.04 LTS
- Versions
- 1.10.3+dfsg1-2
- 1.10.4+dfsg1-1
- 1.10.7+dfsg1-1
- 1.10.7+dfsg1-2
- 1.10.7+dfsg1-2build1
- 1.10.7+dfsg1-2ubuntu0.1~esm2
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
ruby-nokogiri Ubuntu Pro 22.04 LTS
- Versions
- 1.11.1+dfsg-2ubuntu1
- 1.11.7+dfsg-3
- 1.11.7+dfsg-3build1
- 1.13.1+dfsg-2
- 1.13.1+dfsg-2ubuntu0.1~esm1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
ruby-nokogiri Ubuntu 24.04 LTS
- Versions
- 1.14.3+dfsg-2
- 1.16.2+dfsg-1
- 1.16.2+dfsg-1build1
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published
ruby-nokogiri Ubuntu 26.04 LTS
- Versions
- 1.18.2+dfsg-1build1
- 1.18.10+dfsg-2
- 1.18.10+dfsg-3
- Affected ranges
- ECOSYSTEM: (−∞, +∞)
No fix published