Mysql Workbench vulnerabilitiesRanked by how likely they are to be used.

Product23 versions
The short answer

Mysql Workbench is made by Oracle. We track 42 published vulnerabilities in it, across 23 versions. None of them is on the list of flaws known to be exploited today. If you run Mysql Workbench, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Mysql Workbench vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Mysql Workbench's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Mysql Workbench 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.

50% or more10% to 49%Under 10%
  1. 92%

    A vulnerability was found in libssh's server-side state machine before versions 0.7.6 and 0.8.4.

    CVSS9.1Published17 Oct 2018
  2. 83%

    The c_rehash script does not properly sanitise shell metacharacters to prevent command injection.

    CVSS7.3Published3 May 2022
  3. 64%

    An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client.

    CVSS5.9Published25 Mar 2021
  4. 53%

    Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the...

    CVSS7.5Published21 Apr 2020
  5. 50%

    ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length.

    CVSS7.4Published24 Aug 2021
  6. 22%

    There's a flaw in libxml2 in versions before 2.9.11.

    CVSS8.8Published18 May 2021
  7. 22%

    Due to the formatting logic of the "console.table()" function it was not safe to allow user controlled input to be passed to the "properties" parameter while simultaneously passing a plain object with at least one...

    CVSS8.2Published24 Feb 2022
  8. 17%

    If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0...

    CVSS5.9Published27 Feb 2019
  9. 17%

    There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11.

    CVSS8.6Published19 May 2021
Precursor Intelligence

Running Mysql Workbench? 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 42 published vulnerabilities listed under the name Mysql Workbench, across 23 versions.

None of Mysql Workbench's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Mysql Workbench. 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.