Skip to main content
VulnerabilityPublished Updated

CVE-2025-55009: workos authkit-remix · Information Exposure

Affects workos authkit-remixSource CVE Database V5

0

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

Data as of 26 Oct 2026, 12:55 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.15.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 26 Oct 2026.

What to do

Upgrade workos authkit-remix to 0.15.0.

Affected software

ProductAffectedFixed in
workos authkit-remixAffected
  • <0.15.0
Fixed in
  • 0.15.0

AI-suggested

European organizations should immediately audit their use of the @workos-inc/authkit-remix package and identify any versions below 0.15.0 in their codebases. The primary mitigation is to upgrade to version 0.15.0 or later, where the exposure of sensitive tokens in the browser HTML is corrected. Until upgrading is possible, organizations should implement strict Content Security Policies (CSP) to mitigate token theft via XSS attacks and ensure all communications use TLS to prevent interception. Additionally, review and minimize token scope and lifetime to reduce risk if tokens are compromised. Implement monitoring and alerting for unusual authentication activity that may indicate token misuse. Developers should avoid returning sensitive tokens in client-rendered HTML and instead handle them securely on the server side or via secure HTTP-only cookies. Conduct thorough security testing, including code reviews and penetration testing focused on authentication flows. Finally, educate development teams about secure token handling best practices to prevent recurrence.

Description

The AuthKit library for Remix provides convenient helpers for authentication and session management using WorkOS & AuthKit with Remix. In versions 0.14.1 and below, @workos-inc/authkit-remix exposed sensitive authentication artifacts — specifically sealedSession and accessToken — by returning them from the authkitLoader. This caused them to be rendered into the browser HTML.

References

Community reviews

Loading reviews…