How severe is CVE-2024-42490?

CVE-2024-42490 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-42490?

CVE-2024-42490 affects the following packages: goauthentik.io (Go), goauthentik.io (Go). Ecosystems affected: Go.

How do I fix CVE-2024-42490?

Update goauthentik.io to 2024.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-42490 is resolved across your whole dependency graph.

How do I detect CVE-2024-42490 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for goauthentik.io, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-42490 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2024-42490 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-42490 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-42490?

CVE-2024-42490 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-42490?

CVE-2024-42490 is classified as CWE-285 (CWE-285). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-42490 published, and has it been updated?

CVE-2024-42490 was published on August 22, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2024-42490 — goauthentik.io

HIGHFix: goauthentik/authentik@19318d4

CVE-2024-42490 is a high-severity (CVSS 7.5) CWE-285 vulnerability in goauthentik.io. A fix is available for goauthentik.io — see the affected versions and patch details below.

authentik has Insufficient Authorization for several API endpoints

Also known asBIT-authentik-2024-42490GHSA-qxqc-27pr-wgc8GO-2024-3085

Published

Aug 22, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-42490.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐹goauthentik.io🐹goauthentik.io

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Several API endpoints can be accessed by users without correct authentication/authorization.

The main API endpoints affected by this:

/api/v3/crypto/certificatekeypairs/<uuid>/view_certificate/
/api/v3/crypto/certificatekeypairs/<uuid>/view_private_key/
/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.

Patches

authentik 2024.4.4, 2024.6.4 and 2024.8.0 fix this issue.

Workarounds

Access to the API endpoints can be blocked at a Reverse-proxy/Load balancer level to prevent this issue from being exploited.

For more information

If you have any questions or comments about this advisory:

Email us at [email protected]

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`goauthentik.io`	≥ 2024.6.0-rc1&&< 2024.6.4	2024.6.4`go get goauthentik.io@v2024.6.4`
🐹Go	`goauthentik.io`	all versions	2024.4.4`go get goauthentik.io@v2024.4.4`

Affected Products

1 product · 2 configurations

Application

authentikgoauthentik

≥ 2024.6.0 && < 2024.6.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for goauthentik.io, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update goauthentik.io to 2024.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-42490 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Summary Several API endpoints can be accessed by users without correct authentication/authorization. The main API endpoints affected by this: - `/api/v3/crypto/certificatekeypairs/<uuid>/view_certificate/` - `/api/v3/crypto/certificatekeypairs/<uuid>/view_private_key/` - `/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. ### Patches authentik