# CVE-2026-27192: Feathers has an origin validation bypass via prefix matching

> Attackers can bypass origin validation via prefix matching to exfiltrate OAuth tokens and achieve account takeover in FeathersJS applications.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-mp4x-c34x-wv3x

## What is CVE-2026-27192?

CVE-2026-27192 is a high-severity vulnerability in feathersjs feathers, published on 21 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Feathersjs is a framework for creating web APIs and real-time applications with TypeScript or JavaScript. In versions 5.0.39 and below, origin validation uses startsWith() for comparison, allowing attackers to bypass the check by registering a domain that shares a common prefix with an allowed origin.The getAllowedOrigin() function checks if the Referer header starts with any allowed origin, and this comparison is insufficient as it only validates the prefix. This is exploitable when the origins array is configured and an attacker registers a domain starting with an allowed origin string (e.g., https://target.com.attacker.com bypasses https://target.com). On its own, tokens are still redirected to a configured origin. However, in specific scenarios an attacker can initiate the OAuth flow from an unauthorized origin and exfiltrate tokens, achieving full account takeover. This issue has bee fixed in version 5.0.40.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2026-27192?

2 open source packages ship an affected version, including @feathersjs/authentication-oauth. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@feathersjs/authentication-oauth` | npm | All versions | 5.0.40 |
| `@feathersjs/authentication-oauth` | npm | All versions | 5.0.40 |

Products: Feathersjs Feathers.

## How do I fix CVE-2026-27192?

Upgrade @feathersjs/authentication-oauth to 5.0.40 or later.

## Is CVE-2026-27192 being exploited?

There is no known exploitation of CVE-2026-27192 in the wild and no public exploit code.

## Other vulnerabilities in feathersjs feathers

- [CVE-2026-29792](https://insights.sbomify.com/CVE-2026-29792/): Feathersjs has an OAuth Callback Account Takeover (critical 9.3)
- [CVE-2026-29793](https://insights.sbomify.com/CVE-2026-29793/): NoSQL Injection via WebSocket id Parameter in MongoDB Adapter (critical 9.3)
- [CVE-2026-27193](https://insights.sbomify.com/CVE-2026-27193/): Feathers exposes internal headers via unencrypted session cookie (high 8.2)
- [CVE-2023-37899](https://insights.sbomify.com/CVE-2023-37899/): feathersjs socket handler allows abusing implicit toString (high 7.5)
- [CVE-2026-27191](https://insights.sbomify.com/CVE-2026-27191/): Feathers: Open Redirect in OAuth callback enables account takeover (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27192 and fix it if it is affected.

What it is: CVE-2026-27192 is a high-severity vulnerability in feathersjs feathers, published on 21 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-27192 in the wild and no public exploit code.

Affected packages and fixed versions:
- @feathersjs/authentication-oauth (npm): affected all versions; fixed in 5.0.40
- @feathersjs/authentication-oauth (npm): affected all versions; fixed in 5.0.40

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-27192/ (Markdown: https://insights.sbomify.com/CVE-2026-27192/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27192
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27192
- OSV: https://osv.dev/vulnerability/CVE-2026-27192

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-27192/
Summaries are generated and may contain mistakes; the official description above is the record.