Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-27191: CWE-601: URL Redirection to Untrusted Site ('Open Redirect') in feathersjs feathers

0
High
VulnerabilityCVE-2026-27191cvecve-2026-27191cwe-601
Published: Sat Feb 21 2026 (02/21/2026, 03:23:28 UTC)
Source: CVE Database V5
Vendor/Project: feathersjs
Product: feathers

Description

CVE-2026-27191 is a high-severity open redirect vulnerability in the feathersjs framework versions below 5. 0. 40. The flaw arises from improper validation of the redirect query parameter, allowing attackers to craft URLs that cause browsers to interpret attacker-controlled domains as the host. This enables theft of access tokens via URL authority injection, leading to full account takeover without requiring prior authentication but needing user interaction. The vulnerability is fixed in version 5. 0. 40. Organizations using vulnerable versions of feathersjs in web APIs or real-time applications are at risk of impersonation attacks. Mitigation requires upgrading to 5.

AI-Powered Analysis

AILast updated: 02/21/2026, 04:16:41 UTC

Technical Analysis

CVE-2026-27191 is an open redirect vulnerability classified under CWE-601 affecting the feathersjs framework, a popular tool for building web APIs and real-time applications using JavaScript or TypeScript. In versions 5.0.39 and earlier, the application constructs redirect URLs by concatenating a base origin with a user-supplied redirect query parameter without proper validation. When the origins array is configured improperly—specifically when origin values do not end with a trailing slash—an attacker can exploit this by injecting an '@' character followed by an attacker-controlled domain in the redirect parameter. For example, supplying a redirect value like '@attacker.com' results in a URL such as https://target.com@attacker.com#access_token=..., which browsers interpret as pointing to attacker.com rather than target.com. This URL authority injection allows attackers to steal access tokens embedded in the URL fragment, enabling them to impersonate victims and achieve full account takeover. The vulnerability requires user interaction (clicking a crafted link) but no prior authentication or privileges. It has been assigned a CVSS 4.0 score of 7.4 (high severity), reflecting the significant impact on confidentiality and integrity, with moderate attack complexity and user interaction required. The issue was addressed and fixed in feathersjs version 5.0.40 by properly validating and sanitizing redirect parameters to prevent URL authority injection.

Potential Impact

The primary impact of this vulnerability is the potential for full account takeover of users interacting with applications built on vulnerable versions of feathersjs. Attackers can steal access tokens by tricking users into clicking maliciously crafted URLs that exploit the open redirect flaw. This compromises user confidentiality and integrity, allowing attackers to impersonate victims, access sensitive data, and perform unauthorized actions within the affected application. The availability of the application is not directly impacted. Given feathersjs's role in building APIs and real-time apps, exploitation could lead to widespread unauthorized access, data breaches, and loss of user trust. Organizations relying on vulnerable versions risk significant reputational damage, regulatory penalties, and operational disruption. The attack requires user interaction but no authentication, increasing the attack surface especially in phishing or social engineering scenarios.

Mitigation Recommendations

1. Upgrade all instances of feathersjs to version 5.0.40 or later, where this vulnerability is fixed. 2. Review and sanitize all redirect parameters rigorously, ensuring they do not contain '@' characters or other URL authority injection vectors. 3. Configure the origins array properly, always including trailing slashes to prevent ambiguous URL parsing. 4. Implement strict allowlists for redirect URLs, permitting only trusted domains and paths. 5. Employ Content Security Policy (CSP) headers to restrict where scripts and resources can be loaded from, mitigating token theft via malicious redirects. 6. Educate users about phishing risks and suspicious URLs to reduce the likelihood of successful social engineering. 7. Monitor logs for unusual redirect patterns or access token exposures. 8. Consider implementing short-lived tokens and token revocation mechanisms to limit the window of exploitation if tokens are stolen.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-18T19:47:02.154Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69992e44be58cf853b3dcccb

Added to database: 2/21/2026, 4:02:12 AM

Last enriched: 2/21/2026, 4:16:41 AM

Last updated: 2/21/2026, 5:23:58 AM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats