Given a valid SAML Response, an attacker can potentially modify the document, bypassing…
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-347.
Summary
### Impact Given a valid SAML Response, an attacker can potentially modify the document, bypassing signature validation in order to pass off the altered document as a signed one. This enables a variety of attacks, including users accessing accounts other than the one to which they authenticated in the identity provider, or full authentication bypass if an external attacker can obtain an expired, signed SAML Response. ### Patches A patch is available, users of gosaml2 should upgrade to v0.5.0 or higher. ### References See the [underlying advisory on goxmldsig](https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7) for more details.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | github.com/russellhaering/gosaml2 (Go) | before 0.5.0 | 0.5.0 | Patch available | GHSA-5684-g483-2249 |
- github.com/russellhaering/gosaml2 (Go) Vendor— Affected before 0.5.0 Fixed in 0.5.0 Patch available GHSA-5684-g483-2249
Remediation
- Fix · GHSA-5684-g483-2249 github.com/russellhaering/gosaml2 (Go) Fixed in 0.5.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-5684-g483-2249
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences