Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIntercept XML message with GCM-encrypted nodes
-
ExploitBrute-force missing authentication tag validation
-
ExecutionRecover GHASH key from encryption
-
ImpactDecrypt sensitive XML content or forge ciphertexts
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Integrity verification
|
| Exploitation Conditions | xml-security library versions before 2.3.1 processing XML messages encrypted with aes-128-gcm, aes-192-gcm, or aes-256-gcm algorithms. No authentication required; remote attacker can intercept and manipulate encrypted XML nodes in transit. |
| Impact | Despite the high CVSS score of 8.2, real-world exploitation risk appears moderate. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates remote exploitation with no authentication required, which is concerning. However, no EPSS score is provided, suggesting limited observed exploitation activity. The vulnerability is not listed in CISA KEV, indicating no known active exploitation. The attack requires brute-forcing authentication tags, which while feasible, requires computational resources and may be detectable. The primary impact is confidentiality (C:H) with limited integrity impact (I:L), making this most critical for organizations handling sensitive data via SAML/XML encryption. |
| Exploit ScenarioDerived | An attacker intercepts encrypted SAML assertions or XML messages between an identity provider and service provider. Without proper tag validation, they can manipulate the authentication tag and attempt brute-force attacks to recover the GHASH key. Once successful, they can decrypt sensitive user data, authentication tokens, or personal information contained in the XML. Additionally, they could forge malicious encrypted XML nodes that would be accepted as valid, potentially injecting false authentication claims or modifying user attributes. No public POC is referenced, but the attack is theoretically straightforward for skilled cryptographic attackers with access to encrypted traffic. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 13, 2026
Critical authentication bypass vulnerability in the simplesamlphp/xml-security library (versions before 2.3.1) that affects XML encryption using AES-GCM modes. Attackers can exploit missing authentication tag validation to brute-force decryption keys, decrypt sensitive XML data, and forge arbitrary ciphertexts without knowing encryption keys. No active exploitation detected (not in KEV), but the high CVSS score (8.2) and network-based attack vector make this a priority for organizations using affected SAML/XML security implementations.
RemediationAI
Primary remediation: Upgrade to xml-security version 2.3.1 or later, which includes the fix (commit fdc12449e959c610943f9fd428e95e3832d74c25). The patch adds proper validation of authentication tag length for GCM modes. Workaround: If immediate patching is not possible, consider temporarily switching to non-GCM encryption modes (e.g., AES-CBC) if your implementation allows, though this may have other security implications. Review the vendor advisory at https://github.com/simplesamlphp/xml-security/security/advisories/GHSA-r353-4845-pr5p for detailed guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in composer, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The xml-security library (CPE: cpe:2.3:a:simplesamlphp:xml-security:*:*:*:*:*:*:*:*) implements XML encryption and digital signatures, commonly used in SAML authentication flows. The vulnerability stems from CWE-354 (Improper Validation of Integrity Check Value) where AES-GCM encrypted XML nodes fail to validate the authentication tag length. GCM mode provides authenticated encryption, but without proper tag validation, the cryptographic integrity protection is compromised. This affects all versions prior to 2.3.1 when using aes-128-gcm, aes-192-gcm, or aes-256-gcm encryption algorithms.
Know when Xml Security gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
2DescriptionGitHub Advisory
xml-security is a library that implements XML signatures and encryption. Prior to 2.3.1, XML nodes encrypted with either aes-128-gcm, aes-192-gcm, or aes-256-gcm lack validation of the authentication tag length. An attacker can use this to brute-force an authentication tag, recover the GHASH key, and decrypt the encrypted nodes. It also allows to forge arbitrary ciphertexts without knowing the encryption key. This vulnerability is fixed in 2.3.1.
Executive ViewAI
CVE-2026-32600 is a high-severity authentication bypass affecting XML encryption in SAML implementations that could allow attackers to decrypt sensitive data and forge authentication tokens without knowing encryption keys. Organizations using affected versions of simplesamlphp/xml-security library face potential compromise of identity and access controls, putting user accounts, confidential communications, and system integrity at risk.
Implement network segmentation to restrict access to SAML/XML processing endpoints; enable detailed audit logging for XML decryption failures and authentication attempts; deploy WAF rules to detect anomalous XML payloads or excessive decryption requests; consider disabling AES-GCM mode if alternative encryption methods are available; enforce mutual TLS (mTLS) for SAML service communications; increase monitoring for failed authentication events and encrypted data access patterns. Note: These are temporary mitigations only; patch application is mandatory when available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-12099
GHSA-r353-4845-pr5p
NVD
CVE.org
EPSS
VulDB
Exploit-DB