npm package report

Is @feathersjs/authentication-oauth safe?

4 known vulnerabilities, worst severity CRITICAL.

cvss
9.3

how bad it is if exploited, out of 10

epss
0.50%

chance of exploitation in the next 30 days

xyz score
4.8

CyberXYZ composite, out of 10

fig. 01 — GHSA-wg9x-qfgw-pxhj, the advisory selected below

// advisories

GHSA-wg9x-qfgw-pxhj

CRITICALCVE-2026-29792

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

Affected
>= 5.0.0, <= 5.0.41
Fixed in
5.0.42
Weakness
CWE-287
Published
2026-03-10
Source
github

GHSANVDMITREreference

// dependencies

4 direct, 1 carrying known advisories, worst HIGH

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 02:54 UTC. The most recent advisory here was published 2026-03-10. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @feathersjs/authentication-oauth safe? npm package security report | CyberXYZ