dbcve.org
FeathersApplication · Feathersjs

CVE-2026-29792

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 5.0.42 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Feathersjs is a framework for creating web APIs and real-time applications with TypeScript or JavaScript. From 5.0.0 to before 5.0.42, 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. This vulnerability is fixed in 5.0.42.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FeathersJS versions 5.0.0-5.0.41 contain an authentication bypass where the OAuth service's fallback chain incorrectly trusts raw query parameters from the request. An unauthenticated attacker can send a crafted GET request to /oauth/:provider/callback with a forged profile in the query string; since no OAuth session exists (attacker never initiated the authorize flow), the fallback uses the attacker-controlled query params to look up a user entity and mint a valid JWT, granting access to existing user accounts.

MitigationUpgrade FeathersJS to version 5.0.42 or later. Additionally, audit OAuth configuration to ensure the fallback chain does not blindly trust raw request query parameters for authentication decisions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FeathersApplication
Affected:>= 5.0.0, < 5.0.42

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify FeathersJS installation and version
    Check package.json for @feathersjs/dependencies or examine node_modules/@feathersjs directory. Run 'npm list @feathersjs/feathers' or check package-lock.json for @feathersjs/feathers version entry.
    Affected if The installed @feathersjs/feathers version is >= 5.0.0 and < 5.0.42
  2. Determine if OAuth authentication is configured
    Search project configuration files (such as src/authentication.ts, config/, or similar) for OAuth-related setup including '@feathersjs/authentication-oauth' package usage, 'oauth' service configuration, or 'oauthCallback' routes.
    Affected if OAuth authentication service (@feathersjs/authentication-oauth) is installed and configured in the application
  3. Verify OAuth fallback chain exists
    Examine the authentication configuration for fallback chain definitions that may use raw request query parameters for user lookup. Look for code handling /oauth/:provider/callback routes.
    Affected if The OAuth configuration includes a fallback mechanism that processes query parameters from the callback request for user entity lookup
  4. Check for exposed OAuth callback endpoints
    Review application routing (app.ts, services/, or generated routes) to confirm /oauth/:provider/callback endpoints are publicly accessible without prior authentication.
    Affected if OAuth callback endpoints are exposed and accessible without requiring an existing OAuth session

The environment is affected if FeathersJS version is 5.0.0 through 5.0.41 AND OAuth authentication with a query parameter fallback chain is configured and the callback endpoint is publicly accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.0.42 or later
Fixed in 5.0.42
Interim mitigation

Upgrade FeathersJS to version 5.0.42 or later. Additionally, audit OAuth configuration to ensure the fallback chain does not blindly trust raw request query parameters for authentication decisions.

Recommended fix High confidence

5.0.42

  1. Upgrade FeathersJS to version 5.0.42 or later to remediate the OAuth authentication bypass vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Feathers Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29792 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29792 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data