Skip to main content
Mallory
MediumVulnerability

CVE-2026-79772: SAML Signature-Validation Bypass via Nokogiri Canonicalization Error Handling

Published Aug 25, 2026 · Updated 29 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.9Medium · v4
EPSS0.34%28th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Nokogiri
IdentifiersCVE-2026-79772CWE-252 · Unchecked Return Value

Nokogiri versions before 1.19.1 fail to check the return value of xmlC14NExecute in the CRuby extension's canonicalize method. When XML canonicalization fails, the method returns an empty string instead of raising an exception. Downstream SAML libraries that fail to detect this error can incorrectly accept invalid XML during signature validation, enabling signature-validation bypass. JRuby implementations are not affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Affected downstream SAML applications can incorrectly accept XML whose signature validation should fail, compromising the integrity of signature-based security decisions. Authentication or authorization consequences depend on how the application uses the accepted SAML data.

Mitigation

If you can’t patch tonight, do this now.

Until an upgrade is possible, independently detect canonicalization failures and ensure downstream SAML/XML signature-validation code rejects empty or invalid canonicalization results. Do not assume canonicalization failures will raise exceptions.

Remediation

Patch, then assume compromise.

Upgrade the nokogiri RubyGem to version 1.19.1 or later in affected CRuby deployments. Ensure applications load the updated dependency. JRuby implementations do not require remediation for this vulnerability.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
NokogiriNokogiriapplication
FAQ

Frequently asked questions

Is CVE-2026-79772 exploited in the wild?
Yes. As of Oct 23, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-79772?
As of Oct 23, 2026, Mallory has found no public exploit for CVE-2026-79772.
Is there a patch for CVE-2026-79772?
Upgrade the nokogiri RubyGem to version 1.19.1 or later in affected CRuby deployments. Ensure applications load the updated dependency.
What products are affected by CVE-2026-79772?
Nokogiri.
How severe is CVE-2026-79772?
CVE-2026-79772 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 0.34% (28th percentile) as of Oct 23, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.