PatchSiren cyber security CVE debrief
CVE-2026-57437 sparklemotion CVE debrief
A vulnerability in Nokogiri, an open-source XML and HTML library for Ruby, allows for potential segfaults when evaluating XPath expressions. This issue arises when an XPathContext outlives its source document, which has been garbage collected. The vulnerability is fixed in Nokogiri version 1.19.4. Defenders should assess exposure and prioritize upgrading to Nokogiri version 1.19.4 or later. The vulnerability requires verification from the supplied official sources, and its impact is limited to specific usage scenarios.
- Vendor
- sparklemotion
- Product
- nokogiri
- CVSS
- LOW 1.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-06-25
- Original CVE updated
- 2026-10-25
- Advisory published
- 2026-06-25
- Advisory updated
- 2026-10-25
Who should care
Defenders responsible for Ruby applications using Nokogiri, especially those constructing XPathContext directly, should assess exposure and prioritize upgrading to Nokogiri version 1.19.4 or later.
Why it matters
This vulnerability in Nokogiri could lead to potential segfaults when evaluating XPath expressions. Defenders should prioritize verifying and upgrading to Nokogiri version 1.19.4 or later. The vulnerability requires verification from the supplied official sources, and its impact is limited to specific usage scenarios.
- Potential segfaults when evaluating XPath expressions
- Verification of Nokogiri version and upgrade to 1.19.4 or later required
- Review of application code for direct XPathContext usage necessary
Technical summary
Nokogiri::XML::XPathContext did not keep its source document alive for garbage collection. If an XPathContext outlived its document and the document was collected, evaluating an XPath expression could read invalid memory and potentially segfault. This vulnerability is fixed in Nokogiri version 1.19.4 and requires verification from the supplied official sources. Defenders should prioritize verifying and upgrading to Nokogiri version 1.19.4 or later to mitigate this vulnerability. The vulnerability has a CVSS score of 1.7 and a severity of LOW.
Defensive priority
Defenders should prioritize verifying and upgrading to Nokogiri version 1.19.4 or later to mitigate this vulnerability.
Recommended defensive actions
- Verify Nokogiri version and upgrade to 1.19.4 or later
- Review application code for direct XPathContext usage
- Assess exposure in Ruby applications using Nokogiri
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The vulnerability is described in the Nokogiri security advisory GHSA-p67v-3w7g-wjg7 and is tracked in the CVE Program record and NIST NVD. The advisory provides details on the vulnerability and recommends upgrading to Nokogiri version 1.19.4 or later. Defenders should verify the vulnerability and assess exposure in Ruby applications using Nokogiri.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-57437 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-57437
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-57437 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-57437
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-p67v-3w7g-wjg7
[email protected] - Mitigation, Vendor 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.