Categories
CVE-2026-60089 medium CVSS 5.5

Path Traversal in praisonaiagents (CVE-2026-60089)

Summary

Path traversal in praisonaiagents (CVE-2026-60089). Data can be tampered with by attackers. Exploitable via praisonaiagents. Mitigation: upgrade to 1.6.78 or later.

Original description

The description as published by the source.

PraisonAI (pip package praisonaiagents) before 1.6.78 automatically loads defaults from a project-local .praisonai/config.toml when constructing an Agent, and does not validate the defaults.output.output_file path. A repository-controlled config file can set output_file to an absolute or '..' traversal path; when the developer subsequently calls agent.start() without explicitly passing an output parameter, PraisonAI writes the agent response to that path (creating parent directories as needed), allowing an untrusted checked-out project to overwrite files outside the project root with the privileges of the user running PraisonAI.

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-60089 has been found in praisonaiagents.
Attackers can target a specific entry point like praisonaiagents over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.5/10.
What to do: upgrade praisonaiagents to 1.6.78 or later.
If unsure, ask your IT team or search "praisonaiagents CVE-2026-60089" on the vendor's site.

CVE-2026-60089 (praisonaiagents) — CWE-22 / CVSS v3 5.5
Attack vector: local / unauthenticated
Attack surface: praisonaiagents / Agent / defaults.output.output_file / OutputConfig.output_file
Patched: 1.6.78 — 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.

❓ What is the problem

Path traversal (CWE-22) exists in praisonaiagents. Attackers reach the vulnerable code path via praisonaiagents without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of praisonaiagents. Attack surface: praisonaiagents / Agent / defaults.output.output_file / OutputConfig.output_file.

🔥 Severity

Severity: Medium (CVSS 5.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.6.78.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify
    grep -r 'praisonaiagents' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で praisonaiagents を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade praisonaiagents to 1.6.78

    ステージング環境で 1.6.78 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip praisonaiagents
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.78"}]}]
PyPI praisonaiagents
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.78"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details