# CVE-2025-63700: @clerk/clerk-js (High 7.5)

📦

📦 npm

Not in CISA KEV

HIGH severity

# CVE-2025-63700 — @clerk/clerk-js

HIGH 

CVE-2025-63700 is a high-severity (CVSS 7.5) vulnerability in @clerk/clerk-js. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Clerk-js vulnerable to bypass of OAuth authentication flow by manipulating request at OTP verification stage

Published

Nov 20, 2025

Updated

Nov 21, 2025

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Nov 21, 2025 · OSV.dev, FIRST.org (EPSS)

## 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.

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

`@clerk/clerk-js`npm

1.3Mdownloads / week

## Description

An issue was discovered in Clerk-js 5.88.0 allowing attackers to bypass the OAuth authentication flow by manipulating the request at the OTP verification stage.

## Affected Packages

1 total

Ecosystem

Package

Vulnerable range

Fix

📦npm

`@clerk/clerk-js` 

all versions

No fix

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @clerk/clerk-js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Remediation status
    
    The records we use list no patched version of @clerk/clerk-js for CVE-2025-63700. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
    
3.  ### Mitigate without a patch
    
    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.
    

## Frequently Asked Questions

An issue was discovered in Clerk-js 5.88.0 allowing attackers to bypass the OAuth authentication flow by manipulating the request at the OTP verification stage.

O3 Security · Impact-Aware SCA

### Is CVE-2025-63700 in your dependencies?

Find it across npm, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)