GHSA-v3gr-w9gf-23cx is a high-severity (CVSS 7.1) Information Exposure vulnerability in @workos-inc/authkit-remix. A fix is available for @workos-inc/authkit-remix — see the affected versions and patch details below.
The AuthKit Remix Library renders sensitive auth data in HTML
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-v3gr-w9gf-23cx.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-v3gr-w9gf-23cx plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.
@workos-inc/authkit-remixnpmDescription
Summary
Before 0.15.0, @workos-inc/authkit-remix returned sensitive authentication artifacts from the authkitLoader, specifically sealedSession and accessToken. Because these values were returned from the loader, they were embedded into the server-rendered HTML and became readable by any script with access to the page’s DOM (e.g., in the presence of XSS or a malicious browser extension).
- Impact: Exposure of these secrets can lead to session hijacking and unauthorized API access.
- Fix: Version
0.15.0changes the default behavior so the loader no longer returnssealedSession/accessToken. A secure server-side mechanism is provided to fetch an access token when needed.
Patches
Patched in v0.15.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @workos-inc/authkit-remix | all versions | 0.15.0npm install @workos-inc/authkit-remix@0.15.0 |
Detection & mitigation playbook
Open-source dependencyDetect
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.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v3gr-w9gf-23cx 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-v3gr-w9gf-23cx can be triaged on real exposure rather than presence alone.
Tailored to GHSA-v3gr-w9gf-23cx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-v3gr-w9gf-23cx in your dependencies?
O3 Security finds GHSA-v3gr-w9gf-23cx across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.