CVE-2025-63700 Clerk-js vulnerable to bypass of OAuth authentication flow by manipulating request at OTP verification stage
Not scored
Published
Updated
Check this codebase for CVE-2025-63700 and fix it if it is affected.
What it is: CVE-2025-63700 is a vulnerability in @clerk/clerk-js, published on 20 Nov 2025.
Exploitation: There is no known exploitation of CVE-2025-63700 in the wild and no public exploit code.
Affected packages and fixed versions:
- @clerk/clerk-js (npm): affected all versions up to 5.88.0; no fix listed
- @clerk/clerk-js (npm): affected all versions up to 5.88.0; no fix listed
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2025-63700/ (Markdown: https://insights.sbomify.com/CVE-2025-63700/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2025-63700?
CVE-2025-63700 is a vulnerability in @clerk/clerk-js, published on 20 Nov 2025.
Official description
DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
Which versions are affected by CVE-2025-63700?
2 open source packages ship an affected version, including @clerk/clerk-js.
| Package | Affected | Fixed in |
|---|---|---|
@clerk/clerk-js npm | All versions to 5.88.0 | None |
@clerk/clerk-js npm | All versions to 5.88.0 | None |
How do I fix CVE-2025-63700?
No fix has been published for CVE-2025-63700 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-63700 being exploited?
There is no known exploitation of CVE-2025-63700 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-3mm3-wfpv-q85g.