Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8amended

npm PraisonAI utility shell safe-command wrapper allowlist bypass via shell chaining

CVE-2026-57133GHSA-5jv7-2mjm-h6qj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonai 1.7.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm praisonai

    Affected
    >= 1.5.1, <= 1.7.1
    Fixed in
    1.7.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-57133: 0.80% estimated exploitation activity in the next 30 days; percentile 56.78 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The published npm package praisonai ships dist/tools/utility-tools.js, which exports a shell(command) helper described in source as: The helper attempts to enforce a safe read-only command allowlist by checking only the first whitespace-delimited token: It then passes the entire original string to Node childprocess.exec(): Because exec() runs the command through a shell, a command string that starts with an allowed command can append a second non-allowlisted command with shell metacharacters. For example, direct printf <marker is rejected, but echo ok; printf <marker is accepted and executes printf. This bypasses the helper's safe-command policy and allows arbitrary shell commands to run with the PraisonAI process privileges when an application, agent, or integration exposes this helper to lower-trust users, prompts, model output, or plugin/tool input. The PoV is deterministic and local-only. It installs only the npm package, runs harmless marker commands, and does not…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-5jv7-2mjm-h6qj

  2. Revision 1 · created ·

    Published from osv record GHSA-5jv7-2mjm-h6qj

Agent brief

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

# Patch Next advisory brief: CVE-2026-57133

Advisory: npm PraisonAI utility shell safe-command wrapper allowlist bypass via shell chaining
IDs: CVE-2026-57133, GHSA-5jv7-2mjm-h6qj
Record: https://patchnext.com/advisories/cve-2026-57133 (revision 2, source checked 26 Oct 2026, 12:57 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: praisonai 1.7.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm praisonai: affected >= 1.5.1, <= 1.7.1; fixed in 1.7.2

## Suggested inspection (read-only)
- `npm ls praisonai --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 praisonai.
- 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://osv.dev/vulnerability/GHSA-5jv7-2mjm-h6qj (OSV record GHSA-5jv7-2mjm-h6qj lists affected ranges: npm praisonai >=1.5.1 <1.7.2 (fixed))
- Verified: https://github.com/advisories/GHSA-5jv7-2mjm-h6qj (GitHub-reviewed advisory GHSA-5jv7-2mjm-h6qj lists affected ranges: npm praisonai >=1.5.1 <=1.7.1)

Commands are suggestions: review each one before running it.

Loading voting…