CVE-2026-61426: PraisonAI before 1.7.3 Unauthenticated Agent Access via Insecure Defaults
PraisonAI before 1.7.3 contains an insecure default configuration that binds to all interfaces with no API key requirement and wildcard CORS. Unauthenticated attackers can call GET /api/agents to read agent instructions and system prompts, or POST /api/chat to invoke agents without authentication.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
PraisonAIto a version that resolves this vulnerability.Fixed in 1.7.3 - Configuration
Update PraisonAI default configuration to stop using wildcard CORS.
PraisonAI (API server) CORS = Restrict from wildcard to specific origins (no wildcard CORS) - Configuration
Change insecure defaults so the server does not expose GET /api/agents and POST /api/chat without authentication/API key.
PraisonAI (API server) API authentication requirement = Require an API key / authentication for /api/agents and /api/chat - Configuration
Update configuration so PraisonAI does not bind to all interfaces by default.
PraisonAI (API server) Bind address / network exposure = Bind to specific/internal interfaces only (not all interfaces)
Event History
Frequently Asked Questions
What is the severity of CVE-2026-61426?
CVE-2026-61426 has a severity rating of 8.8, categorized as high.
How do I fix CVE-2026-61426?
To fix CVE-2026-61426, upgrade PraisonAI to version 1.7.3 or later to eliminate insecure default configurations.
What are the consequences of exploiting CVE-2026-61426?
Exploiting CVE-2026-61426 allows unauthenticated attackers to access sensitive agent instructions and invoke agents without authentication.
What versions of PraisonAI are affected by CVE-2026-61426?
CVE-2026-61426 affects all versions of PraisonAI prior to 1.7.3.
Is there a CVE for PraisonAI's insecure default configurations?
Yes, CVE-2026-61426 specifically addresses the issue of insecure default configurations in PraisonAI.