Attack Chain

1. An attacker identifies a SAML integration using a vulnerable version of samlify.
2. The attacker crafts a malicious input containing XML markup designed to inject a new attribute (e.g., ‘role=admin’) into the SAML assertion. This input is typically injected via a user-controlled field such as email or name.
3. The attacker authenticates with the Identity Provider (IdP), triggering the SAML assertion generation process.
4. The IdP’s replaceTagsByValue() function fails to properly escape the malicious XML markup within the <saml:AttributeValue> tag.
5. The IdP signs the tampered SAML assertion, including the attacker-injected attribute.
6. The IdP sends the modified SAML assertion to the Service Provider (SP).
7. The SP uses sp.parseLoginResponse() to parse the SAML assertion. Due to the injected attribute being signed by the IdP, the SP trusts the injected attribute.
8. The attacker gains elevated privileges within the SP application because the SP uses the injected attribute (e.g., ‘role=admin’) for authorization decisions.

Impact

Successful exploitation of this vulnerability (CVE-2026-46490) allows attackers to escalate privileges within applications that rely on SAML for authentication and authorization. A normal user can inject arbitrary attributes (e.g., role=admin) into a signed assertion and have them parsed by sp.parseLoginResponse(). This can lead to unauthorized access to sensitive data, modification of critical system settings, or other malicious activities, depending on how the application uses SAML attributes.

Recommendation

• Upgrade to samlify version 2.13.0 or later to remediate the XML injection vulnerability (CVE-2026-46490).
• Implement server-side input validation and sanitization to prevent XML injection in SAML attribute values.
• Deploy the Sigma rule Detect Samlify XML Injection Attempt in SAML Response to detect potential exploitation attempts.