Most recent entries from all

BELL-CVE-2026-79772

Affected: Alpaquita:23: ruby-nokogiri, Alpaquita:25: ruby-nokogiri, Alpaquita:stream: ruby-nokogiri

BREW-mikutter-CVE-2026-79772 — Nokogiri does not check the return value from xmlC14NExecute

Affected: Homebrew: mikutter

## Summary

Nokogiri's CRuby extension fails to check the return value from `xmlC14NExecute` in the method `Nokogiri::XML::Document#canonicalize` and `Nokogiri::XML::Node#canonicalize`. When canonicalization fails, an empty string is returned instead of raising an exception. This incorrect return value may allow downstream libraries to accept invalid or incomplete canonicalized XML, which has been demonstrated to enable signature validation bypass in SAML libraries.

JRuby is not affected, as the Java implementation correctly raises `RuntimeError` on canonicalization failure.

## Mitigation

Upgrade to Nokogiri `>= 1.19.1`.

## Severity

The maintainers have assessed this as **Medium** severity. Nokogiri itself is a parsing library without a clear security boundary related to canonicalization, so the direct impact is that a method returns incorrect data on invalid input. However, this behavior was exploited in practice to bypass SAML signature validation in downstream libraries (see References).

## Credit

This vulnerability was responsibly reported by HackerOne researcher `d4d`.

EUVD-2026-361467

fkie_cve-2026-79772

Nokogiri versions before 1.19.1 fail to check the return value from xmlC14NExecute in the canonicalize method, returning an empty string on failure instead of raising an exception. Attackers can exploit this to bypass signature validation in downstream SAML libraries by providing invalid canonicalized XML that is incorrectly accepted as valid.

GHSA-wx95-c6cv-8532 — Nokogiri does not check the return value from xmlC14NExecute

Affected: RubyGems: nokogiri