Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | This vulnerability presents moderate real-world risk despite a CVSS base score of 5.3 (low-to-moderate). The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) indicates a low-barrier network attack requiring no privileges or user interaction, but impact is confined to confidentiality (C:L) with no integrity or availability impact. However, the practical risk depends on deployment context: if AgentOS instances are internet-facing (default binding to 0.0.0.0 with permissive CORS), reconnaissance becomes trivial and information leaked may enable targeted attacks on downstream systems. The vulnerability is not a direct code execution or service disruption vector, but information disclosure of agent configurations can facilitate secondary attacks (e.g., prompt injection targeting identified agents, social engineering using exposed roles). No CISA KEV status or public proof-of-concept availability was provided; this is a discovery via vendor security advisory (GitHub GHSA), not confirmed active exploitation. For organizations running isolated or properly firewalled AgentOS deployments, risk is lower; for cloud-exposed or multi-tenant scenarios, the lack of authentication is a critical security posture deficiency. |
| Exploit ScenarioDerived | An attacker scans for internet-exposed AgentOS instances (default binding to 0.0.0.0 makes them discoverable). Upon finding an instance, the attacker sends an unauthenticated HTTP GET request to /api/agents and receives a JSON response listing all agent names, roles, and the first 100 characters of their system instructions. The attacker uses this reconnaissance to identify high-value agents (e.g., 'financial-advisor', 'internal-api-gateway') and crafts prompt injection payloads or social engineering strategies targeted at those specific agents' roles. No authentication credential is required; network access alone is sufficient. While no public proof-of-concept exploit code was identified, the attack is trivial to execute given the simplicity of HTTP enumeration. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 09, 2026
PraisonAI AgentOS prior to version 4.5.128 exposes agent metadata including names, roles, and system instruction snippets via an unauthenticated GET /api/agents endpoint accessible from any network origin due to missing authentication middleware and permissive CORS defaults. This information disclosure vulnerability allows remote attackers to enumerate agent configurations without credentials, potentially revealing sensitive operational details that could inform social engineering or reconnaissance attacks against multi-agent deployments.
RemediationAI
Vendor-released patch: PraisonAI 4.5.128. Upgrade immediately to version 4.5.128 or later to obtain the fix for the authentication and authorization defects in the AgentOS API. Immediate workarounds prior to patching include: restrict network access to the AgentOS deployment by implementing firewall rules to limit /api/agents endpoint access to trusted internal networks only, configure CORS to restrict allow_origins to known trusted domains instead of ["*"], and deploy API authentication middleware (API keys, OAuth2, or similar) in front of the AgentOS application to enforce access control. Refer to the GitHub security advisory at https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-pm96-6xpr-978x for detailed remediation guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in pypi
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
PraisonAI is a FastAPI-based multi-agent orchestration platform. The vulnerability stems from inadequate API security posture: the AgentOS application lacks authentication middleware for the /api/agents endpoint, performs no API key validation, and deploys with CORS allow_origins set to the wildcard ["*"] and host bound to 0.0.0.0 (all interfaces). This configuration, combined with no access control checks, allows any unauthenticated HTTP client to retrieve agent configuration metadata. The root cause (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) reflects a design flaw where sensitive operational metadata is exposed without identity verification or authorization checks. The first 100 characters of system instructions may leak prompt injection vectors, role descriptions, or internal operational context that should remain confidential.
Know when Praisonai gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
2DescriptionGitHub Advisory
PraisonAI is a multi-agent teams system. Prior to 4.5.128, 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. This vulnerability is fixed in 4.5.128.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
PraisonAI's TypeScript MCP server (npm package `praisonai`, versions 1.5.0 through 1.7.1) exposes an HTTP JSON-RPC trans
WebSocket origin-validation bypass in PraisonAI's Browser Server (praisonai/browser/server.py) before 4.6.58 lets an att
PraisonAI's `praisonai serve` subsystem (agents and unified modes) accepts an `--api-key` CLI flag that is parsed but ne
Unauthenticated remote agent invocation in PraisonAI versions 4.6.34 through 4.6.57 allows any network-reachable caller
SSRF protection bypass in PraisonAI's praisonaiagents library (all versions before 1.6.58) lets low-privileged users rou
Authentication fail-open in PraisonAI's Recipe HTTP server allows unauthenticated remote attackers to invoke recipe exec
Authentication bypass in PraisonAI's AgentServer component exposes all routes - /publish, /events, /info, /health - to u
Arbitrary Python code execution in PraisonAI's workflow include feature allows an attacker who controls a local recipe d
Server-side request forgery in PraisonAI's web_crawl() function (versions 1.5.128-1.6.57) allows an attacker who can inf
Cross-site request forgery against the PraisonAI MCP HTTP-stream transport allows unauthenticated remote attackers to ex
Remote unauthenticated access to PraisonAI's legacy Flask API server allows attackers to execute configured agent workfl
Path traversal in praisonaiagents prior to 1.6.58 allows a low-privileged caller to write arbitrary JSON files to any pr
EUVD-2026-21172
GHSA-pm96-6xpr-978x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB