How severe is GHSA-hw46-3hmr-x9xv?

No CVSS score has been assigned to GHSA-hw46-3hmr-x9xv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hw46-3hmr-x9xv?

GHSA-hw46-3hmr-x9xv affects the following packages: omniauth-saml (RubyGems), omniauth-saml (RubyGems), omniauth-saml (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-hw46-3hmr-x9xv?

Update omniauth-saml to 2.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hw46-3hmr-x9xv is resolved across your whole dependency graph.

How do I detect GHSA-hw46-3hmr-x9xv in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for omniauth-saml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hw46-3hmr-x9xv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hw46-3hmr-x9xv?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hw46-3hmr-x9xv can be triaged on real exposure rather than presence alone.

Is GHSA-hw46-3hmr-x9xv actively exploited in the wild?

No public exploit code has been indexed for GHSA-hw46-3hmr-x9xv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-hw46-3hmr-x9xv published, and has it been updated?

GHSA-hw46-3hmr-x9xv was published on March 12, 2025 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

Not in CISA KEV

GHSA-hw46-3hmr-x9xv — omniauth-saml

Fix: omniauth/omniauth-saml@0d5eaa0

GHSA-hw46-3hmr-x9xv is a security vulnerability in omniauth-saml. A fix is available for omniauth-saml — see the affected versions and patch details below.

omniauth-saml has dependency on ruby-saml version with Signature Wrapping Attack issue

Published

Mar 12, 2025

Updated

Feb 4, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Feb 4, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

💎omniauth-saml💎omniauth-saml💎omniauth-saml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Summary

There are 2 new Critical Signature Wrapping Vulnerabilities (CVE-2025-25292, CVE-2025-25291) and a potential DDOS Moderated Vulneratiblity (CVE-2025-25293) affecting ruby-saml, a dependency of omniauth-saml.

The fix will be applied to ruby-saml and released 12 March 2025, under version 1.18.0.

Please upgrade the ruby-saml requirement to v1.18.0.

Impact

Signature Wrapping Vulnerabilities allows an attacker to impersonate a user.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`omniauth-saml`	≥ 2.2.0&&< 2.2.3	2.2.3`bundle update omniauth-saml --conservative`
💎RubyGems	`omniauth-saml`	≥ 2.0.0&&< 2.1.3	2.1.3`bundle update omniauth-saml --conservative`
💎RubyGems	`omniauth-saml`	all versions	1.10.6`bundle update omniauth-saml --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for omniauth-saml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update omniauth-saml to 2.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hw46-3hmr-x9xv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hw46-3hmr-x9xv can be triaged on real exposure rather than presence alone.

Tailored to GHSA-hw46-3hmr-x9xv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary There are 2 new Critical Signature Wrapping Vulnerabilities (CVE-2025-25292, CVE-2025-25291) and a potential DDOS Moderated Vulneratiblity (CVE-2025-25293) affecting ruby-saml, a dependency of omniauth-saml. The fix will be applied to ruby-saml and released 12 March 2025, under version 1.18.0. Please [upgrade](https://github.com/omniauth/omniauth-saml/blob/master/omniauth-saml.gemspec#L16) the ruby-saml requirement to v1.18.0. ### Impact Signature Wrapping Vulnerabilities allows an attacker to impersonate a user.

O3 Security · Impact-Aware SCA

Is GHSA-hw46-3hmr-x9xv in your dependencies?

O3 Security finds GHSA-hw46-3hmr-x9xv across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works