Vulnerability Database · NuGet · Package report
ExCSS: vulnerability history, versions and safety
ExCSS is a package in the NuGet ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the NuGet ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on ExCSS 4.3.2 i
Updated on 23 Oct 2026
Good news: 4.3.2, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Niche
- Community Moderate
What to do: Stay on 4.3.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.3.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 4.3.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 377 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 ExCSS, 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.
- 4.3.2 23 Jul 2026
- 4.3.1 28 Jul 2025
- 4.3.0 22 Oct 2024
- 4.2.7 11 Oct 2024
- 4.2.6 23 Sep 2024
- 4.2.5 22 Jan 2024
- 4.2.5-release0000 22 Jan 2024
- 4.2.4 02 Oct 2023
- 4.2.4-release0000 02 Oct 2023
- 4.2.3 29 Sep 2023
- 4.2.3-release0000 29 Sep 2023
- 4.2.2 03 Sep 2023
- 4.2.2-release0000 31 Aug 2023
- 4.2.1 06 Jul 2023
- 4.2.1-release0000 06 Jul 2023
- 4.2.0 08 Apr 2023
- 4.2.0-release0004 08 Apr 2023
- 4.2.0-release0000 08 Apr 2023
- 4.1.4 06 Jul 2022
- 4.1.3 21 Dec 2021
- 4.1.2 21 Dec 2021
- 4.1.1 16 Sep 2021
- 4.1.0 09 Dec 2020
- 4.0.2 23 Nov 2020
- 4.0.0 05 Nov 2020
- 3.0.0 13 Mar 2018
- 2.0.6 29 Apr 2015
- 2.0.5 07 Oct 2014
- 2.0.3 14 Jul 2014
- 2.0.2 24 Jan 2014
- 2.0.1 10 Jan 2014
- 2.0.0 03 Dec 2013
- 1.1.0 20 Jul 2012
- 1.0.10 04 Apr 2012
- 1.0.9 25 Mar 2012
- 1.0.8 19 Mar 2012
- 1.0.7 17 Mar 2012
- 1.0.6 16 Mar 2012
- 1.0.5 11 Mar 2012
- 1.0.4 11 Mar 2012
- 1.0.3 11 Mar 2012
- 1.0.2 10 Mar 2012
- 1.0.1 10 Mar 2012
- 1.0.0
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 4.3.2 | 23 Jul 2026 | none | MIT | — | Details → |
| 4.3.1 | 28 Jul 2025 | none | MIT | — | Details → |
| 4.3.0 | 22 Oct 2024 | none | MIT | — | Details → |
| 4.2.7 | 11 Oct 2024 | none | MIT | — | Details → |
| 4.2.6 | 23 Sep 2024 | none | MIT | — | Details → |
| 4.2.5 | 22 Jan 2024 | none | MIT | — | Details → |
| 4.2.5-release0000 | 22 Jan 2024 | none | MIT | — | Details → |
| 4.2.4 | 02 Oct 2023 | none | MIT | — | Details → |
| 4.2.4-release0000 | 02 Oct 2023 | none | MIT | — | Details → |
| 4.2.3 | 29 Sep 2023 | none | MIT | — | Details → |
| 4.2.3-release0000 | 29 Sep 2023 | none | MIT | — | Details → |
| 4.2.2 | 03 Sep 2023 | none | MIT | — | Details → |
| 4.2.2-release0000 | 31 Aug 2023 | none | MIT | — | Details → |
| 4.2.1 | 06 Jul 2023 | none | MIT | — | Details → |
| 4.2.1-release0000 | 06 Jul 2023 | none | MIT | — | Details → |
| 4.2.0 | 08 Apr 2023 | none | MIT | — | Details → |
| 4.2.0-release0004 | 08 Apr 2023 | none | MIT | — | Details → |
| 4.2.0-release0000 | 08 Apr 2023 | none | — | — | Details → |
| 4.1.4 | 06 Jul 2022 | none | — | — | Details → |
| 4.1.3 | 21 Dec 2021 | none | — | — | Details → |
| 4.1.2 | 21 Dec 2021 | none | — | — | Details → |
| 4.1.1 | 16 Sep 2021 | none | — | — | Details → |
| 4.1.0 | 09 Dec 2020 | none | — | — | Details → |
| 4.0.2 | 23 Nov 2020 | none | — | — | Details → |
| 4.0.0 | 05 Nov 2020 | none | — | — | Details → |
| 3.0.0 | 13 Mar 2018 | none | — | — | Details → |
| 2.0.6 | 29 Apr 2015 | none | — | — | Details → |
| 2.0.5 | 07 Oct 2014 | none | — | — | Details → |
| 2.0.3 | 14 Jul 2014 | none | — | — | Details → |
| 2.0.2 | 24 Jan 2014 | none | — | — | Details → |
| 2.0.1 | 10 Jan 2014 | none | — | — | Details → |
| 2.0.0 | 03 Dec 2013 | none | — | — | Details → |
| 1.1.0 | 20 Jul 2012 | none | — | — | Details → |
| 1.0.10 | 04 Apr 2012 | none | — | — | Details → |
| 1.0.9 | 25 Mar 2012 | none | — | — | Details → |
| 1.0.8 | 19 Mar 2012 | none | — | — | Details → |
| 1.0.7 | 17 Mar 2012 | none | — | — | Details → |
| 1.0.6 | 16 Mar 2012 | none | — | — | Details → |
| 1.0.5 | 11 Mar 2012 | none | — | — | Details → |
| 1.0.4 | 11 Mar 2012 | none | — | — | Details → |
| 1.0.3 | 11 Mar 2012 | none | — | — | Details → |
| 1.0.2 | 10 Mar 2012 | none | — | — | Details → |
| 1.0.1 | 10 Mar 2012 | none | — | — | Details → |
| 1.0.0 | — | none | — | — | Details → |
All 44 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.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for ExCSS
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
Questions
About ExCSS
Is ExCSS safe to use?
Vulert has no vulnerabilities on record for ExCSS 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 ExCSS's Vulert package health score?
Vulert scores ExCSS 85/100, which reads as healthy. 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 ExCSS affected?
No. 4.3.2, 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 ExCSS should I use?
4.3.2 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 ExCSS have?
0 vulnerabilities are recorded for ExCSS 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 ExCSS vulnerabilities disclosed?
0 vulnerabilities were recorded for ExCSS 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 ExCSS 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 ExCSS for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ExCSS version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.