Is CVE-2025-55009 exploited in the wild?

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

How severe is CVE-2025-55009?

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

Which products and versions are affected?

@workos-inc/authkit-remix (npm) SEMVER:introduced=0,fixed=0.15.0; WorkOS Authkit-Remix before 0.15.0.

Is there a fix for CVE-2025-55009?

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

How is CVE-2025-55009 attacked?

It is attacked over the network.

Am I affected by CVE-2025-55009?

Check whether you run @workos-inc/authkit-remix (npm) or WorkOS Authkit-Remix 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-55009: WorkOS AuthKit Remix sensitive data exposure in HTML

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

AuthKit Remix is a library used to integrate authentication and user management into Remix web applications. Versions before 0.15.0 exposed sensitive authentication tokens (session data and API access tokens) by embedding them directly in the HTML pages served to browsers, making them readable to malicious scripts or browser extensions. This could allow attackers to hijack user sessions or make unauthorized API calls on behalf of users.

Vendors: npm, WorkOS.

Quick answers

Is CVE-2025-55009 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-55009 being exploited in the wild.
How severe is CVE-2025-55009?: Low severity, with a CVSS score of 3.1, published 8 August 2025.
Which products and versions are affected?: @workos-inc/authkit-remix (npm) SEMVER:introduced=0,fixed=0.15.0; WorkOS Authkit-Remix before 0.15.0.
Is there a fix for CVE-2025-55009?: Yes. @workos-inc/authkit-remix (npm): upgrade to 0.15.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-55009 attacked?: It is attacked over the network.
Am I affected by CVE-2025-55009?: Check whether you run @workos-inc/authkit-remix (npm) or WorkOS Authkit-Remix 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-remix (npm): upgrade to 0.15.0 or later
```
npm install @workos-inc/authkit-remix@0.15.0
```

Technical details

The vulnerability is a sensitive data exposure issue (CWE-200) in the @workos-inc/authkit-remix library. The authkitLoader function returned sensitive authentication artifacts—sealedSession and accessToken—which were then embedded into server-rendered HTML and accessible to any script with DOM access. An attacker with an XSS vulnerability, malicious browser extension, or local access could read these tokens from the page. The vulnerability requires low privileges (an authenticated user) and high attack complexity. Versions 0.15.0 and later fix this by removing these values from the default loader return and providing a secure server-side mechanism for token retrieval.

Affected products

WorkOS AuthKit Remix before 0.15.0

Identifiers

CVE-2025-55009
GHSA-v3gr-w9gf-23cx

Timeline

2025-08-08: disclosed
2025-08-08: patched: Fixed in v0.15.0

References

https://github.com/workos/authkit-remix/security/advisories/GHSA-v3gr-w9gf-23cx

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