CVE-2025-53548GHSA-9MP4-77WG-RWX9
@clerk/backend Performs Insufficient Verification of Data Authenticity
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.4.0, 2.10.2, 1.7.4, 2.4.4, 6.23.3, and 4 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
Clerk helps developers build user management. Applications that use the verifyWebhook() helper to verify incoming Clerk webhooks are susceptible to accepting improperly signed webhook events. The issue was resolved in @clerk/backend 2.4.0.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- clerk javascript
fixed in 2.4.0
- @clerk/backendnpm
From 2.0.0 · fixed in 2.4.0
- @clerk/astronpm
From 2.9.0 · fixed in 2.10.2
- @clerk/expressnpm
From 1.6.0 · fixed in 1.7.4
- @clerk/fastifynpm
From 2.3.0 · fixed in 2.4.4
- @clerk/nextjsnpm
From 6.2.10 · fixed in 6.23.3
- @clerk/nuxtnpm
From 1.7.0 · fixed in 1.7.5
- @clerk/react-routernpm
From 1.5.0 · fixed in 1.6.4
- @clerk/remixnpm
From 4.8.0 · fixed in 4.8.5
- @clerk/tanstack-react-startnpm
From 0.16.0 · fixed in 0.18.3