<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 08:21:42 +0000</lastBuildDate>
    <item>
      <title>GHSA-9cv2-cfxc-v4v2 — Nokogiri: Null Pointer Dereference calling methods on uninitialized wrapper classes</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-9cv2-cfxc-v4v2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: nokogiri&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Nokogiri contains a bug when calling certain methods on allocated-but-uninitialized native wrapper classes that inherit from `Nokogiri::XML::Node`. This caused a NULL pointer dereference that could crash the process.&lt;/p&gt;
&lt;p&gt;Nokogiri 1.19.4 checks for missing native data pointers and raises a `RuntimeError`.&lt;/p&gt;
&lt;p&gt;JRuby is not affected.&lt;/p&gt;
&lt;p&gt;### Severity&lt;/p&gt;
&lt;p&gt;The Nokogiri maintainers have evaluated this as low severity. This is only triggered by a programming error. It requires application code to call `.allocate` directly on a native-backed class and then invoke methods on the resulting uninitialized object. It cannot be triggered by untrusted input or through normal use of the public API.&lt;/p&gt;
&lt;p&gt;### Mitigation&lt;/p&gt;
&lt;p&gt;Upgrade to Nokogiri 1.19.4 or later.&lt;/p&gt;
&lt;p&gt;Avoid calling `.allocate` directly on Nokogiri native-backed classes. Use the documented constructors and factory methods instead.&lt;/p&gt;
&lt;p&gt;### Credit&lt;/p&gt;
&lt;p&gt;This issue was responsibly reported by Zheng Yu from depthfirst.com.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: nokogiri&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Nokogiri contains a bug when calling certain methods on allocated-but-uninitialized native wrapper classes that inherit from `Nokogiri::XML::Node`. This caused a NULL pointer dereference that could crash the process.&lt;/p&gt;
&lt;p&gt;Nokogiri 1.19.4 checks for missing native data pointers and raises a `RuntimeError`.&lt;/p&gt;
&lt;p&gt;JRuby is not affected.&lt;/p&gt;
&lt;p&gt;### Severity&lt;/p&gt;
&lt;p&gt;The Nokogiri maintainers have evaluated this as low severity. This is only triggered by a programming error. It requires application code to call `.allocate` directly on a native-backed class and then invoke methods on the resulting uninitialized object. It cannot be triggered by untrusted input or through normal use of the public API.&lt;/p&gt;
&lt;p&gt;### Mitigation&lt;/p&gt;
&lt;p&gt;Upgrade to Nokogiri 1.19.4 or later.&lt;/p&gt;
&lt;p&gt;Avoid calling `.allocate` directly on Nokogiri native-backed classes. Use the documented constructors and factory methods instead.&lt;/p&gt;
&lt;p&gt;### Credit&lt;/p&gt;
&lt;p&gt;This issue was responsibly reported by Zheng Yu from depthfirst.com.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-9cv2-cfxc-v4v2</guid>
    </item>
  </channel>
</rss>
