MySQL Shell CVE-2026-46870

Attacker must have low-privileged network access and the ability to interact with the MySQL Shell for VS Code component over one of its supported protocols (the description explicitly says 'multiple protocols'), which in practice means a developer must initiate or accept a connection from the VS Code extension toward an endpoint the attacker can influence. Exploitation is gated by AC:H (high attack complexity - specific timing, configuration, or sequencing required), is limited to deployments running MySQL Shell 2026.2.0+9.6.1 with the VS Code extension active, and requires PR:L meaning the attacker is not fully unauthenticated against the target environment. No user interaction is required per CVSS (UI:N), but a developer-initiated session against attacker-influenced infrastructure is the realistic pathway.

The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H) yields 8.5 - high severity driven by network reach, scope change, and full CIA impact, but offset by high attack complexity and a required low-privilege foothold. EPSS data is not provided and the vulnerability is not in CISA KEV, with no public POC referenced, suggesting this is currently a theoretical/Oracle-internal finding rather than an active threat. The description states 'network access via multiple protocols' for an IDE-embedded shell, which is unusual - verify with Oracle whether this means an attacker-controlled MySQL server, malicious protocol responses, or another path, as that distinction materially changes who is exposed. Overall this should be patched on the next maintenance cycle for developer workstations running the VS Code extension, but it is not an emergency-grade issue at this time.

An attacker who already has a low-privileged foothold on the network (for example, controlling a rogue MySQL instance or man-in-the-middling a developer's connection) lures a developer's MySQL Shell for VS Code session into connecting, and through a complex sequence of crafted protocol responses compromises the Shell process. Because of the scope change, the attacker pivots from the Shell into the VS Code host or other components, potentially executing developer-side actions or exfiltrating credentials. No public POC is available, and high attack complexity means the chain is not trivial to reproduce.