dbcve.org
AuthentikApplication · Goauthentik

CVE-2024-37905

HIGH · 8.8 CVSS v3.1 Published 2024-06-28
Fix available
A fix is available. Upgrade to 2024.2.4 / 2024.4.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
authentik is an open-source Identity Provider that emphasizes flexibility and versatility. Authentik API-Access-Token mechanism can be exploited to gain admin user privileges. A successful exploit of the issue will result in a user gaining full admin access to the Authentik application, including resetting user passwords and more. This issue has been patched in version(s) 2024.2.4, 2024.4.2 and 2024.6.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The authentik identity provider contains a privilege escalation vulnerability in its API-Access-Token mechanism. Attackers can exploit this to gain full administrative access to the application, enabling password resets and full control over the identity platform.

MitigationUpgrade authentik to version 2024.2.4, 2024.4.2, or 2024.6.0 or later to patch the vulnerability. Prior to upgrade, review API token configurations and audit existing admin accounts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AuthentikApplication
Affected:< 2024.2.4>= 2024.4.0, < 2024.4.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed authentik version
    Check the version via the admin UI footer, or run 'authentik version' from the command line, or inspect the running container/image tag if deployed via Docker
    Affected if The version is below 2024.2.4, or is between 2024.4.0 and 2024.4.3 inclusive
  2. Verify API-Access-Token feature is in use
    Navigate to the authentik admin interface and check under 'Tokens' or 'API Tokens' section to see if any API access tokens have been created
    Affected if API access tokens exist in the environment, particularly tokens with elevated or administrative scopes
  3. Review token permissions and scope
    Examine each API token's assigned permissions in the admin panel under the token details. Look for tokens granted 'admin' scope or superuser status
    Affected if Any API access token has superuser privileges or administrative-level permissions granted
  4. Audit admin accounts for unauthorized changes
    Review the 'Users' or 'Administrators' section in the admin UI to list all accounts with admin rights. Check for any unexpected or recently created admin accounts
    Affected if There are admin accounts that were not created by your organization or show recent suspicious activity
  5. Check token creation logs
    Examine authentik's event log or audit log for entries related to API token creation, especially those with admin scope, looking for creation times or sources that align with the vulnerability window
    Affected if Logs show API tokens with admin scope created during the period when the vulnerable versions were in use

You are affected if your authentik installation is version 2024.2.4 or earlier, or falls between 2024.4.0 and 2024.4.3, AND you have API access tokens configured with administrative permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2024.2.4 / 2024.4.3 or later
Fixed in 2024.2.42024.4.3
Interim mitigation

Upgrade authentik to version 2024.2.4, 2024.4.2, or 2024.6.0 or later to patch the vulnerability. Prior to upgrade, review API token configurations and audit existing admin accounts.

Recommended fix High confidence

2024.6.0 (recommended) or 2024.4.3 for 2024.4.x users or 2024.2.4 for 2024.2.x users

  1. 1. Identify current Authentik version by checking the authentik version endpoint or container image tag
  2. 2. Determine appropriate upgrade path based on current version (if < 2024.2.4, upgrade to 2024.2.4 or later; if >= 2024.4.0 and < 2024.4.3, upgrade to 2024.4.3 or later)
  3. 3. Back up Authentik database and configuration files before upgrading
  4. 4. For Docker deployments: Update the image tag to the desired fixed version (e.g., latest, 2024.6.0, or 2024.4.3) and recreate containers
  5. 5. For non-Docker deployments: Follow official upgrade documentation using pip or system package manager
  6. 6. Verify upgrade completed successfully by checking the authentik admin interface and version information
  7. 7. Test that API tokens and admin privileges are working as expected post-upgrade
Caveat No breaking changes mentioned in the advisory; standard upgrade procedure applies

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Authentik Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,220
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,552.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37905 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-37905 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data