Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-57140 – Unauthenticated Agent Access / Sensitive Data Exposure & Invocation – PraisonAI (np

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-57140 is a critical missing-authentication vulnerability (CWE-306) in the AgentOS HTTP server shipped as part of the npm praisonai package, a multi-agent teams framework maintained by MervinPraison. Versions 1.6.0 up to and including 1.7.1 register the GET /api/agents and POST /api/chat endpoints without any authentication or authorization middleware, and the server defaults to binding on 0.0.0.0, making it reachable over the network. A remote, unauthenticated attacker can enumerate configured agents and invoke them directly, potentially reaching the agents’ underlying tools, memory, external API integrations, credentials, and workflow state. The issue carries a CVSS v3.1 base score of 9.4 (Critical).

Technical details

  • Root cause: The AgentOS implementation (src/praisonai-ts/src/os/agentos.ts) inherits a default host binding of 0.0.0.0 from src/praisonai-ts/src/os/config.ts, and registers the GET /api/agents and POST /api/chat routes without any authentication middleware placed in front of them.
  • Trigger conditions: Simply running an AgentOS instance on an affected version with default configuration exposes it to any network client that can reach the listening port — no credentials or prior access are required.
  • Attack vector: Network (AV:N), no privileges required (PR:N), no user interaction (UI:N), low attack complexity (AC:L).
  • Impact: An attacker can call GET /api/agents to obtain agent names, roles, and instruction prefixes, then use POST /api/chat to invoke a chosen agent. This can expose sensitive instruction/configuration data and allow the attacker to drive the agent’s connected tools, memory, external APIs, credentials, and workflow state — resulting in high confidentiality impact, high integrity impact, and low availability impact.

Affected software

  • Vendor: MervinPraison
  • Product: PraisonAI (npm praisonai package, TypeScript AgentOS component)
  • Affected versions: >= 1.6.0 and <= 1.7.1
  • Fixed version: 1.7.2 and later

Severity

  • CVSS v3.1 Base Score: 9.4 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Mitigation and recommended actions

  • Immediate: Upgrade the praisonai npm package to version 1.7.2 or later, which introduces an initial remediation for this issue.
  • If immediate patching is not possible:
    • Do not expose AgentOS instances directly to untrusted networks; bind the service to a loopback interface (127.0.0.1) rather than 0.0.0.0 where configuration allows.
    • Place the service behind a reverse proxy or gateway that enforces authentication/authorization before requests reach /api/agents and /api/chat.
    • Restrict network access to AgentOS ports using firewall rules or network segmentation, limiting reachability to trusted internal clients only.
    • Monitor for unexpected calls to /api/agents and /api/chat from unfamiliar sources as an indicator of exploitation attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge