VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@goauthentik/api: vulnerability history, versions and safety

@goauthentik/api is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Aug 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @goauthentik/api vulnerabilities

Vulert verdict on @goauthentik/api 2026.8.5 i

Updated on 23 Oct 2026

Good news: 2026.8.5, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 73/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

What to do: Stay on 2026.8.5 or newer. This can change: a vulnerability disclosed tomorrow can affect 2026.8.5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2026.8.5 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 29 Aug 2023 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Stars 2 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @goauthentik/api, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2026.8.5 21 Oct 2026 none MIT — Details →
2026.5.8 21 Oct 2026 none MIT — Details →
2026.8.4 14 Oct 2026 none MIT — Details →
2026.8.3 17 Sep 2026 none MIT — Details →
2026.8.2 09 Sep 2026 none MIT — Details →
2026.5.7 09 Sep 2026 none MIT — Details →
2026.2.7 09 Sep 2026 none MIT — Details →
2026.8.1 01 Sep 2026 none MIT — Details →
2026.8.0 18 Aug 2026 none MIT — Details →
2026.8.0-rc7 10 Aug 2026 none MIT — Details →
2026.8.0-rc6 03 Aug 2026 none MIT — Details →
2026.8.0-rc5 03 Aug 2026 none MIT — Details →
2026.8.0-rc4 03 Aug 2026 none MIT — Details →
2026.8.0-rc3 03 Aug 2026 none MIT — Details →
2026.8.0-rc2 03 Aug 2026 none MIT — Details →
2026.8.0-rc1 03 Aug 2026 none MIT — Details →
2026.5.6 22 Jul 2026 none MIT — Details →
2026.5.5 15 Jul 2026 none MIT — Details →
2026.2.6 15 Jul 2026 none MIT — Details →
2026.5.4 08 Jul 2026 none MIT — Details →
2026.2.5 07 Jul 2026 none — — Details →
2026.5.3 10 Jun 2026 none MIT — Details →
2026.5.2 28 May 2026 none MIT — Details →
2026.2.4 28 May 2026 none MIT — Details →
2025.12.6 28 May 2026 none MIT — Details →
2026.5.0 22 May 2026 none MIT — Details →
2026.5.0-rc2 13 May 2026 none MIT — Details →
2026.2.3 12 May 2026 none — — Details →
2025.12.5 12 May 2026 none — — Details →
2026.5.0-rc1 11 May 2026 none MIT — Details →
2026.2.3-rc1 10 Apr 2026 none — — Details →
2026.2.2 07 Apr 2026 none — — Details →
2026.2.2-rc3 07 Apr 2026 none — — Details →
2026.2.2-rc2 02 Apr 2026 none — — Details →
2026.2.2-rc1 01 Apr 2026 none — — Details →
2026.2.1 27 Mar 2026 none — — Details →
2026.2.1-rc1 27 Mar 2026 none — — Details →
2026.2.0 27 Mar 2026 none — — Details →
2026.2.0-rc5 27 Mar 2026 none — — Details →
2026.2.0-rc4 27 Mar 2026 none — — Details →
2026.2.0-rc3 27 Mar 2026 none — — Details →
2025.10.4 27 Mar 2026 none — — Details →
2026.2.0-rc2 27 Mar 2026 none — — Details →
2025.12.4 27 Mar 2026 none — — Details →
2025.8.6 27 Mar 2026 none — — Details →
2026.2.0-rc1 27 Mar 2026 none — — Details →
2025.12.3 27 Mar 2026 none — — Details →
2025.12.2 27 Mar 2026 none — — Details →
2025.12.1 27 Mar 2026 none — — Details →
2025.12.0 27 Mar 2026 none — — Details →
2025.12.0-rc3 27 Mar 2026 none — — Details →
2025.12.0-rc2 27 Mar 2026 none — — Details →
2025.10.3 27 Mar 2026 none — — Details →
2025.12.0-rc1 27 Mar 2026 none — — Details →
2025.10.2 27 Mar 2026 none — — Details →
2025.8.5 27 Mar 2026 none — — Details →
2025.10.1 27 Mar 2026 none — — Details →
2025.10.0 27 Mar 2026 none — — Details →
2025.10.0-rc3 27 Mar 2026 none — — Details →
2025.8.4 27 Mar 2026 none — — Details →
2025.8.3 27 Mar 2026 none — — Details →
2025.8.2 27 Mar 2026 none — — Details →
2025.8.1 27 Mar 2026 none — — Details →
2025.8.0 27 Mar 2026 none — — Details →
2025.8.0-rc7 27 Mar 2026 none — — Details →
2026.5.0-rc1-1774452234 25 Mar 2026 none — — Details →
2026.5.0-rc1-1774286058 23 Mar 2026 none — — Details →
2026.5.0-rc1-1773773770 17 Mar 2026 none — — Details →
2026.5.0-rc1-1773681572 16 Mar 2026 none — — Details →
2026.5.0-rc1-1773518480 14 Mar 2026 none — — Details →
2026.5.0-rc1-1773445002 13 Mar 2026 none — — Details →
2026.5.0-rc1-1773051490 09 Mar 2026 none — — Details →
2026.5.0-rc1-1772620687 04 Mar 2026 none — — Details →
2026.2.0-rc4-1771862880 23 Feb 2026 none — — Details →
2026.5.0-rc1-1771854957 23 Feb 2026 none — — Details →
2026.5.0-rc1-1771348436 17 Feb 2026 none — — Details →
2026.5.0-rc1-1770991247 13 Feb 2026 none — — Details →
2026.5.0-rc1-1770841133 11 Feb 2026 none — — Details →
2026.5.0-rc1-1770770609 11 Feb 2026 none — — Details →
2026.2.0-rc1-1770744803 10 Feb 2026 none — — Details →
2026.2.0-rc1-1770333267 05 Feb 2026 none — — Details →
2026.2.0-rc1-1770223158 04 Feb 2026 none — — Details →
2026.2.0-rc1-1770134072 03 Feb 2026 none — — Details →
2026.2.0-rc1-1770125387 03 Feb 2026 none — — Details →
2026.2.0-rc1-1769710374 29 Jan 2026 none — — Details →
2026.2.0-rc1-1769702893 29 Jan 2026 none — — Details →
2026.2.0-rc1-1769650973 29 Jan 2026 none — — Details →
2026.2.0-rc1-1769618615 28 Jan 2026 none — — Details →
2026.2.0-rc1-1769523342 27 Jan 2026 none — — Details →
2026.2.0-rc1-1769519393 27 Jan 2026 none — — Details →
2026.2.0-rc1-1769453512 26 Jan 2026 none — — Details →
2026.2.0-rc1-1769434248 26 Jan 2026 none — — Details →
2026.2.0-rc1-1769200848 23 Jan 2026 none — — Details →
2026.2.0-rc1-1769184916 23 Jan 2026 none — — Details →
2026.2.0-rc1-1769128766 23 Jan 2026 none — — Details →
2026.2.0-rc1-1769102238 22 Jan 2026 none — — Details →
2026.2.0-rc1-1768869959 20 Jan 2026 none — — Details →
2026.2.0-rc1-1767898882 08 Jan 2026 none — — Details →
2026.2.0-rc1-1767826226 07 Jan 2026 none — — Details →
2026.2.0-rc1-1767803006 07 Jan 2026 none — — Details →
2026.2.0-rc1-1767672135 06 Jan 2026 none — — Details →
2026.2.0-rc1-1767654897 05 Jan 2026 none — — Details →
2026.2.0-rc1-1766493698 23 Dec 2025 none — — Details →
2026.2.0-rc1-1766432129 22 Dec 2025 none — — Details →
2026.2.0-rc1-1766103708 19 Dec 2025 none — — Details →
2026.2.0-rc1-1765908665 16 Dec 2025 none — — Details →
2026.2.0-rc1-1765828227 15 Dec 2025 none — — Details →
2026.2.0-rc1-1765573201 12 Dec 2025 none — — Details →
2025.12.0-rc1-1765566302 12 Dec 2025 none — — Details →
2025.12.0-rc1-1765464563 11 Dec 2025 none — — Details →
2025.12.0-rc1-1765464370 11 Dec 2025 none — — Details →
2025.12.0-rc1-1765387260 10 Dec 2025 none — — Details →
2025.12.0-rc1-1765383563 10 Dec 2025 none — — Details →
2025.12.0-rc1-1765381247 10 Dec 2025 none — — Details →
2025.12.0-rc1-1765371513 10 Dec 2025 none — — Details →
2025.12.0-rc1-1765370909 10 Dec 2025 none — — Details →
2025.12.0-rc1-1765306026 09 Dec 2025 none — — Details →
2025.12.0-rc1-1765290953 09 Dec 2025 none — — Details →
2025.12.0-rc1-1765191857 08 Dec 2025 none — — Details →
2025.12.0-rc1-1765152822 08 Dec 2025 none — — Details →

The newest 120 of 709 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @goauthentik/api

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-39522: Username enumeration attack in goauthentik 5.3 medium 2023.6.2 29 Aug 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @goauthentik/api

Is @goauthentik/api safe to use?

Vulert records 1 vulnerabilities for @goauthentik/api in npm: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @goauthentik/api's Vulert package health score?

Vulert scores @goauthentik/api 73/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @goauthentik/api affected?

No. 2026.8.5, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does @goauthentik/api have?

1 vulnerability is recorded for @goauthentik/api in the npm ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @goauthentik/api vulnerabilities disclosed?

0 vulnerabilities were recorded for @goauthentik/api in the last 12 months, and the oldest entry in this database dates to 29 Aug 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @goauthentik/api are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @goauthentik/api for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @goauthentik/api version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.