How severe is GHSA-wg9x-qfgw-pxhj?

No CVSS score has been assigned to GHSA-wg9x-qfgw-pxhj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wg9x-qfgw-pxhj?

GHSA-wg9x-qfgw-pxhj affects the following packages: @feathersjs/authentication-oauth (npm). Ecosystems affected: npm.

How do I fix GHSA-wg9x-qfgw-pxhj?

Update @feathersjs/authentication-oauth to 5.0.42 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wg9x-qfgw-pxhj is resolved across your whole dependency graph.

How do I detect GHSA-wg9x-qfgw-pxhj in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @feathersjs/authentication-oauth. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-wg9x-qfgw-pxhj 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-wg9x-qfgw-pxhj?

O3 pinpoints whether GHSA-wg9x-qfgw-pxhj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-wg9x-qfgw-pxhj actively exploited in the wild?

No public exploit code has been indexed for GHSA-wg9x-qfgw-pxhj 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.

What is the EPSS score for GHSA-wg9x-qfgw-pxhj?

GHSA-wg9x-qfgw-pxhj has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-wg9x-qfgw-pxhj?

GHSA-wg9x-qfgw-pxhj is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-wg9x-qfgw-pxhj published, and has it been updated?

GHSA-wg9x-qfgw-pxhj was published on March 10, 2026 and was last updated on March 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-wg9x-qfgw-pxhj

Feathers has an OAuth Callback Account Takeover issue

Also known asCVE-2026-29792

Published

Mar 10, 2026

Updated

Mar 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk40th percentile+0.44%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

📦@feathersjs/authentication-oauth

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

Description

An unauthenticated attacker can send a crafted GET request directly to /oauth/:provider/callback with a forged profile in the query string. The OAuth service's authentication payload has a fallback chain that reaches params.query (the raw request query) when Grant's session/state responses are empty. Since the attacker never initiated an OAuth authorize flow, Grant has no session to work with and produces no response, so the fallback fires. The forged profile then drives entity lookup and JWT minting. The attacker gets a valid access token for an existing user without ever contacting the OAuth provider. Critical (CVSS 9.8)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@feathersjs/authentication-oauth`	≥ 5.0.0&&< 5.0.42	5.0.42

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @feathersjs/authentication-oauth. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @feathersjs/authentication-oauth to 5.0.42 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wg9x-qfgw-pxhj 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 pinpoints whether GHSA-wg9x-qfgw-pxhj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wg9x-qfgw-pxhj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An unauthenticated attacker can send a crafted GET request directly to `/oauth/:provider/callback` with a forged profile in the query string. The OAuth service's authentication payload has a fallback chain that reaches params.query (the raw request query) when Grant's session/state responses are empty. Since the attacker never initiated an OAuth authorize flow, Grant has no session to work with and produces no response, so the fallback fires. The forged profile then drives entity lookup and JWT minting. The attacker gets a valid access token for an existing user without ever contacting the OAu

O3 Security · Impact-Aware SCA

Is GHSA-wg9x-qfgw-pxhj in your dependencies?

O3 detects GHSA-wg9x-qfgw-pxhj across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works