Loading vulnerability…
CVE-2026-22005 is an unspecified vulnerability in the Server: Optimizer component of Oracle MySQL Server. It affects MySQL Server versions 8.0.0 through 8.0.45, 8.4.0 through 8.4.8, and 9.0.0 through 9.6.0. A high-privileged attacker with network access through multiple supported protocols can trigger a MySQL Server hang or a frequently repeatable crash, resulting in complete denial of service. The vulnerability is rated CVSS 3.1 4.9 (AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small proof-of-concept demonstrating a phishing-oriented abuse case of the OAuth 2.0 Device Authorization Grant, labeled as CVE-2026-22005. It contains two Python files: a simulated vulnerable authorization server (`device_code_server.py`) and a minimal attacker-side script (`exploit_device_code_phish.py`), plus a README and license. The server code defines two Flask-style routes, `/device/code` and `/token`, backed by an in-memory `codes` dictionary. `/device/code` generates a `device_code` and `user_code`, while `/token` accepts a `device_code` and, if the status is still pending, returns a hardcoded access token (`secret`) after a short delay. The README explains the intended weakness: the authorization server allows polling too frequently and does not sufficiently protect against phishing/social engineering during device flow completion. The attacker script is only skeletal; it imports `requests` and `time` and prints a status message, but does not implement full polling or brute-force logic. As a result, the repository is best classified as a POC rather than an operational exploit. The main exploit capability is demonstrating token theft/account takeover via rapid polling of a device flow token endpoint after tricking a victim into entering the attacker-controlled `user_code`. No hardcoded external IPs, domains, or full URLs are present beyond the local route paths and a README badge URL.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.