What is GHSA-CVP8-5R8G-FHVQ?

GHSA-CVP8-5R8G-FHVQ is a critical-severity security vulnerability in omniauth-saml (rubygems), affecting versions >= 2.0.0, < 2.1.2. It is fixed in 2.1.2, 1.10.5, 2.2.1.

How severe is GHSA-CVP8-5R8G-FHVQ?

GHSA-CVP8-5R8G-FHVQ has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of omniauth-saml are affected by GHSA-CVP8-5R8G-FHVQ?

omniauth-saml (rubygems) versions >= 2.0.0, < 2.1.2 is affected.

Is there a fix for GHSA-CVP8-5R8G-FHVQ?

Yes. GHSA-CVP8-5R8G-FHVQ is fixed in 2.1.2, 1.10.5, 2.2.1. Upgrade to this version or later.

Is GHSA-CVP8-5R8G-FHVQ exploitable, and should I be worried?

Whether GHSA-CVP8-5R8G-FHVQ 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.

What actually determines whether GHSA-CVP8-5R8G-FHVQ 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.

GHSA-CVP8-5R8G-FHVQ in omniauth-saml

Q: How severe is GHSA-CVP8-5R8G-FHVQ?

GHSA-CVP8-5R8G-FHVQ has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of omniauth-saml are affected by GHSA-CVP8-5R8G-FHVQ?

omniauth-saml (rubygems) versions >= 2.0.0, < 2.1.2 is affected.

Q: Is there a fix for GHSA-CVP8-5R8G-FHVQ?

Yes. GHSA-CVP8-5R8G-FHVQ is fixed in 2.1.2, 1.10.5, 2.2.1. Upgrade to this version or later.

Q: Is GHSA-CVP8-5R8G-FHVQ exploitable, and should I be worried?

Whether GHSA-CVP8-5R8G-FHVQ 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.

Q: What actually determines whether GHSA-CVP8-5R8G-FHVQ 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.

Q: How do I fix GHSA-CVP8-5R8G-FHVQ?

Upgrade: omniauth-saml to 2.1.2 or later, omniauth-saml to 1.10.5 or later, omniauth-saml to 2.2.1 or later.

Summary

omniauth-saml vulnerable to Improper Verification of Cryptographic Signature

ruby-saml, the dependent SAML gem of omniauth-saml has a signature wrapping vulnerability in <= v1.12.0 and v1.13.0 to v1.16.0 , see https://github.com/SAML-Toolkits/ruby-saml/security/advisories/GHSA-jw9c-mfg7-9rx2
As a result, omniauth-saml created a new release by upgrading ruby-saml to the patched versions v1.17.

Impact

GHSA-CVP8-5R8G-FHVQ has a CVSS score of 10.0 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.1.2, 1.10.5, 2.2.1); upgrading removes the vulnerable code path.

Affected versions

omniauth-saml (>= 2.0.0, < 2.1.2) omniauth-saml (< 1.10.5) omniauth-saml (>= 2.2.0, < 2.2.1)

Security releases

omniauth-saml → 2.1.2 (rubygems) omniauth-saml → 1.10.5 (rubygems) omniauth-saml → 2.2.1 (rubygems)

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 environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

omniauth-saml to 2.1.2 or later; omniauth-saml to 1.10.5 or later; omniauth-saml to 2.2.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-CVP8-5R8G-FHVQ? GHSA-CVP8-5R8G-FHVQ is a critical-severity security vulnerability in omniauth-saml (rubygems), affecting versions >= 2.0.0, < 2.1.2. It is fixed in 2.1.2, 1.10.5, 2.2.1.
How severe is GHSA-CVP8-5R8G-FHVQ? GHSA-CVP8-5R8G-FHVQ has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of omniauth-saml are affected by GHSA-CVP8-5R8G-FHVQ? omniauth-saml (rubygems) versions >= 2.0.0, < 2.1.2 is affected.
Is there a fix for GHSA-CVP8-5R8G-FHVQ? Yes. GHSA-CVP8-5R8G-FHVQ is fixed in 2.1.2, 1.10.5, 2.2.1. Upgrade to this version or later.
Is GHSA-CVP8-5R8G-FHVQ exploitable, and should I be worried? Whether GHSA-CVP8-5R8G-FHVQ 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
What actually determines whether GHSA-CVP8-5R8G-FHVQ 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.
How do I fix GHSA-CVP8-5R8G-FHVQ?
- Upgrade omniauth-saml to 2.1.2 or later
- Upgrade omniauth-saml to 1.10.5 or later
- Upgrade omniauth-saml to 2.2.1 or later

Other vulnerabilities in omniauth-saml

CVE-IDSeverityPackage summary

GHSA-HW46-3HMR-X9XVCriticalomniauth-saml: omniauth-saml has dependency on ruby-saml version with Signature Wrapping Attack issue CVE-2017-11430Highomniauth-saml: OmniAuth-SAML authentication bypass via incorrect XML canonicalization and DOM traversal