Vulnerability in praisonaiagents (CVE-2026-55530)
Summary
Vulnerability in praisonaiagents (CVE-2026-55530). Data can be tampered with by attackers. Mitigation: upgrade to 1.6.58 or later.
Original description
The description as published by the source.
PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.58, ast_grep_rewrite lacks the @require_approval decorator used by sibling mutation tools. With dry_run=False, an agent-controlled call can pass --update-all and a broad path to rewrite matching files without the expected authorization gate. This issue is fixed in version 1.6.58.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55530 has been found in praisonaiagents.
Data can be tampered with by attackers. CVSS score: 6.1/10.
What to do: upgrade praisonaiagents to 1.6.58 or later.
If unsure, ask your IT team or search "praisonaiagents CVE-2026-55530" on the vendor's site.
CVE-2026-55530 (praisonaiagents) — CWE-862 / CVSS v3 6.1
Attack vector: local / unauthenticated
Patched: 1.6.58 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in praisonaiagents.
Check the vendor advisory for the affected versions of praisonaiagents.
Severity: Medium (CVSS 6.1/10). Data can be tampered with by attackers.
Update to 1.6.58.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'praisonaiagents' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'praisonaiagents' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
praisonaiagentsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade praisonaiagents to 1.6.58ステージング環境で 1.6.58 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- web github.com
- web github.com