VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

Svg: vulnerability history, versions and safety

Svg 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 Svg vulnerabilities

Vulert verdict on Svg 3.4.8 i

Updated on 23 Oct 2026

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

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

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

  • Current release 3.4.8 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,316 i
  • OpenSSF scorecard 3/10 i
  • Last release 2 months ago i
  • Licence MS-PL 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 Svg, 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.4.8 23 Jul 2026 none MS-PL — Details →
3.4.7 22 Feb 2024 none MS-PL — Details →
3.4.6 16 Nov 2023 none MS-PL — Details →
3.4.5 31 Oct 2023 none MS-PL — Details →
3.4.4 29 Oct 2022 none MS-PL — Details →
3.4.3 16 Jul 2022 none MS-PL — Details →
3.4.2 11 Apr 2022 none MS-PL — Details →
3.4.1 19 Mar 2022 none MS-PL — Details →
3.4.0 09 Jan 2022 none MS-PL — Details →
3.3.0 23 Sep 2021 none MS-PL — Details →
3.2.3 12 Jan 2021 none MS-PL — Details →
3.2.1 12 Jan 2021 none MS-PL — Details →
3.1.1 01 May 2020 none MS-PL — Details →
3.0.102 13 Jan 2020 none MS-PL — Details →
3.0.84 09 Nov 2019 none MS-PL — Details →
3.0.49 30 Aug 2019 none MS-PL — Details →
3.0.20-g594db9696a 29 Jul 2019 none MS-PL — Details →
3.0.9-g6ea47b4039 27 Jun 2019 none MS-PL — Details →
3.0.3-gecdc54b12b 19 Jun 2019 none MS-PL — Details →
2.4.3 07 May 2019 none non-standard — Details →
2.4.2 01 Mar 2019 none non-standard — Details →
2.4.1 25 Jan 2019 none non-standard — Details →
2.4.0 08 Jan 2019 none non-standard — Details →
2.4.0-preview1 01 Jan 2019 none non-standard — Details →
2.3.0 28 Dec 2016 none non-standard — Details →
2.2.2 17 Nov 2016 none non-standard — Details →
2.2.1 24 May 2016 none non-standard — Details →
2.2.0 09 May 2016 none non-standard — Details →
2.1.0 17 Sep 2015 none non-standard — Details →
2.0.0 23 Mar 2015 none non-standard — Details →
1.7.0 02 Jul 2014 none non-standard — Details →
1.6.1 13 Mar 2014 none non-standard — Details →
1.6.0 13 Mar 2014 none non-standard — Details →
1.5.2 25 Nov 2013 none non-standard — Details →
1.5.1 18 Nov 2013 none non-standard — Details →
1.5.0 13 Sep 2013 none non-standard — Details →
1.0.2 27 Jun 2013 none non-standard — Details →
1.0.1 20 Jun 2013 none non-standard — Details →
1.0.0 17 Jun 2013 none non-standard — Details →

All 39 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 Svg

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 Svg

Is Svg safe to use?

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

Vulert scores Svg 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 Svg affected?

No. 3.4.8, 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 Svg should I use?

3.4.8 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 Svg have?

0 vulnerabilities are recorded for Svg 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 Svg vulnerabilities disclosed?

0 vulnerabilities were recorded for Svg 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 Svg 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 Svg for upcoming vulnerabilities?

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