VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

Syncfusion.SfShared.UWP: vulnerability history, versions and safety

Syncfusion.SfShared.UWP 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 Syncfusion.SfShared.UWP vulnerabilities

Vulert verdict on Syncfusion.SfShared.UWP 35.1.41 i

Updated on 23 Oct 2026

Good news: Vulert has no vulnerability on record for Syncfusion.SfShared.UWP in the NuGet ecosystem. That is a good sign, not a guarantee — keep an eye on the versions you run.

Package health score 100/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Not enough data
  • Community Not enough data

What to do: Run a supported release and keep monitoring: new vulnerabilities are published for packages every day. Nothing yet: a new vulnerability can appear at any time — Vulert alerts you if one affects this package. Monitor it with Vulert →

  • Current release 35.1.41 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 3 months ago i
  • Licence non-standard 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 Syncfusion.SfShared.UWP, 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
34.1.32 21 Jul 2026 none non-standard — Details →
34.1.31 13 Jul 2026 none non-standard — Details →
34.1.29 06 Jul 2026 none non-standard — Details →
33.2.13 16 Jun 2026 none non-standard — Details →
33.2.6 12 May 2026 none non-standard — Details →
33.2.5 04 May 2026 none non-standard — Details →
33.1.46 30 Mar 2026 none non-standard — Details →
16.1.0.22 — none non-standard — Details →
16.2.0.46 — none non-standard — Details →
16.2.0.50 — none non-standard — Details →
16.3.0.17-beta — none non-standard — Details →
16.3.0.21 — none non-standard — Details →
16.3.0.29 — none non-standard — Details →
16.3.0.35-beta — none non-standard — Details →
16.3.0.36 — none non-standard — Details →
16.4.0.40-beta — none non-standard — Details →
16.4.0.42 — none non-standard — Details →
16.4.0.44 — none non-standard — Details →
16.4.0.46 — none non-standard — Details →
16.4.0.47 — none non-standard — Details →
16.4.0.48 — none non-standard — Details →
16.4.0.52 — none non-standard — Details →
16.4.0.53 — none non-standard — Details →
16.4.0.54 — none non-standard — Details →
17.1.0.32-beta — none non-standard — Details →
17.1.0.38 — none non-standard — Details →
17.1.0.40 — none non-standard — Details →
17.1.0.41 — none non-standard — Details →
17.1.0.42 — none non-standard — Details →
17.1.0.43 — none non-standard — Details →
17.1.0.44 — none non-standard — Details →
17.1.0.47 — none non-standard — Details →
17.1.0.48 — none non-standard — Details →
17.1.0.49 — none non-standard — Details →
17.1.0.50 — none non-standard — Details →
17.1.0.51 — none non-standard — Details →
17.1.0.52 — none non-standard — Details →
17.1.0.53 — none non-standard — Details →
17.2.0.28-beta — none non-standard — Details →
17.2.0.34 — none non-standard — Details →
17.2.0.35 — none non-standard — Details →
17.2.0.36 — none non-standard — Details →
17.2.0.39 — none non-standard — Details →
17.2.0.40 — none non-standard — Details →
17.2.0.41 — none non-standard — Details →
17.2.0.46 — none non-standard — Details →
17.2.0.47 — none non-standard — Details →
17.2.0.49 — none non-standard — Details →
17.2.0.51 — none non-standard — Details →
17.3.0.14 — none non-standard — Details →
17.3.0.17 — none non-standard — Details →
17.3.0.19 — none non-standard — Details →
17.3.0.21 — none non-standard — Details →
17.3.0.26 — none non-standard — Details →
17.3.0.27 — none non-standard — Details →
17.3.0.28 — none non-standard — Details →
17.3.0.29 — none non-standard — Details →
17.3.0.30 — none non-standard — Details →
17.3.0.33 — none non-standard — Details →
17.3.0.34 — none non-standard — Details →
17.3.0.9-beta — none non-standard — Details →
17.4.0.39 — none non-standard — Details →
17.4.0.40 — none non-standard — Details →
17.4.0.41 — none non-standard — Details →
17.4.0.43 — none non-standard — Details →
17.4.0.44 — none non-standard — Details →
17.4.0.46 — none non-standard — Details →
17.4.0.47 — none non-standard — Details →
17.4.0.49 — none non-standard — Details →
17.4.0.50 — none non-standard — Details →
17.4.0.51 — none non-standard — Details →
17.4.0.53 — none non-standard — Details →
17.4.0.55 — none non-standard — Details →
18.1.0.36-beta — none non-standard — Details →
18.1.0.42 — none non-standard — Details →
18.1.0.43 — none non-standard — Details →
18.1.0.44 — none non-standard — Details →
18.1.0.45 — none non-standard — Details →
18.1.0.46 — none non-standard — Details →
18.1.0.48 — none non-standard — Details →
18.1.0.52 — none non-standard — Details →
18.1.0.53 — none non-standard — Details →
18.1.0.54 — none non-standard — Details →
18.1.0.55 — none non-standard — Details →
18.1.0.56 — none non-standard — Details →
18.1.0.57 — none non-standard — Details →
18.1.0.59 — none non-standard — Details →
18.2.0.44 — none non-standard — Details →
18.2.0.45 — none non-standard — Details →
18.2.0.46 — none non-standard — Details →
18.2.0.47 — none non-standard — Details →
18.2.0.48 — none non-standard — Details →
18.2.0.54 — none non-standard — Details →
18.2.0.55 — none non-standard — Details →
18.2.0.56 — none non-standard — Details →
18.2.0.57 — none non-standard — Details →
18.2.0.58 — none non-standard — Details →
18.2.0.59 — none non-standard — Details →
18.3.0.35 — none non-standard — Details →
18.3.0.38 — none non-standard — Details →
18.3.0.40 — none — — Details →
18.3.0.42 — none — — Details →
18.3.0.44 — none — — Details →
18.3.0.47 — none — — Details →
18.3.0.48 — none — — Details →
18.3.0.50 — none — — Details →
18.3.0.51 — none — — Details →
18.3.0.52 — none — — Details →
18.3.0.53 — none — — Details →
18.4.0.30 — none — — Details →
18.4.0.31 — none — — Details →
18.4.0.32 — none — — Details →
18.4.0.33 — none — — Details →
18.4.0.34 — none — — Details →
18.4.0.35 — none — — Details →
18.4.0.39 — none — — Details →
18.4.0.41 — none — — Details →
18.4.0.42 — none — — Details →
18.4.0.43 — none — — Details →
18.4.0.44 — none — — Details →

The newest 120 of 403 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 Syncfusion.SfShared.UWP

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 Syncfusion.SfShared.UWP

Is Syncfusion.SfShared.UWP safe to use?

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

Vulert scores Syncfusion.SfShared.UWP 100/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).

Which version of Syncfusion.SfShared.UWP should I use?

34.1.32 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 Syncfusion.SfShared.UWP have?

0 vulnerabilities are recorded for Syncfusion.SfShared.UWP 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 Syncfusion.SfShared.UWP vulnerabilities disclosed?

0 vulnerabilities were recorded for Syncfusion.SfShared.UWP 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 Syncfusion.SfShared.UWP 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 Syncfusion.SfShared.UWP for upcoming vulnerabilities?

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