Skip to main content

CVE-2025-55008: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in workos authkit-react-router

High
VulnerabilityCVE-2025-55008cvecve-2025-55008cwe-200
Published: Sat Aug 09 2025 (08/09/2025, 02:02:14 UTC)
Source: CVE Database V5
Vendor/Project: workos
Product: authkit-react-router

Description

The AuthKit library for React Router 7+ provides helpers for authentication and session management using WorkOS & AuthKit with React Router. In versions 0.6.1 and below, @workos-inc/authkit-react-router exposed sensitive authentication artifacts — specifically sealedSession and accessToken by returning them from the authkitLoader. This caused them to be rendered into the browser HTML. This issue is fixed in version 0.7.0.

AI-Powered Analysis

AILast updated: 08/17/2025, 01:07:54 UTC

Technical Analysis

CVE-2025-55008 is a high-severity vulnerability affecting the AuthKit library for React Router versions 0.6.1 and below. AuthKit is a helper library designed to facilitate authentication and session management when integrating WorkOS with React Router 7 and above. The vulnerability arises because the library's authkitLoader function inadvertently exposes sensitive authentication artifacts, specifically the sealedSession and accessToken, by returning them in a manner that causes these tokens to be rendered directly into the browser's HTML. This exposure constitutes a CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) vulnerability. The accessToken and sealedSession are critical for maintaining authenticated sessions and authorizing user actions. If these tokens are exposed in the client-side HTML, they can be accessed by malicious actors through various means such as cross-site scripting (XSS) attacks, browser history inspection, or network interception if HTTPS is not enforced. The vulnerability requires no user interaction (UI:N) but does require low privileges (PR:L) to exploit, and the attack vector is network-based (AV:N), meaning an attacker can exploit it remotely. The CVSS v3.1 score of 7.1 reflects the high impact on confidentiality and integrity, with a limited impact on availability. The issue has been resolved in version 0.7.0 of the library, where the sensitive tokens are no longer exposed in the HTML. No known exploits are currently reported in the wild, but the nature of the vulnerability makes it a significant risk for applications using affected versions of authkit-react-router. Organizations using this library in their web applications should prioritize upgrading to version 0.7.0 or later to mitigate this exposure.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of user authentication sessions. Exposure of access tokens and session data can lead to unauthorized access to user accounts, data breaches, and potential lateral movement within enterprise environments. Given the widespread adoption of React Router and the increasing use of WorkOS for identity management in SaaS and enterprise applications, many European companies integrating these technologies could be affected. The exposure of sensitive tokens in the browser HTML increases the attack surface for client-side attacks, which can be particularly damaging in regulated sectors such as finance, healthcare, and government where personal data protection is critical under GDPR. A successful exploitation could result in unauthorized data access, compliance violations, reputational damage, and financial penalties. Additionally, since the vulnerability can be exploited remotely without user interaction, it increases the likelihood of automated attacks targeting vulnerable applications.

Mitigation Recommendations

European organizations should immediately audit their use of the authkit-react-router library to identify any instances of versions below 0.7.0. The primary mitigation is to upgrade to version 0.7.0 or later, where the vulnerability is fixed. Beyond upgrading, developers should review their authentication flows to ensure that sensitive tokens are never exposed in client-rendered HTML or accessible via JavaScript in an unsafe manner. Implementing Content Security Policy (CSP) headers can help mitigate the risk of token theft via XSS attacks. Additionally, organizations should enforce HTTPS to protect tokens in transit and consider implementing short-lived tokens with refresh mechanisms to limit the window of exposure. Regular security code reviews and dependency scanning should be integrated into the development lifecycle to detect vulnerable versions promptly. Monitoring for unusual authentication activity can help detect exploitation attempts early. Finally, educating developers about secure token handling and client-server data separation is crucial to prevent similar issues.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-08-04T17:34:24.422Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6896b351ad5a09ad00087c23

Added to database: 8/9/2025, 2:32:49 AM

Last enriched: 8/17/2025, 1:07:54 AM

Last updated: 9/20/2025, 7:22:06 PM

Views: 64

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

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

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats