Is CVE-2025-55008 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-55008 being exploited in the wild.

How severe is CVE-2025-55008?

Low severity, with a CVSS score of 3.1, published 8 August 2025.

Which products and versions are affected?

@workos-inc/authkit-react-router (npm) SEMVER:introduced=0,fixed=0.7.0; WorkOS AuthKit React Router before 0.7.0.

Is there a fix for CVE-2025-55008?

Yes. @workos-inc/authkit-react-router (npm): upgrade to 0.7.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-55008 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-55008?

Check whether you run @workos-inc/authkit-react-router (npm) or WorkOS AuthKit React Router at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-55008: WorkOS AuthKit React Router information disclosure in authkitLoader

CVE-2025-55008 · Severity: low · CVSS 3.1 · Published 2025-08-08

The AuthKit React Router library is used to manage authentication in React applications. Before version 0.7.0, the library exposed sensitive authentication credentials (session tokens and access tokens) directly in the HTML sent to browsers, making them visible to attackers exploiting XSS vulnerabilities, installing malicious browser extensions, or with local machine access. This could allow attackers to hijack user sessions.

Vendors: npm, WorkOS.

Quick answers

Is CVE-2025-55008 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-55008 being exploited in the wild.
How severe is CVE-2025-55008?: Low severity, with a CVSS score of 3.1, published 8 August 2025.
Which products and versions are affected?: @workos-inc/authkit-react-router (npm) SEMVER:introduced=0,fixed=0.7.0; WorkOS AuthKit React Router before 0.7.0.
Is there a fix for CVE-2025-55008?: Yes. @workos-inc/authkit-react-router (npm): upgrade to 0.7.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-55008 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-55008?: Check whether you run @workos-inc/authkit-react-router (npm) or WorkOS AuthKit React Router at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@workos-inc/authkit-react-router (npm): upgrade to 0.7.0 or later
```
npm install @workos-inc/authkit-react-router@0.7.0
```

Technical details

The vulnerability is an information disclosure (CWE-200) in the authkitLoader function, which returned sensitive authentication artifacts (sealedSession and accessToken) that were subsequently rendered into the browser's HTML. The vulnerability requires network access plus low-level privileges and high attack complexity (XSS exploitation, malicious extensions, or local access). An attacker exploiting this can obtain authentication tokens to hijack sessions and potentially modify user data. The vulnerability was patched in version 0.7.0, which removed these secrets from the default authkitLoader return and provides a secure server-side token fetching mechanism instead.

Affected products

WorkOS AuthKit React Router before 0.7.0

Identifiers

CVE-2025-55008
GHSA-vqvc-9q8x-vmq6

Timeline

2025-08-08: disclosed
2025-08-08: patched: Version 0.7.0 released

References

https://github.com/workos/authkit-react-router/security/advisories/GHSA-vqvc-9q8x-vmq6

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.