https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T23:41:39.055807+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bell-cve-2026-57437 BELL-CVE-2026-57437 2026-10-03T23:41:39.174471+00:00

Affected: Alpaquita:stream: ruby-nokogiri

 https://cve.radiocsirt.org/vuln/brew-mikutter-cve-2026-57437 BREW-mikutter-CVE-2026-57437 — Nokogiri: Possible Use-After-Free when directly using `NokogirI::XML::XPathContext` beyond document lifetime 2026-10-03T23:41:39.174532+00:00

Affected: Homebrew: mikutter

### 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 is only reachable when application code constructs an `XPathContext` directly and lets the document become unreachable while continuing to use the context. The normal `Document#xpath`, `#css`, and related search methods are not affected, and it is not triggerable by malicious document input.

Nokogiri 1.19.4 makes `XPathContext` keep its source document alive for as long as the context exists.

Only the CRuby implementation is affected. JRuby is not affected.

### Severity

The Nokogiri maintainers have evaluated this as low severity. Reaching it requires an unusual API-usage pattern that does not arise during normal use. The application must construct an `XML::XPathContext` directly and continue using it after allowing its source document to be garbage-collected. Nokogiri 1.19.4 makes this pattern safe with no change to the public API. The context now keeps its source document alive for as long as it exists.

### Mitigation

Upgrade to Nokogiri 1.19.4 or later.

As a workaround, ensure the source document remains referenced for as long as any `XPathContext` created from it is in use. The standard `Document#xpath`, `#css`, and related search methods already do this and are unaffected.

### Credit

This issue w…

 https://cve.radiocsirt.org/vuln/euvd-2026-330285 EUVD-2026-330285 2026-10-03T23:41:39.174644+00:00 EUVD-2026-330285 https://cve.radiocsirt.org/vuln/fkie_cve-2026-57437 fkie_cve-2026-57437 2026-10-03T23:41:39.174660+00:00

Nokogiri is an open source XML and HTML library for the Ruby programming language. Prior to 1.19.4, 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 is only reachable when application code constructs an XPathContext directly and lets the document become unreachable while continuing to use the context. The normal Document#xpath, #css, and related search methods are not affected, and it is not triggerable by malicious document input. This vulnerability is fixed in 1.19.4.

 https://cve.radiocsirt.org/vuln/ghsa-p67v-3w7g-wjg7 GHSA-p67v-3w7g-wjg7 — Nokogiri: Possible Use-After-Free when directly using `NokogirI::XML::XPathContext` beyond document lifetime 2026-10-03T23:41:39.174686+00:00

Affected: RubyGems: nokogiri

### 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 is only reachable when application code constructs an `XPathContext` directly and lets the document become unreachable while continuing to use the context. The normal `Document#xpath`, `#css`, and related search methods are not affected, and it is not triggerable by malicious document input.

Nokogiri 1.19.4 makes `XPathContext` keep its source document alive for as long as the context exists.

Only the CRuby implementation is affected. JRuby is not affected.

### Severity

The Nokogiri maintainers have evaluated this as low severity. Reaching it requires an unusual API-usage pattern that does not arise during normal use. The application must construct an `XML::XPathContext` directly and continue using it after allowing its source document to be garbage-collected. Nokogiri 1.19.4 makes this pattern safe with no change to the public API. The context now keeps its source document alive for as long as it exists.

### Mitigation

Upgrade to Nokogiri 1.19.4 or later.

As a workaround, ensure the source document remains referenced for as long as any `XPathContext` created from it is in use. The standard `Document#xpath`, `#css`, and related search methods already do this and are unaffected.

### Credit

This issue w…

 https://cve.radiocsirt.org/vuln/msrc_cve-2026-57437 msrc_CVE-2026-57437 — Nokogiri: Possible Use-After-Free when directly using `NokogirI::XML::XPathContext` beyond document lifetime 2026-10-03T23:41:39.174725+00:00 msrc_CVE-2026-57437 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-57437 UBUNTU-CVE-2026-57437 2026-10-03T23:41:39.174744+00:00

Affected: Ubuntu:Pro:14.04:LTS: ruby-nokogiri, Ubuntu:16.04:LTS: ruby-nokogiri, Ubuntu:18.04:LTS: ruby-nokogiri, Ubuntu:Pro:20.04:LTS: ruby-nokogiri, Ubuntu:Pro:22.04:LTS: ruby-nokogiri, Ubuntu:24.04:LTS: ruby-nokogiri, Ubuntu:25.10: ruby-nokogiri, Ubuntu:26.04:LTS: ruby-nokogiri

Nokogiri is an open source XML and HTML library for the Ruby programming language. Prior to 1.19.4, 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 is only reachable when application code constructs an XPathContext directly and lets the document become unreachable while continuing to use the context. The normal Document#xpath, #css, and related search methods are not affected, and it is not triggerable by malicious document input. This vulnerability is fixed in 1.19.4.