How severe is GHSA-v2qh-f584-6hj8?

No CVSS score has been assigned to GHSA-v2qh-f584-6hj8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v2qh-f584-6hj8?

GHSA-v2qh-f584-6hj8 affects the following packages: @workos-inc/authkit-remix (npm). Ecosystems affected: npm.

How do I fix GHSA-v2qh-f584-6hj8?

Update @workos-inc/authkit-remix to 0.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v2qh-f584-6hj8 is resolved across your whole dependency graph.

How do I detect GHSA-v2qh-f584-6hj8 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @workos-inc/authkit-remix, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-v2qh-f584-6hj8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-v2qh-f584-6hj8?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-v2qh-f584-6hj8 can be triaged on real exposure rather than presence alone.

Is GHSA-v2qh-f584-6hj8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-v2qh-f584-6hj8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-v2qh-f584-6hj8?

GHSA-v2qh-f584-6hj8 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 12th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-v2qh-f584-6hj8?

GHSA-v2qh-f584-6hj8 is classified as CWE-532 (CWE-532). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-v2qh-f584-6hj8 published, and has it been updated?

GHSA-v2qh-f584-6hj8 was published on November 5, 2024 and was last updated on November 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-v2qh-f584-6hj8 — @workos-inc/authkit-remix

Fix: workos/authkit-remix@32d5bcd

GHSA-v2qh-f584-6hj8 is a CWE-532 vulnerability in @workos-inc/authkit-remix. A fix is available for @workos-inc/authkit-remix — see the affected versions and patch details below.

@workos-inc/authkit-remix refresh tokens are logged when the debug flag is enabled

Also known asCVE-2024-51753

Published

Nov 5, 2024

Updated

Nov 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-v2qh-f584-6hj8.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@workos-inc/authkit-remixnpm

88downloads / week

Description

The AuthKit library for Remix provides convenient helpers for authentication and session management using WorkOS & AuthKit with Remix. In affected versions refresh tokens are logged to the console when the disabled by default debug flag, is enabled. This issue has been patched in version 0.4.1. All users are advised to upgrade. There are no known workarounds for this vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@workos-inc/authkit-remix`	all versions	0.4.1`npm install @workos-inc/authkit-remix@0.4.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @workos-inc/authkit-remix, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @workos-inc/authkit-remix to 0.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v2qh-f584-6hj8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-v2qh-f584-6hj8 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-v2qh-f584-6hj8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Refresh tokens are logged to the console when the disabled by default `debug` flag, is enabled. ### Patches Patched in [https://github.com/workos/authkit-remix/releases/tag/v0.4.1](https://github.com/workos/authkit-remix/releases/tag/v0.4.1)

O3 Security · Impact-Aware SCA

Is GHSA-v2qh-f584-6hj8 in your dependencies?

O3 Security finds GHSA-v2qh-f584-6hj8 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works