https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 06:45:59 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-263214 EUVD-2026-263214 https://cve.radiocsirt.org/vuln/euvd-2026-263214 https://cve.radiocsirt.org/vuln/fkie_cve-2025-67510 <p>Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.</p> <p>Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-67510 https://cve.radiocsirt.org/vuln/ghsa-898v-775g-777c <p><strong>Affected:</strong> Packagist: neuron-core/neuron-ai</p> <p>### Impact</p> <p>`MySQLWriteTool` executes arbitrary SQL provided by the caller using `PDO::prepare()` + `execute()` without semantic restrictions.</p> <p>This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as `DROP TABLE`, `TRUNCATE`, `DELETE`, `ALTER`, or privilege-related statements (subject to DB permissions).</p> <p>**Who is impacted:** Deployments that expose an agent with `MySQLWriteTool` enabled to untrusted input and/or run the tool with a DB user that has broad privileges.</p> <p>### Patches</p> <p>**Not patched in:** 2.8.11</p> <p>Recommended improvements (even if keeping the tool intentionally powerful):</p> <p>- Provide a safer API that supports only constrained operations (e.g., `insertRecord`, `updateRecord`) with allowlisted tables/columns.</p> <p>- Add a policy/allowlist layer (e.g., allow only `INSERT`/`UPDATE` on selected tables; forbid `DROP/TRUNCATE/ALTER/GRANT`).</p> <p>- Add optional review workflow: log + require human approval for high-risk statements; or “dry-run” mode.</p> <p>- Document strongly that the tool must not be exposed to untrusted prompts without additional safeguards.</p> <p>### Workarounds</p> <p>- Do not enable `MySQLWriteTool` for public/untrusted agents.</p> <p>- Use a dedicated DB user with **least privilege**:</p> <p>- no `DROP`, no `ALTER`, no `GRANT`, no access to sensitive tables unless necessary</p> <p>- Add an application-layer policy rejecting high…</p> <p><strong>Affected:</strong> Packagist: neuron-core/neuron-ai</p> <p>### Impact</p> <p>`MySQLWriteTool` executes arbitrary SQL provided by the caller using `PDO::prepare()` + `execute()` without semantic restrictions.</p> <p>This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as `DROP TABLE`, `TRUNCATE`, `DELETE`, `ALTER`, or privilege-related statements (subject to DB permissions).</p> <p>**Who is impacted:** Deployments that expose an agent with `MySQLWriteTool` enabled to untrusted input and/or run the tool with a DB user that has broad privileges.</p> <p>### Patches</p> <p>**Not patched in:** 2.8.11</p> <p>Recommended improvements (even if keeping the tool intentionally powerful):</p> <p>- Provide a safer API that supports only constrained operations (e.g., `insertRecord`, `updateRecord`) with allowlisted tables/columns.</p> <p>- Add a policy/allowlist layer (e.g., allow only `INSERT`/`UPDATE` on selected tables; forbid `DROP/TRUNCATE/ALTER/GRANT`).</p> <p>- Add optional review workflow: log + require human approval for high-risk statements; or “dry-run” mode.</p> <p>- Document strongly that the tool must not be exposed to untrusted prompts without additional safeguards.</p> <p>### Workarounds</p> <p>- Do not enable `MySQLWriteTool` for public/untrusted agents.</p> <p>- Use a dedicated DB user with **least privilege**:</p> <p>- no `DROP`, no `ALTER`, no `GRANT`, no access to sensitive tables unless necessary</p> <p>- Add an application-layer policy rejecting high…</p> https://cve.radiocsirt.org/vuln/ghsa-898v-775g-777c