CVE-2025-67509

Workarounds

If you cannot upgrade immediately:

• Remove/disable MySQLSelectTool for any agent reachable from untrusted input.

• Ensure DB account used by the tool does not have FILE privilege.

• Ensure secure_file_priv is 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.

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.

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2025-67509 has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.8.12); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2025-67509? CVE-2025-67509 is a high-severity code injection vulnerability in neuron-core/neuron-ai (composer), affecting versions <= 2.8.11. It is fixed in 2.8.12. Untrusted input is evaluated as executable code within the application's runtime environment.
2. How severe is CVE-2025-67509? CVE-2025-67509 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of neuron-core/neuron-ai are affected by CVE-2025-67509? neuron-core/neuron-ai (composer) versions <= 2.8.11 is affected.
4. Is there a fix for CVE-2025-67509? Yes. CVE-2025-67509 is fixed in 2.8.12. Upgrade to this version or later.
5. Is CVE-2025-67509 exploitable, and should I be worried? Whether CVE-2025-67509 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-67509 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-67509? Upgrade neuron-core/neuron-ai to 2.8.12 or later.