CVE-2026-128073: gosaml2 · Unauthenticated panic decrypting an EncryptedAssertion with a short or empty CipherValue
Affects github.com/russellhaering/gosaml2Source GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 0.12.0 soon.
Data as of 19 Nov 2026, 21:05 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 0.12.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade github.com/russellhaering/gosaml2 to 0.12.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/russellhaering/gosaml2 | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in gosaml2 version 0.12.0 that fixes this vulnerability by adding proper length checks in the AES-GCM decryption path. Users should upgrade to version 0.12.0 or later to remediate this issue. No other mitigation is required as the vulnerability is fixed in the official release.
Description
A vulnerability in the gosaml2 library allows an unauthenticated attacker to cause a panic (crash) by sending a crafted SAML Response containing an EncryptedAssertion with AES-GCM encryption and a CipherValue shorter than the required 12-byte nonce size. This triggers a slice bounds out of range panic during decryption before any signature or content validation occurs. The issue affects gosaml2 versions prior to 0.12.0 and does not require a valid signature, only the service provider's public certificate. A fix is available in version 0.12.0.
References
- github.com/russellhaering/gosaml2/security/advisories/GHSA-5hj8-q7fv-qrj6 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-128073 (opens in a new tab)
- github.com/russellhaering/gosaml2/pull/281 (opens in a new tab)
- github.com/russellhaering/gosaml2/commit/b2bd784b196b21f606faaa6a4eeae929bd75aa20 (opens in a new tab)
- github.com/russellhaering/gosaml2 (opens in a new tab)
- github.com/russellhaering/gosaml2/releases/tag/v0.12.0 (opens in a new tab)