VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

Tgstation.Server.Api: vulnerability history, versions and safety

Tgstation.Server.Api is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 22 releases, first recorded in Jul 2024. 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 H1
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 Tgstation.Server.Api vulnerabilities

Vulert verdict on Tgstation.Server.Api 18.2.1 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 18.2.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 29 Jul 2024 i
  • Highest CVSS 8.4 i
  • With no published fix 0 i
  • Stars 86 i
  • Last release 8 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by NuGet, 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 Tgstation.Server.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
18.2.1 05 Feb 2026 none non-standard — Details →
16.3.0 03 Nov 2024 none non-standard — Details →
16.2.0 02 Nov 2024 none non-standard — Details →
16.1.0 07 Oct 2024 none non-standard — Details →
15.0.0 10 Sep 2024 none non-standard — Details →
14.1.0 08 Sep 2024 none non-standard — Details →
14.0.0 04 Sep 2024 none non-standard — Details →
13.7.0 12 Aug 2024 none non-standard — Details →
13.6.0 27 Jul 2024 none non-standard — Details →
13.5.0 21 Jul 2024 none non-standard — Details →
13.4.0 06 Jul 2024 none non-standard — Details →
13.3.0 21 Apr 2024 none non-standard — Details →
13.2.0 23 Feb 2024 none non-standard — Details →
13.1.0 03 Feb 2024 none non-standard — Details →
13.0.1 26 Dec 2023 none non-standard — Details →
13.0.0 24 Dec 2023 none non-standard — Details →
12.2.0 17 Nov 2023 none non-standard — Details →
12.0.1 07 Nov 2023 none non-standard — Details →
12.0.0 05 Nov 2023 none non-standard — Details →
11.1.2 24 Aug 2023 none non-standard — Details →
11.1.1 23 Aug 2023 none non-standard — Details →
11.1.0 22 Aug 2023 none non-standard — Details →
11.0.0 14 Jul 2023 none non-standard — Details →
10.4.1 26 Apr 2023 none non-standard — Details →
10.4.0 25 Apr 2023 none non-standard — Details →
10.3.0 03 Apr 2023 none non-standard — Details →
10.2.0 22 Jan 2023 none non-standard — Details →
10.0.0 03 Oct 2022 none non-standard — Details →
9.6.1 20 Sep 2022 none non-standard — Details →
9.6.0 24 Aug 2022 none non-standard — Details →
9.5.0 12 Aug 2022 none non-standard — Details →
9.4.0 18 Jul 2022 none non-standard — Details →
9.3.1 12 Oct 2021 none non-standard — Details →
9.3.0 27 Sep 2021 none non-standard — Details →
9.2.0 29 Aug 2021 none non-standard — Details →
9.1.0 12 Aug 2021 none non-standard — Details →
9.0.0 21 Feb 2021 none non-standard — Details →
8.3.0 22 Jan 2021 none non-standard — Details →
8.2.0 12 Jan 2021 none non-standard — Details →
8.1.1 01 Jan 2021 none non-standard — Details →
8.1.0 30 Dec 2020 none non-standard — Details →
8.0.0 29 Dec 2020 none non-standard — Details →
7.4.0 07 Nov 2020 none non-standard — Details →
7.3.2 07 Sep 2020 none non-standard — Details →
7.3.1 29 Aug 2020 none non-standard — Details →
7.3.0 25 Aug 2020 none non-standard — Details →
7.2.0 10 Aug 2020 none non-standard — Details →
7.1.0 30 Jul 2020 none non-standard — Details →
7.0.1 10 Jul 2020 none non-standard — Details →
7.0.0 09 Jul 2020 none non-standard — Details →
6.6.0 09 Jun 2020 H1 non-standard Yes Details →
6.5.1 01 Jun 2020 H1 non-standard Yes Details →
6.5.0 28 May 2020 H1 non-standard Yes Details →
6.4.1 24 May 2020 H1 non-standard Yes Details →
6.4.0 18 May 2020 H1 non-standard Yes Details →
6.3.0 16 May 2020 H1 non-standard Yes Details →
6.2.0 13 May 2020 H1 non-standard Yes Details →
6.1.0 08 May 2020 H1 non-standard Yes Details →
4.0.2 30 Mar 2020 H1 non-standard Yes Details →
4.0.0 28 Sep 2018 H1 non-standard Yes Details →
4.0.0-preview6007 22 Sep 2018 H1 non-standard Yes Details →
4.0.0-preview6006 21 Sep 2018 H1 non-standard Yes Details →
4.0.0-preview6005 21 Sep 2018 H1 non-standard Yes Details →
4.0.0-preview6004 18 Sep 2018 H1 non-standard Yes Details →
4.0.0-preview6003 14 Sep 2018 H1 non-standard Yes Details →
4.0.0-preview6002 10 Sep 2018 H1 non-standard Yes Details →
4.0.0-preview6001 06 Sep 2018 H1 non-standard Yes Details →
4.0.0-preview5 29 Aug 2018 H1 non-standard Yes Details →
4.0.0-preview4 29 Aug 2018 H1 non-standard Yes Details →
4.0.0-preview3 27 Aug 2018 H1 non-standard Yes Details →
4.0.0-preview2 20 Aug 2018 H1 non-standard Yes Details →
4.0.0-preview1 14 Aug 2018 H1 non-standard Yes Details →

All 72 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 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 Tgstation.Server.Api

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Insufficient Permission Vulnerability in tgstation-server 8.4 high 6.8.0 29 Jul 2024

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 Tgstation.Server.Api

Is Tgstation.Server.Api safe to use?

Vulert records 1 vulnerabilities for Tgstation.Server.Api in NuGet: 0 critical, 1 high, 0 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 Tgstation.Server.Api's Vulert package health score?

Vulert scores Tgstation.Server.Api 77/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 Tgstation.Server.Api affected?

No. 18.2.1, 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.

Which version of Tgstation.Server.Api should I use?

18.2.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does Tgstation.Server.Api have?

1 vulnerability is recorded for Tgstation.Server.Api in the NuGet ecosystem: 0 critical, 1 high, 0 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 Tgstation.Server.Api vulnerabilities disclosed?

0 vulnerabilities were recorded for Tgstation.Server.Api in the last 12 months, and the oldest entry in this database dates to 29 Jul 2024. 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 Tgstation.Server.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 Tgstation.Server.Api for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the Tgstation.Server.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.