Skip to main content
VulnerabilityPublished

XML Signature Wrapping authentication bypass in Moldova's MPass SAML NuGet library, fixed in 10.0.4 (CVE requested, CAN-2026-2041077)

Source Reddit NetSec

0

Fixed in 10.0.4 : update affected systems when convenient.

Data as of 29 Oct 2026, 01:11 UTC

Severity
Medium

Rated by Threat Radar

Patch
Available – fixed in 10.0.4

What to do

AI-suggested

Upgrade to MPass SAML NuGet library versions 10.0.4 or 10.0.5 where the vulnerability is fixed. The fix enforces that the signed reference matches the root element ID, preventing signature wrapping attacks. No other mitigation is required as the issue is resolved in these versions.

Discussion

An XML Signature Wrapping vulnerability in Moldova's MPass SAML NuGet library allows authentication bypass by relocating signed elements within SAML responses. This flaw affects versions 8.0.53 to 8.0.56 and 10.0.2 and was fixed in versions 10.0.4 and 10.0.5. The issue arises because the signature verification did not ensure that the signed reference matched the root element of the response, enabling attackers to authenticate as arbitrary users.

r/netsec (opens in a new tab)u/maxim-masiutin0 points0 comments

Egov.Integrations.MPass.Saml, the ASP.NET Core handler that relying parties use to verify MPass SAML 2.0 responses, verified signatures like this in every version before 10.0.4:

signedXml.LoadXml(signatureElement); return signedXml.CheckSignature(publicCertificate, verifySignatureOnly: true);

CheckSignature confirms that the references in SignedInfo are validly signed. Nothing tied a signed reference to the response root the relying party then reads, so anyone holding one validly signed MPass message could relocate the signed element, put chosen assertion content at the root, and still pass verification. The result is authentication as an arbitrary user. Version 10.0.4 adds the missing check: exactly one reference, and its URI must equal the root element ID.

  • Weakness: CWE-347 (Improper Verification of Cryptographic Signature)
  • Attack pattern: CAPEC-475 (Signature Spoofing by Improper Validation)
  • Affected: 8.0.53 to 8.0.56 and 10.0.2
  • Fixed: 10.0.4 and 10.0.5

Serghei Zagaiciuc found and publicly disclosed the flaw. I confirmed the affected range and the fix by decompiling the published packages. I have submitted a CVE ID request through the MITRE CNA of Last Resort form; so far it has a tracking number, CAN-2026-2041077, and no CVE ID has been assigned yet. No exploit is published.

References

Community reviews

Loading reviews…