Quick answers
- Is CVE-2026-57137 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57137 being exploited in the wild.
- How severe is CVE-2026-57137?
- High severity, with a CVSS score of 8.8, published 15 September 2026.
- Which products and versions are affected?
- praisonai (npm) SEMVER:introduced=1.4.0,fixed=1.7.2.
- Is there a fix for CVE-2026-57137?
- Yes. praisonai (npm): upgrade to 1.7.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57137 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-57137?
- Check whether you run praisonai (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- praisonai (npm): upgrade to 1.7.2 or later
npm install praisonai@1.7.2
Technical details
The vulnerability is a logic-order flaw in AgentLoop.step() within src/praisonai-ts/src/ai/agent-loop.ts. The code passes executable tools directly to the AI SDK's generateText() function, which automatically executes any tool with an execute handler. Only after the tools have been executed and results collected does PraisonAI invoke the onToolCall approval callback. This inverts the intended approval model: AI SDK's native needsApproval pattern enforces approval before execution, but PraisonAI implements approval as a post-execution audit hook while naming it as a pre-execution approval gate. An attacker or malicious agent can invoke sensitive operations (file writes, API calls, etc.) through tools; the approval callback's rejection comes too late to prevent side effects. The vulnerability affects versions 1.4.0 through 1.7.1 and is fixed in 1.7.2 by moving approval checks before tool execution.
Affected products
- PraisonAI praisonai >=1.4.0, <=1.7.1
Identifiers
- CVE-2026-57137
- GHSA-h2w2-v7j6-xqm4
Timeline
- 2026-06-18: disclosed
- 2026-06-18: patched: Version 1.7.2 available with fix