Vulnerability Database · Debian · Package report

virtuoso-opensource: vulnerability history, versions and safety

virtuoso-opensource is a package in the Debian ecosystem. Vulert records 74 vulnerabilities for it across 14 releases, from May 2023 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
74 vulnerabilities recorded U74
i
74 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
11 in the last 12 months

Most recent disclosure 23 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on virtuoso-opensource i

Updated on 23 Oct 2026

Careful: 74 of the 74 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 74 vulnerabilities on record across 3 years, 11 in the last year.

What to do: Plan around the 74 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 74 over 3 years · 11 in the last year i
  • Latest disclosure 23 Jun 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 74 i

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 holds for virtuoso-opensource, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 14 of 14 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 33
  • 2025 30
  • 2026 11

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 11 of the 74 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for virtuoso-opensource

The 5 most severe of 74 vulnerabilities recorded for this package

Search all 74 in the database →

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 virtuoso-opensource

Is virtuoso-opensource safe to use?

Vulert records 74 vulnerabilities for virtuoso-opensource in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 74 not yet rated. 74 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does virtuoso-opensource have?

74 vulnerabilities are recorded for virtuoso-opensource in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 74 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new virtuoso-opensource vulnerabilities disclosed?

11 vulnerabilities were recorded for virtuoso-opensource in the last 12 months, and the oldest entry in this database dates to 15 May 2023. 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 virtuoso-opensource 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 virtuoso-opensource for upcoming vulnerabilities?

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