Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-qxqc-27pr-wgc8

HIGH

GHSA-qxqc-27pr-wgc8 is a high-severity (CVSS 8.7) CWE-285 vulnerability in goauthentik.io. O3 Security confirms whether GHSA-qxqc-27pr-wgc8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

GoAuthentik vulnerable to Insufficient Authorization for several API endpoints

Also known asBIT-authentik-2024-42490CVE-2024-42490GO-2024-3085
Published
Aug 22, 2024
Updated
Apr 17, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

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:

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogoauthentik.io2024.6.0-rc1&&< 2024.6.42024.6.4
🐹Gogoauthentik.ioall versions2024.4.4

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for goauthentik.io. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

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

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-qxqc-27pr-wgc8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qxqc-27pr-wgc8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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
O3 Security · Impact-Aware SCA

Is GHSA-qxqc-27pr-wgc8 in your dependencies?

O3 detects GHSA-qxqc-27pr-wgc8 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.