GHSA-5684-G483-2249

GHSA-5684-G483-2249 is a critical-severity security vulnerability in github.com/russellhaering/gosaml2 (go), affecting versions < 0.5.0. It is fixed in 0.5.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Signature Validation Bypass

References

See the underlying advisory on goxmldsig for more details.

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.

Affected versions

github.com/russellhaering/gosaml2 (< 0.5.0)

Security releases

github.com/russellhaering/gosaml2 → 0.5.0 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

A patch is available, users of gosaml2 should upgrade to v0.5.0 or higher.

Frequently Asked Questions

  1. What is GHSA-5684-G483-2249? GHSA-5684-G483-2249 is a critical-severity security vulnerability in github.com/russellhaering/gosaml2 (go), affecting versions < 0.5.0. It is fixed in 0.5.0.
  2. Which versions of github.com/russellhaering/gosaml2 are affected by GHSA-5684-G483-2249? github.com/russellhaering/gosaml2 (go) versions < 0.5.0 is affected.
  3. Is there a fix for GHSA-5684-G483-2249? Yes. GHSA-5684-G483-2249 is fixed in 0.5.0. Upgrade to this version or later.
  4. Is GHSA-5684-G483-2249 exploitable, and should I be worried? Whether GHSA-5684-G483-2249 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether GHSA-5684-G483-2249 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix GHSA-5684-G483-2249? Upgrade github.com/russellhaering/gosaml2 to 0.5.0 or later.

Other vulnerabilities in github.com/russellhaering/gosaml2

Stop the waste.
Protect your environment with Kodem.