https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 20:53:10 +0000 https://vulnerability.circl.lu/vuln/cve-2026-57435 <p><strong>Affected:</strong> sparklemotion nokogiri</p> <p>Nokogiri is an open source XML and HTML library for the Ruby programming language. Prior to 1.19.4, Nokogiri’s CRuby native extension could leave a Ruby wrapper pointing to freed memory when replacing the value of an XML attribute. If Ruby code had already accessed an attribute child node, Nokogiri::XML::Attr#value= could free the underlying native child node while the wrapper remained reachable through the document node cache. A later use of the freed child node or a Ruby GC mark could dereference an invalid pointer, causing an invalid read and a possible segfault. This vulnerability is fixed in 1.19.4.</p> <p><strong>Affected:</strong> sparklemotion nokogiri</p> <p>Nokogiri is an open source XML and HTML library for the Ruby programming language. Prior to 1.19.4, Nokogiri’s CRuby native extension could leave a Ruby wrapper pointing to freed memory when replacing the value of an XML attribute. If Ruby code had already accessed an attribute child node, Nokogiri::XML::Attr#value= could free the underlying native child node while the wrapper remained reachable through the document node cache. A later use of the freed child node or a Ruby GC mark could dereference an invalid pointer, causing an invalid read and a possible segfault. This vulnerability is fixed in 1.19.4.</p> https://vulnerability.circl.lu/vuln/cve-2026-57435 https://vulnerability.circl.lu/vuln/ghsa-phwj-rprq-35pp <p><strong>Affected:</strong> RubyGems: nokogiri</p> <p>### Summary</p> <p>Nokogiri’s CRuby native extension could leave a Ruby wrapper pointing to freed memory when replacing the value of an XML attribute. If Ruby code had already accessed an attribute child node, `Nokogiri::XML::Attr#value=` could free the underlying native child node while the wrapper remained reachable through the document node cache. A later use of the freed child node or a Ruby GC mark could dereference an invalid pointer, causing an invalid read and a possible segfault.</p> <p>Nokogiri 1.19.4 preserves any already-wrapped attribute child nodes before replacing the attribute value.</p> <p>JRuby is not affected.</p> <p>### Severity</p> <p>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 directly access an attribute&#39;s child node and then replace that same attribute&#39;s value via `Attr#value=` or `#content=`. Nokogiri 1.19.4 makes this pattern safe with no change to the public API. Already-wrapped attribute child nodes are preserved before the value is replaced.</p> <p>### Mitigation</p> <p>Upgrade to Nokogiri 1.19.4 or later.</p> <p>As a workaround, avoid accessing attribute child nodes directly via `Attr#child` or similar before mutating the same attribute’s value.</p> <p>### Credit</p> <p>This issue was responsibly reported by Zheng Yu from depthfirst.com.</p> <p><strong>Affected:</strong> RubyGems: nokogiri</p> <p>### Summary</p> <p>Nokogiri’s CRuby native extension could leave a Ruby wrapper pointing to freed memory when replacing the value of an XML attribute. If Ruby code had already accessed an attribute child node, `Nokogiri::XML::Attr#value=` could free the underlying native child node while the wrapper remained reachable through the document node cache. A later use of the freed child node or a Ruby GC mark could dereference an invalid pointer, causing an invalid read and a possible segfault.</p> <p>Nokogiri 1.19.4 preserves any already-wrapped attribute child nodes before replacing the attribute value.</p> <p>JRuby is not affected.</p> <p>### Severity</p> <p>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 directly access an attribute&#39;s child node and then replace that same attribute&#39;s value via `Attr#value=` or `#content=`. Nokogiri 1.19.4 makes this pattern safe with no change to the public API. Already-wrapped attribute child nodes are preserved before the value is replaced.</p> <p>### Mitigation</p> <p>Upgrade to Nokogiri 1.19.4 or later.</p> <p>As a workaround, avoid accessing attribute child nodes directly via `Attr#child` or similar before mutating the same attribute’s value.</p> <p>### Credit</p> <p>This issue was responsibly reported by Zheng Yu from depthfirst.com.</p> https://vulnerability.circl.lu/vuln/ghsa-phwj-rprq-35pp