PatchSiren cyber security CVE debrief
CVE-2026-79771 sparklemotion CVE debrief
The Nokogiri library versions before 1.19.3 contain a memory leak vulnerability in the XSLT Stylesheet transform method. This occurs when processing Ruby strings containing null bytes. An attacker can exploit this vulnerability by passing attacker-controlled input with null bytes to transform parameters, causing heap allocations to leak and enabling denial of service against long-running processes. Affected product deployments should be identified in managed environments and assigned an owner for follow-up. The CVE record was published on 2026-08-25T16:17:28.603Z and has not been modified since then. The NVD entry is currently Analyzed. Limited evidence suggests that developers and administrators using Nokogiri versions before 1.19.3 should be aware of this vulnerability and take necessary actions to mitigate the risk.
- Vendor
- sparklemotion
- Product
- nokogiri
- CVSS
- MEDIUM 6.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-25
- Original CVE updated
- 2026-09-01
- Advisory published
- 2026-08-25
- Advisory updated
- 2026-09-01
Who should care
Developers and administrators using Nokogiri versions before 1.19.3 should be aware of this vulnerability and take necessary actions to mitigate the risk. This includes upgrading to version 1.19.3 or later, restricting input to XSLT transform parameters, and monitoring long-running processes for denial of service.
Technical summary
The Nokogiri library versions before 1.19.3 contain a memory leak vulnerability in the XSLT Stylesheet transform method. This occurs when processing Ruby strings containing null bytes. An attacker can exploit this vulnerability by passing attacker-controlled input with null bytes to transform parameters, causing heap allocations to leak and enabling denial of service against long-running processes.
Defensive priority
Medium-priority defensive actions are required to address the memory leak vulnerability in Nokogiri versions before 1.19.3.
Recommended defensive actions
- Verify Nokogiri version and upgrade to 1.19.3 or later if necessary
- Restrict input to XSLT transform parameters to prevent null bytes
- Monitor long-running processes for denial of service
- Implement compensating controls to detect and prevent potential attacks
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
Evidence notes
The CVE description indicates that Nokogiri versions before 1.19.3 contain a memory leak in the XSLT Stylesheet transform method. Limited evidence suggests that attackers can exploit this by passing attacker-controlled input with null bytes to transform parameters, causing heap allocations to leak and enabling denial of service against long-running processes. Further verification is needed to confirm affected scope and inventory.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-79771 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-79771
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-79771 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-79771
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-v2fc-qm4h-8hqv
[email protected] - Vendor Advisory
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/nokogiri-before-memory-leak-via-xslt-transform
[email protected] - Third Party Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.