Neuron MySQLSelectTool “read-only” bypass via SELECT ... INTO OUTFILE (file write → potential RCE)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

EPSS

• CVE-2025-67509: 0.29% estimated exploitation activity in the next 30 days; percentile 21.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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,…

Published by the source

9 Dec 2025, 17:19 UTC

Last modified by the source

11 Dec 2025, 15:49 UTC

Source last checked

26 Oct 2026, 14:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j8g6-5gqc-mq36

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-67509

Advisory: Neuron MySQLSelectTool “read-only” bypass via `SELECT ... INTO OUTFILE` (file write → potential RCE)
IDs: CVE-2025-67509, GHSA-j8g6-5gqc-mq36
Record: https://patchnext.com/advisories/cve-2025-67509 (revision 1, source checked 26 Oct 2026, 14:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: neuron-core/neuron-ai 2.8.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist neuron-core/neuron-ai: affected <= 2.8.11; fixed in 2.8.12

## Suggested inspection (read-only)
- Packagist neuron-core/neuron-ai: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on neuron-core/neuron-ai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j8g6-5gqc-mq36 (GitHub-reviewed advisory GHSA-j8g6-5gqc-mq36 lists affected ranges: Packagist neuron-core/neuron-ai >=0 <=2.8.11)

Commands are suggestions: review each one before running it.