# CVE-2024-22206: Clerk nextjs auth() and getAuth() IDOR vulnerability

Source: https://junglewise.ai/threats/cve-2024-22206-clerk-nextjs-auth-and-getauth-idor-vulnerability  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-01-12. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2024-22206 · Severity: low · CVSS 3.1 · Published 2024-01-12

Clerk's @clerk/nextjs authentication library contains a logic flaw in its auth() and getAuth() methods that allows attackers to bypass access controls and gain unauthorized access to other users' data. Applications using affected versions (4.7.0–4.29.2) for Next.js backend authentication are vulnerable to privilege escalation and account takeover if attackers can manipulate authentication tokens or user identifiers.

Technologies: [@clerk/nextjs (npm)](https://junglewise.ai/threats/technologies/clerk-nextjs). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2024-22206 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-22206 being exploited in the wild.

**How severe is CVE-2024-22206?** Low severity, with a CVSS score of 3.1, published 12 January 2024.

**Which products and versions are affected?** @clerk/nextjs (npm) SEMVER:introduced=4.7.0,fixed=4.29.3.

**Is there a fix for CVE-2024-22206?** Yes. @clerk/nextjs (npm): upgrade to 4.29.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2024-22206 attacked?** It is attacked over the network.

**Am I affected by CVE-2024-22206?** Check whether you run @clerk/nextjs (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- @clerk/nextjs (npm): upgrade to 4.29.3 or later

  ```sh
  npm install @clerk/nextjs@4.29.3
  ```


## Technical details

The vulnerability is an insecure direct object reference (IDOR) flaw in the @clerk/nextjs SDK versions 4.7.0 through 4.29.2, affecting the auth() method in the Next.js App Router and getAuth() in the Pages Router. The root cause is a logic flaw in the authentication and authorization validation that fails to properly verify user identity when processing API requests, allowing attackers to access resources belonging to other users by manipulating request parameters. The attack requires network access to affected API endpoints but does not require user interaction or prior authentication. An attacker can gain unauthorized access to sensitive data, perform actions on behalf of other users, or escalate privileges. The fix is available in @clerk/nextjs version 4.29.3 and later; applications must upgrade immediately.

## Affected products

- Clerk @clerk/nextjs >=4.7.0, <4.29.3

## Identifiers

- CVE-2024-22206
- GHSA-q6w5-jg5q-47vg

## Timeline

- 2024-01-12: disclosed

## References

- [https://github.com/clerk/javascript/security/advisories/GHSA-q6w5-jg5q-47vg](https://github.com/clerk/javascript/security/advisories/GHSA-q6w5-jg5q-47vg)

## Related threats

- [Clerk JavaScript SDKs authorization bypass in combined predicates](https://junglewise.ai/threats/cve-2026-42349-clerk-javascript-sdks-authorization-bypass-in-combined-predicates)
- [Official Clerk JavaScript SDKs: Middleware-based route protection bypass](https://junglewise.ai/threats/cve-2026-41248-official-clerk-javascript-sdks-middleware-based-route-protection)
- [Clerk webhook verifyWebhook insufficient signature verification](https://junglewise.ai/threats/cve-2025-53548-clerk-webhook-verifywebhook-insufficient-signature-verification)