Vulert records 1 vulnerabilities for mono in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 1 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 mono have?

1 vulnerability is recorded for mono in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 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 mono vulnerabilities disclosed?

0 vulnerabilities were recorded for mono in the last 12 months, and the oldest entry in this database dates to 03 Nov 2007. 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 mono 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 mono for upcoming vulnerabilities?

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

Vulnerability Database · Debian · Package report

mono: vulnerability history, versions and safety

mono is a package in the Debian ecosystem. Vulert records 1 vulnerability for it across 1 release, first recorded in Nov 2007. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

1 vulnerabilities recorded U1

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mono vulnerabilities

Vulert verdict on mono i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 1 vulnerability 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 1 over 1 year · 0 in the last year i
Latest disclosure 03 Nov 2007 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert holds for mono, 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.

Version	Vulert vulnerabilities	Fix published	Details
1.2.2.1-1	U1	Yes	Details →

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

02 Disclosure history

How often vulnerabilities are recorded

2007 1

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

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for mono

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
Buffer Overflow Vulnerability in Mono	N/A unrated	1.2.2.1-1etch1	03 Nov 2007

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