VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

ming: vulnerability history, versions and safety

ming is a package in the Debian ecosystem. Vulert records 9 vulnerabilities for it across 9 releases, from Jan 2017 to May 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded U9
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 ming vulnerabilities

Vulert verdict on ming i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 26 May 2018. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 9 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 9 over 1 year · 0 in the last year i
  • Latest disclosure 26 May 2018 i
  • Highest CVSS n/a i
  • With no published fix 0 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 ming, 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 9 of 9 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 5
  • 2018 4

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

03 Vulnerabilities

Recorded vulnerabilities for ming

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Security Update for ming Package N/A unrated 1:0.4.4-1.1+deb7u4 14 Oct 2017
Security Update for ming Package N/A unrated 1:0.4.4-1.1+deb7u5 18 Nov 2017
ming - Security Update N/A unrated 1:0.4.4-1.1+deb7u6 11 Jan 2018
Security Update for ming package N/A unrated 1:0.4.4-1.1+deb7u7 11 Mar 2018
ming - Multiple Vulnerabilities N/A unrated 1:0.4.4-1.1+deb7u8 09 Apr 2018

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 ming

Is ming safe to use?

Vulert records 9 vulnerabilities for ming in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 9 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does ming have?

9 vulnerabilities are recorded for ming in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 9 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 ming vulnerabilities disclosed?

0 vulnerabilities were recorded for ming in the last 12 months, and the oldest entry in this database dates to 26 Jan 2017. 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 ming 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 ming for upcoming vulnerabilities?

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