Skip to main content
CVE-2025-55008VulnerabilityPublished Updated

CVE-2025-55008: workos authkit-react-router · Information Exposure

Affects workos authkit-react-routerSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High : upgrade to 0.7.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.7.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade workos authkit-react-router to 0.7.0.

Affected software

ProductAffectedFixed in
workos authkit-react-routerAffected
  • <0.7.0
Fixed in
  • 0.7.0

AI-suggested

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.

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.

References

Community reviews

Loading reviews…