GHSA-wg9x-qfgw-pxhj — @feathersjs/authenticatio…
GHSA-wg9x-qfgw-pxhj is a Improper Authentication vulnerability in @feathersjs/authentication-oauth. A fix is available for @feathersjs/authentication-oauth — see the affected versions and patch details below.
Feathers has an OAuth Callback Account Takeover issue
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-wg9x-qfgw-pxhj.
EPSS Exploitation Probability
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.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@feathersjs/authentication-oauthnpmDescription
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @feathersjs/authentication-oauth | ≥ 5.0.0&&< 5.0.42 | 5.0.42npm install @feathersjs/authentication-oauth@5.0.42 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @feathersjs/authentication-oauth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wg9x-qfgw-pxhj can be triaged on real exposure rather than presence alone.
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
Is GHSA-wg9x-qfgw-pxhj in your dependencies?
O3 Security finds GHSA-wg9x-qfgw-pxhj across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.