Server-side Request Forgery (SSRF) Affecting @clerk/backend package, versions >=3.0.0 <3.2.3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-CLERKBACKEND-15810802
- published29 Mar 2026
- disclosed27 Mar 2026
- creditUnknown
Introduced: 27 Mar 2026
CVE-2026-34076 (opens in a new tab)How to fix?
Upgrade @clerk/backend to version 3.2.3 or higher.
Overview
@clerk/backend is a Clerk Backend SDK - REST Client for Backend API & JWT verification utilities
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the clerkFrontendApiProxy function. An attacker can obtain secret keys by crafting a request path that causes the proxy to forward sensitive information to an attacker-controlled server.
Note: This is only exploitable if the frontendApiProxy feature is enabled in the application's configuration.
Workaround
This vulnerability can be mitigated by disabling the frontendApiProxy feature in the application's configuration.