# CVE-2024-42490: authentik has Insufficient Authorization for several API endpoints

> Unauthenticated users can access sensitive certificate and object data via API endpoints if they possess the specific UUID.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2024
- **Updated:** 22 Aug 2024
- **Also known as:** BIT-authentik-2024-42490, GHSA-qxqc-27pr-wgc8, GO-2024-3085

## What is CVE-2024-42490?

CVE-2024-42490 is a high-severity missing authorization vulnerability in goauthentik authentik, published on 22 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

authentik is an open-source Identity Provider. Several API endpoints can be accessed by users without correct authentication/authorization. The main API endpoints affected by this are /api/v3/crypto/certificatekeypairs/<uuid>/view_certificate/, /api/v3/crypto/certificatekeypairs/<uuid>/view_private_key/, and /api/v3/.../used_by/. Note that all of the affected API endpoints require the knowledge of the ID of an object, which especially for certificates is not accessible to an unprivileged user. Additionally the IDs for most objects are UUIDv4, meaning they are not easily guessable/enumerable. authentik 2024.4.4, 2024.6.4 and 2024.8.0 fix this issue.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2024-42490?

6 open source packages ship an affected version, including goauthentik.io and authentik. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `goauthentik.io` | Go | All versions | None |
| `goauthentik.io` | Go | All versions | 2024.4.4 |
| `goauthentik.io` | Go | All versions | 2024.4.4 |
| `goauthentik.io` | Go | From 2024.6.0-rc1 | 2024.6.4 |
| `goauthentik.io` | Go | From 2024.6.0-rc1 | 2024.6.4 |
| `authentik` | Bitnami | All versions | 2024.4.4, 2024.6.4 |

Products: Goauthentik Authentik.

## How do I fix CVE-2024-42490?

Upgrade goauthentik.io to a fixed version for your release line: 2024.4.4 or 2024.6.4.

## Is CVE-2024-42490 being exploited?

There is no known exploitation of CVE-2024-42490 in the wild and no public exploit code.

## Other vulnerabilities in goauthentik authentik

- [CVE-2026-49448](https://insights.sbomify.com/CVE-2026-49448/): authentik: SourceStage bypass via empty POST (critical 9.8)
- [CVE-2023-46249](https://insights.sbomify.com/CVE-2023-46249/): authentik potential installation takeover when default admin user is deleted (critical 9.7)
- [CVE-2022-23555](https://insights.sbomify.com/CVE-2022-23555/): authentik vulnerable to Improper Authentication via invitation URL token reuse (critical 9.4)
- [CVE-2026-42849](https://insights.sbomify.com/CVE-2026-42849/): authentik: Reflected XSS in SFE AutosubmitStage allows IDP account takeover (critical 9.3)
- [CVE-2026-25227](https://insights.sbomify.com/CVE-2026-25227/): authentik affected by Remote Code Execution via Context Key Injection in PropertyMapping Test Endpoint (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42490 and fix it if it is affected.

What it is: CVE-2024-42490 is a high-severity missing authorization vulnerability in goauthentik authentik, published on 22 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-42490 in the wild and no public exploit code.

Affected packages and fixed versions:
- goauthentik.io (Go): affected all versions; no fix listed
- goauthentik.io (Go): affected all versions; fixed in 2024.4.4
- goauthentik.io (Go): affected all versions; fixed in 2024.4.4
- goauthentik.io (Go): affected from 2024.6.0-rc1; fixed in 2024.6.4
- goauthentik.io (Go): affected from 2024.6.0-rc1; fixed in 2024.6.4
- authentik (Bitnami): affected all versions; fixed in 2024.4.4, 2024.6.4

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-2024-42490/ (Markdown: https://insights.sbomify.com/CVE-2024-42490/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-42490
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-42490
- OSV: https://osv.dev/vulnerability/CVE-2024-42490

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-42490/
Summaries are generated and may contain mistakes; the official description above is the record.