Mono vulnerabilitiesRanked by how likely they are to be used.
Mono is made by Mono-Project. We track 5 published vulnerabilities listed under that exact name, across 317 versions. None of them is on the list of flaws known to be exploited today. Mono-Project lists newer releases under their own names, such as Mono Framework, so check those pages too.
We keep watching the known-exploited list.
Is Mono listed under other names? Yes.
Mono-Project also lists Mono under more specific names, such as Mono Framework. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Mono vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Mono's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Mono flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 3.5%CVE-2015-2320Critical
The TLS stack in Mono before 3.12.1 allows remote attackers to have unspecified impact via vectors related to client-side SSLv2 fallback.
- 3.2%CVE-2015-2319High
The TLS stack in Mono before 3.12.1 makes it easier for remote attackers to conduct cipher-downgrade attacks to EXPORT_RSA ciphers via crafted TLS traffic, related to the "FREAK" issue, a different vulnerability than...
- 2.6%CVE-2012-3543High
mono 2.10.x ASP.NET Web Form Hash collision DoS
- 2.0%CVE-2015-2318High
The TLS stack in Mono before 3.12.1 allows man-in-the-middle attackers to conduct message skipping attacks and consequently impersonate clients by leveraging missing handshake state validation, aka a "SMACK SKIP-TLS"...
- 1.0%CVE-2023-26314High
The mono package before 6.8.0.105+dfsg-3.3 for Debian allows arbitrary code execution because the application/x-ms-dos-executable MIME type is associated with an un-sandboxed Mono CLR interpreter.
Running Mono? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The TLS stack in Mono before 3.12.1 allows remote attackers to have unspecified impact via vectors related to client-side SSLv2 fallback.
- Matched to
- Mono on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 5 published vulnerabilities listed under the name Mono, across 317 versions.
None of Mono's vulnerabilities is on the list of flaws known to be exploited today.
Mono-Project also lists Mono under more specific names, such as Mono Framework. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Mono. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.