VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

Fluid.Core: vulnerability history, versions and safety

Fluid.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 Fluid.Core vulnerabilities

Vulert verdict on Fluid.Core 2.40.0 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 2.40.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,788 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 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 Fluid.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
3.0.0-beta.8 03 Sep 2026 none MIT — Details →
2.40.0 20 Aug 2026 none MIT — Details →
3.0.0-beta.7 16 Aug 2026 none MIT — Details →
3.0.0-beta.6 30 Jul 2026 none MIT — Details →
3.0.0-beta.5 17 Feb 2026 none MIT — Details →
3.0.0-beta.4 30 Jan 2026 none MIT — Details →
3.0.0-beta.3 04 Dec 2025 none MIT — Details →
3.0.0-beta.2 20 Nov 2025 none MIT — Details →
3.0.0-beta.1 07 Nov 2025 none MIT — Details →
2.31.0 07 Nov 2025 none MIT — Details →
2.30.0 25 Oct 2025 none MIT — Details →
2.25.0 15 Jul 2025 none MIT — Details →
2.24.0 27 Apr 2025 none MIT — Details →
2.23.0 22 Apr 2025 none MIT — Details →
2.22.0 17 Apr 2025 none MIT — Details →
2.21.0 24 Mar 2025 none MIT — Details →
2.20.0 22 Mar 2025 none MIT — Details →
2.19.0 15 Jan 2025 none MIT — Details →
2.18.0 07 Jan 2025 none MIT — Details →
2.17.0 30 Dec 2024 none MIT — Details →
2.16.0 13 Dec 2024 none MIT — Details →
2.15.0 06 Dec 2024 none MIT — Details →
2.14.0 02 Dec 2024 none MIT — Details →
2.13.1 24 Nov 2024 none MIT — Details →
2.13.0 24 Nov 2024 none MIT — Details →
2.12.0 06 Nov 2024 none MIT — Details →
2.11.1 23 Jul 2024 none MIT — Details →
2.11.0 11 Jul 2024 none MIT — Details →
2.10.0 17 May 2024 none MIT — Details →
2.9.0 23 Apr 2024 none MIT — Details →
2.8.0 04 Apr 2024 none MIT — Details →
2.7.0 18 Mar 2024 none MIT — Details →
2.6.0 11 Mar 2024 none MIT — Details →
2.5.0 28 Sep 2023 none MIT — Details →
2.4.0 01 Mar 2023 none MIT — Details →
2.3.1 17 Dec 2022 none MIT — Details →
2.3.0 30 Nov 2022 none MIT — Details →
2.2.16 21 Sep 2022 none MIT — Details →
2.2.15 12 Apr 2022 none MIT — Details →
2.2.14 13 Jan 2022 none MIT — Details →
2.2.13 08 Jan 2022 none MIT — Details →
2.2.12 07 Jan 2022 none MIT — Details →
2.2.11 07 Jan 2022 none MIT — Details →
2.2.10 07 Jan 2022 none MIT — Details →
2.2.9 05 Jan 2022 none MIT — Details →
2.2.8 09 Dec 2021 none MIT — Details →
2.2.7 02 Dec 2021 none MIT — Details →
2.2.6 01 Dec 2021 none MIT — Details →
2.2.5 27 Nov 2021 none MIT — Details →
2.2.4 25 Nov 2021 none MIT — Details →
2.2.3 22 Nov 2021 none MIT — Details →
2.2.2 20 Nov 2021 none MIT — Details →
2.2.1 20 Nov 2021 none MIT — Details →
2.2.0 02 Nov 2021 none MIT — Details →
2.1.4 26 Oct 2021 none MIT — Details →
2.1.3 19 Oct 2021 none MIT — Details →
2.1.2 16 Oct 2021 none MIT — Details →
2.1.1 15 Oct 2021 none MIT — Details →
2.1.0 12 Oct 2021 none MIT — Details →
2.0.13 29 May 2021 none MIT — Details →
2.0.12 25 May 2021 none MIT — Details →
2.0.11 20 May 2021 none MIT — Details →
2.0.10 08 May 2021 none MIT — Details →
2.0.9 04 May 2021 none MIT — Details →
2.0.8 03 May 2021 none MIT — Details →
2.0.7 23 Apr 2021 none MIT — Details →
2.0.6 21 Apr 2021 none MIT — Details →
2.0.5 14 Apr 2021 none MIT — Details →
2.0.4 14 Apr 2021 none MIT — Details →
2.0.3 10 Apr 2021 none MIT — Details →
2.0.2 09 Apr 2021 none MIT — Details →
2.0.1 06 Apr 2021 none MIT — Details →
2.0.0-beta-1014 02 Apr 2021 none MIT — Details →
2.0.0-beta-1013 29 Mar 2021 none MIT — Details →
2.0.0-beta-1012 27 Mar 2021 none MIT — Details →
2.0.0-beta-1011 25 Mar 2021 none MIT — Details →
2.0.0-beta-1010 15 Mar 2021 none MIT — Details →
2.0.0-beta-1009 12 Mar 2021 none MIT — Details →
2.0.0-beta-1008 09 Mar 2021 none MIT — Details →
2.0.0-beta-1007 28 Feb 2021 none MIT — Details →
2.0.0-beta-1006 25 Feb 2021 none MIT — Details →
2.0.0-beta-1005 25 Feb 2021 none MIT — Details →
2.0.0-beta-1004 10 Feb 2021 none MIT — Details →
2.0.0-beta-1003 25 Jan 2021 none MIT — Details →
2.0.0-beta-1002 22 Jan 2021 none MIT — Details →
2.0.0-beta-1001 19 Jan 2021 none MIT — Details →
1.0.0 18 Jan 2021 none MIT — Details →
1.0.0-beta-9722 04 Dec 2020 none MIT — Details →
1.0.0-beta-9693 21 Sep 2020 none MIT — Details →
1.0.0-beta-9681 06 Aug 2020 none non-standard — Details →
1.0.0-beta-9678 21 Jul 2020 none non-standard — Details →
1.0.0-beta-9672 22 Jun 2020 none non-standard — Details →
1.0.0-beta-9663 08 Jun 2020 none non-standard — Details →
1.0.0-beta-9660 08 Jun 2020 none non-standard — Details →
1.0.0-beta-9651 21 May 2020 none non-standard — Details →
1.0.0-beta-9637 02 Mar 2020 none non-standard — Details →
1.0.0-beta-9634 15 Jan 2020 none non-standard — Details →
1.0.0-beta-9626 08 Jan 2020 none non-standard — Details →
1.0.0-beta-9624 28 Dec 2019 none non-standard — Details →
1.0.0-beta-9621 28 Dec 2019 none non-standard — Details →
1.0.0-beta-9619 28 Dec 2019 none — — Details →
1.0.0-beta-9617 24 Dec 2019 none — — Details →
1.0.0-beta-9614 24 Dec 2019 none — — Details →
1.0.0-beta-9608 30 Oct 2019 none — — Details →
1.0.0-beta-9605 10 Oct 2019 none — — Details →
1.0.0-beta-9599 20 Sep 2019 none — — Details →
1.0.0-beta-9588 28 Aug 2019 none — — Details →
1.0.0-beta-9586 22 Aug 2019 none — — Details →
1.0.0-beta-9578 15 Aug 2019 none — — Details →
1.0.0-beta-9571 02 Apr 2019 none — — Details →
1.0.0-beta-9560 22 Mar 2019 none — — Details →
1.0.0-beta-9558 21 Mar 2019 none — — Details →
1.0.0-beta-9554 14 Mar 2019 none — — Details →
1.0.0-beta-9545 05 Mar 2019 none — — Details →
1.0.0-beta-9542 03 Mar 2019 none — — Details →
1.0.0-beta-9519 04 Feb 2019 none — — Details →
1.0.0-beta-9513 22 Jan 2019 none — — Details →
1.0.0-beta-9507 21 Jan 2019 none — — Details →
1.0.0-beta-9504 17 Jan 2019 none — — Details →
1.0.0-beta-9501 17 Jan 2019 none — — Details →

The newest 120 of 148 versions Vulert tracks. 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 Fluid.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 Fluid.Core

Is Fluid.Core safe to use?

Vulert has no vulnerabilities on record for Fluid.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 Fluid.Core's Vulert package health score?

Vulert scores Fluid.Core 82/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 Fluid.Core affected?

No. 2.40.0, 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 Fluid.Core should I use?

2.40.0 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 Fluid.Core have?

0 vulnerabilities are recorded for Fluid.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 Fluid.Core vulnerabilities disclosed?

0 vulnerabilities were recorded for Fluid.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 Fluid.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 Fluid.Core for upcoming vulnerabilities?

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