CVE-2026-57137: PraisonAI AgentLoop onToolCall approval runs after tool execution

Published Sep 15, 2026
·
Updated

PraisonAI is a multi-agent teams system. From 1.4.0 until 1.7.2, createAgentLoop() in src/praisonai-ts/src/ai/agent-loop.ts passes executable tools to generateText() before invoking the onToolCall approval callback. Because the wrapped AI SDK executes tool handlers during generation, a callback that returns false records toolrejected only after the denied tool has already produced side effects and populated toolResults. Applications using onToolCall as a human or policy approval boundary can therefore execute rejected file, command, API, or data-modifying operations. This issue is fixed in version 1.7.2.

Affected Software

1 affected component
PraisonAI>1.4.0<1.7.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade PraisonAI AgentLoop to a version that resolves this vulnerability.

    Fixed in 1.7.2

Event History

Sep 15, 2026
CVE Published
via MITRE·10:20 AM
Data Sourced
via MITRE·10:20 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to meaningful impact?

Applications using createAgentLoop() and treating onToolCall as a human or policy approval boundary are exposed. The impact depends on the tools available to the agent, including tools that can modify files or data, run commands, or invoke external APIs.

2

What does an attacker need to exploit this behavior?

An attacker needs the ability to cause the agent to request a tool call that reaches a configured executable tool. No user interaction is required, but the affected application must expose a tool capable of producing side effects.

3

Are rejected tool calls safe in affected versions?

No. In affected versions, tool handlers can run during generateText() before onToolCall is invoked; returning false only records tool_rejected after side effects and toolResults may already exist.

4

What should be done if an immediate upgrade is not possible?

Do not rely on onToolCall to authorize side-effecting tools. Remove, disable, or externally enforce authorization for tools that execute commands, modify files or data, or call sensitive APIs until the affected AgentLoop behavior is remediated.

5

How can teams determine whether they may be affected?

Review whether the application uses createAgentLoop() with executable tools and an onToolCall callback that can deny calls. If so, inspect prior tool activity and toolResults because calls recorded as tool_rejected may already have executed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203