Information Disclosure in praisonai (CVE-2026-40151)

Summary

Vulnerability in praisonai (CVE-2026-40151). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/agents. Mitigation: upgrade to 4.5.128 or later.

Original description

The description as published by the source.

Summary

The AgentOS deployment platform exposes a GET /api/agents endpoint that returns agent names, roles, and the first 100 characters of agent system instructions to any unauthenticated caller. The AgentOS FastAPI application has no authentication middleware, no API key validation, and defaults to CORS allow_origins=["*"] with host="0.0.0.0", making every deployment network-accessible and queryable from any origin by default.

Details

The AgentOS._register_routes() method at src/praisonai/praisonai/app/agentos.py:118 registers all routes on a plain FastAPI app with no authentication dependencies:

# agentos.py:147-160
@app.get(f"{self.config.api_prefix}/agents")
async def list_agents():
    return {
        "agents": [
            {
                "name": getattr(a, 'name', f'agent_{i}'),
                "role": getattr(a, 'role', None),
                "instructions": getattr(a, 'instructions', None)[:100] + "..." 
                    if getattr(a, 'instructions', None) and len(getattr(a, 'instructions', '')) > 100 
                    else getattr(a, 'instructions', None),
            }
            for i, a in enumerate(self.agents)
        ]
    }

The AgentAppConfig at src/praisonai-agents/praisonaiagents/app/config.py:12-55 has no authentication fields — no api_key, no auth_middleware, no token_secret. The only middleware added is CORS with wildcard origins:

# agentos.py:104-111
app.add_middleware(
    CORSMiddlewa…

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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-40151 has been found in praisonai.
Attackers can target a specific entry point like GET /api/agents over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade praisonai to 4.5.128 or later.
If unsure, ask your IT team or search "praisonai CVE-2026-40151" on the vendor's site.

CVE-2026-40151 (praisonai) — CWE-200
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /api/agents / AgentAppConfig / api_key / auth_middleware
Patched: 4.5.128 — 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

Information disclosure (CWE-200) exists in praisonai. Attackers reach the vulnerable code path via GET /api/agents without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of praisonai. Attack surface: GET /api/agents / AgentAppConfig / api_key / auth_middleware.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.5.128.

🛡️ 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 GET /api/agents requests with malformed payloads or SQL meta-characters. Run grep -r 'praisonai' . 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
Identify exposure identify
```
grep -r 'praisonai' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で praisonai を grep し、稼働しているサービス・バージョンを把握する。
2
Hunt for indicators of compromise detect
```
grep 'GET /api/agents' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで GET /api/agents への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
3
Apply patch patch
```
Upgrade praisonai to 4.5.128
```
ステージング環境で 4.5.128 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
4
Post-deployment verification verify
```
Replay attack against GET /api/agents on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI praisonai

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.128"}]}]

References

advisory nvd.nist.gov
package github.com
web github.com