Vulnerability Database · NuGet · Package report

Zendesk-Api: vulnerability history, versions and safety

Zendesk-Api is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 69 releases, first recorded in Jun 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 C1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in NuGet →

Vulert verdict on Zendesk-Api i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for Zendesk-Api is a malicious-package vulnerability — a published version contained hostile code rather than a bug. Do not install it, and check whether it is already resolved in your dependencies.

Long-term outlook: risky 1 vulnerability on record across 1 year, none in the last year.

What to do: Do not install this package. If it is already in your dependency tree, remove or replace it, and check what resolved it in the first place. Vulert keeps watching the name: if a maintained replacement appears, you will see it here. Monitor it with Vulert →

  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 25 Jun 2024 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 1 i

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 holds for Zendesk-Api, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
12.58.0 C1 No Details →
12.57.9 C1 No Details →
12.57.8 C1 No Details →
1.24.66 C1 No Details →
1.24.65 C1 No Details →
1.24.64 C1 No Details →
1.24.63 C1 No Details →
1.24.62 C1 No Details →
1.24.61 C1 No Details →
1.24.60 C1 No Details →
1.24.59 C1 No Details →
1.24.58 C1 No Details →
1.24.57 C1 No Details →
1.24.56 C1 No Details →
1.24.55 C1 No Details →
1.24.54 C1 No Details →
1.24.53 C1 No Details →
1.24.52 C1 No Details →
1.24.51 C1 No Details →
1.24.50 C1 No Details →
1.24.49 C1 No Details →
1.24.48 C1 No Details →
1.24.47 C1 No Details →
1.24.46 C1 No Details →
1.24.45 C1 No Details →
1.24.44 C1 No Details →
1.24.43 C1 No Details →
1.24.42 C1 No Details →
1.24.41 C1 No Details →
1.24.40 C1 No Details →
1.24.39 C1 No Details →
1.24.38 C1 No Details →
1.24.37 C1 No Details →
1.24.36 C1 No Details →
1.24.35 C1 No Details →
1.24.34 C1 No Details →
1.24.33 C1 No Details →
1.24.32 C1 No Details →
1.24.31 C1 No Details →
1.24.30 C1 No Details →
1.24.29 C1 No Details →
1.24.28 C1 No Details →
1.24.27 C1 No Details →
1.24.26 C1 No Details →
1.24.25 C1 No Details →
1.24.24 C1 No Details →
1.24.23 C1 No Details →
1.24.22 C1 No Details →
1.24.21 C1 No Details →
1.24.20 C1 No Details →
1.24.19 C1 No Details →
1.24.18 C1 No Details →
1.24.17 C1 No Details →
1.24.16 C1 No Details →
1.24.15 C1 No Details →
1.24.14 C1 No Details →
1.24.13 C1 No Details →
1.24.12 C1 No Details →
1.24.11 C1 No Details →
1.24.10 C1 No Details →
1.24.9 C1 No Details →
1.24.8 C1 No Details →
1.24.7 C1 No Details →
1.24.6 C1 No Details →
1.24.5 C1 No Details →
1.24.4 C1 No Details →
1.24.3 C1 No Details →
1.24.2 C1 No Details →
1.24.1 C1 No Details →

Newest 69 of 69 versions on record. 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 Zendesk-Api

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

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 Zendesk-Api

Is Zendesk-Api safe to use?

No. Vulert records a malicious-package vulnerability for Zendesk-Api: a published version contained hostile code rather than a bug, and the package looks like one that was withdrawn for abuse. Do not install it, and check whether it is already resolved in your dependencies.

How many vulnerabilities does Zendesk-Api have?

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

0 vulnerabilities were recorded for Zendesk-Api in the last 12 months, and the oldest entry in this database dates to 25 Jun 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 Zendesk-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.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor Zendesk-Api for upcoming vulnerabilities?

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