CVE-2026-128073 with a CVSS score of 7.5 is a denial-of-service vulnerability in the gosaml2 Go library, affecting versions <= 0.11.0. The flaw is an improper input validation issue in the SAML EncryptedAssertion decryption component, specifically the AES-GCM and AES-CBC decryption paths. An unauthenticated attacker who can supply a crafted SAML Response for parsing can trigger the issue by providing an EncryptedAssertion whose CipherValue is empty or shorter than the required nonce or block size. The library attempts to slice the decoded ciphertext before completing length validation, causing a runtime panic with slice bounds out of range. Because the panic is not recovered, it can terminate the affected service provider process or goroutine before signature or content validation completes. The attack requires no valid identity provider relationship, no valid signature, and only the service provider public certificate, which is typically available in SAML metadata, to wrap a symmetric key. The business impact is availability loss, as a small malicious payload can crash the SAML service provider, interrupting authentication or single sign-on workflows and potentially requiring process restart or recovery.
We recommend you to update gosaml2 to version 0.12.0.[/subscribe_to_unlock_form]
CVE-2026-128073 with a CVSS score of 7.5 is a denial-of-service vulnerability in the gosaml2 Go library, affecting versions <= 0.11.0. The flaw is an improper input validation issue in the SAML EncryptedAssertion decryption component, specifically the AES-GCM and AES-CBC decryption paths. An unauthenticated attacker who can supply a crafted SAML Response for parsing can trigger the issue by providing an EncryptedAssertion whose CipherValue is empty or shorter than the required nonce or block size. The library attempts to slice the decoded ciphertext before completing length validation, causing a runtime panic with slice bounds out of range. Because the panic is not recovered, it can terminate the affected service provider process or goroutine before signature or content validation completes. The attack requires no valid identity provider relationship, no valid signature, and only the service provider public certificate, which is typically available in SAML metadata, to wrap a symmetric key. The business impact is availability loss, as a small malicious payload can crash the SAML service provider, interrupting authentication or single sign-on workflows and potentially requiring process restart or recovery.
We recommend you to update gosaml2 to version 0.12.0.[emaillocker id="1283"]
The following reports contain further technical details:
[/emaillocker]