VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

dbup-core: vulnerability history, versions and safety

dbup-core is a package in the NuGet ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the NuGet ecosystem.

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 dbup-core vulnerabilities

Vulert verdict on dbup-core 6.1.1 i

Updated on 23 Oct 2026

Good news: 6.1.1, the version you would install today, has no known vulnerabilities.

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 6.1.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2,632 i
  • OpenSSF scorecard 3/10 i
  • Last release 8 months ago i
  • Licence MIT 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 dbup-core, 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
6.1.1 23 Feb 2026 none MIT — Details →
6.0.15 06 Nov 2025 none MIT — Details →
6.0.4 17 Dec 2024 none MIT — Details →
6.0.3 22 Oct 2024 none MIT — Details →
6.0.0 30 Sep 2024 none MIT — Details →
6.0.0-beta.146 25 Jul 2024 none MIT — Details →
6.0.0-beta.108 18 Mar 2024 none MIT — Details →
5.0.87 15 Mar 2024 none MIT — Details →
6.0.0-beta.73 15 Mar 2024 none MIT — Details →
6.0.0-beta.44 15 Mar 2024 none MIT — Details →
5.0.76 31 Jan 2024 none MIT — Details →
5.0.37 18 Oct 2023 none MIT — Details →
5.0.10 26 Nov 2022 none MIT — Details →
5.0.8 24 Nov 2022 none MIT — Details →
4.6.3 10 May 2022 none MIT — Details →
4.6.0 05 May 2022 none MIT — Details →
4.5.0 21 Nov 2020 none non-standard — Details →
4.4.0 17 Jun 2020 none non-standard — Details →
4.3.1 04 Dec 2019 none non-standard — Details →
4.3.0 26 Nov 2019 none non-standard — Details →
4.2.0 15 Nov 2018 none non-standard — Details →
4.1.1 07 Nov 2018 none non-standard — Details →
4.1.0 26 Apr 2018 none non-standard — Details →
4.0.1 24 Apr 2018 none non-standard — Details →
4.0.1-oraclesupport0001 24 Apr 2018 none non-standard — Details →
4.0.0 15 Apr 2018 none non-standard — Details →
4.0.0-beta0005 17 Mar 2018 none non-standard — Details →
4.0.0-beta0004 27 Feb 2018 none non-standard — Details →
4.0.0-beta0003 18 Feb 2018 none non-standard — Details →
4.0.0-beta0002 12 Sep 2017 none non-standard — Details →
4.6.4-improve-package-health.3 — none MIT — Details →
6.0.0-beta.22 — none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for dbup-core

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 dbup-core

Is dbup-core safe to use?

Vulert has no vulnerabilities on record for dbup-core in NuGet at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is dbup-core's Vulert package health score?

Vulert scores dbup-core 80/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 dbup-core affected?

No. 6.1.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 dbup-core should I use?

6.1.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 dbup-core have?

0 vulnerabilities are recorded for dbup-core in the NuGet ecosystem: 0 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 dbup-core vulnerabilities disclosed?

0 vulnerabilities were recorded for dbup-core in the last 12 months. 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 dbup-core 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 dbup-core for upcoming vulnerabilities?

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