Vulnerability in praisonai-platform (CVE-2026-61442)
Summary
Vulnerability in praisonai-platform (CVE-2026-61442). Data can be tampered with by attackers. Mitigation: upgrade to 0.1.9 or later.
Original description
The description as published by the source.
PraisonAI Platform (praisonai-platform) before 0.1.9 fails to enforce owner/admin authorization on the PATCH routes for projects, issues, and agents, which only require workspace-member role. A workspace member can modify owner-created records; for projects, a member can reassign lead_id to their own user id and then delete the owner-created project, bypassing the delete route's owner/admin permission check.
Source: NIST National Vulnerability Database 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-61442 has been found in praisonai-platform.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade praisonai-platform to 0.1.9 or later.
If unsure, ask your IT team or search "praisonai-platform CVE-2026-61442" on the vendor's site.
CVE-2026-61442 (praisonai-platform) — CWE-862 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.1.9 — 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 praisonai-platform.
Check the vendor advisory for the affected versions of praisonai-platform.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to 0.1.9.
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 'praisonai-platform' . 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 'praisonai-platform' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
praisonai-platformを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade praisonai-platform to 0.1.9ステージング環境で 0.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- web github.com