CVE-2016-0655 is an unspecified vulnerability in the InnoDB component of Oracle MySQL and MariaDB. It affects Oracle MySQL 5.6.29 and earlier, Oracle MySQL 5.7.11 and earlier, MariaDB 10.0 releases before 10.0.25, and MariaDB 10.1 releases before 10.1.14. The underlying defective function and triggering input are not publicly specified.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Unspecified MySQL Server InnoDB vulnerability.
Unspecified MySQL Server InnoDB vulnerability.
Unspecified MySQL Server InnoDB-component vulnerability fixed in the MariaDB update.
A moderate-severity InnoDB availability vulnerability affecting specified Oracle MySQL and MariaDB releases. It requires a single authenticated user account and can cause a partial availability impact (CVSS v2 3.5).
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.