CVE-2026-32600
Awaiting Analysis Awaiting Analysis - Queue
Authentication Tag Validation Bypass in xml-security Enables Decryption

Publication date: 2026-03-16

Last updated on: 2026-03-17

Assigner: GitHub, Inc.

Description
xml-security is a library that implements XML signatures and encryption. Prior to versions 2.3.1 and 1.13.9, 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 and 1.13.9.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-16
Last Modified
2026-03-17
Generated
2026-05-06
AI Q&A
2026-03-16
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
simplesamlphp xml-security to 1.13.9 (exc)
simplesamlphp xml-security From 2.0.0 (inc) to 2.3.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-354 The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, you should upgrade the xml-security library to version 2.3.1 or later, or version 1.13.9 or later, where the issue with authentication tag length validation is fixed.


Can you explain this vulnerability to me?

This vulnerability exists in the xml-security library versions prior to 2.3.1 and 1.13.9. The issue is that XML nodes encrypted with aes-128-gcm, aes-192-gcm, or aes-256-gcm do not properly validate the length of the authentication tag. Because of this, an attacker can brute-force the authentication tag, recover the GHASH key, and decrypt the encrypted XML nodes. Additionally, the attacker can forge arbitrary ciphertexts without knowing the encryption key.


How can this vulnerability impact me? :

The vulnerability can lead to unauthorized decryption of encrypted XML data, exposing sensitive information. It also allows attackers to forge ciphertexts, potentially leading to data tampering or injection of malicious data. This compromises the confidentiality and integrity of the data protected by the xml-security library.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart