Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-j8g6-5gqc-mq36
No affected components available
Impact
MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying). However, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE.
As a result, an attacker who can influence the tool input (e.g., prompt injection through a public agent endpoint) may be able to write arbitrary content to files on the DB server.
If the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory), the impact can escalate to remote code execution on the application host (for example, by writing a PHP web shell).
Who is impacted: Deployments that expose an agent using MySQLSelectTool to untrusted input and run with overly-permissive DB privileges/configuration.
Patches
Not patched in: 2.8.11
Fixed in: 2.8.12
Recommended fix direction:
-
Explicitly reject queries containing:
INTO,OUTFILE,DUMPFILE,LOAD_FILE, and other file/IO-related functions/clauses. -
Prefer AST-based validation (SQL parser) over keyword checks.
-
Constrain allowed tables/columns and disallow multi-statements.
Workarounds
If you cannot upgrade immediately:
-
Remove/disable
MySQLSelectToolfor any agent reachable from untrusted input. -
Ensure DB account used by the tool does not have
FILEprivilege. -
Ensure
secure_file_privis set to a directory that is not web-accessible (or restrict it tightly). -
Add a defensive query filter at the application layer rejecting
INTO OUTFILE,INTO DUMPFILE,LOAD_FILE,;(multi-statements), and suspicious comment patterns.
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a low impact on the confidentiality of the information. There is a high impact on the integrity of the data.
Exploitation activity has been observed. Apply available patches or mitigations urgently.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard