CVE-2026-57140: Praisonai Npm PraisonAI AgentOS Exposes Unauthenticated Vulnerability
CRITICALCVE-2026-57140 is a CRITICAL (CVSS 9.4) npm praisonai agentos exposes unauthenticated vulnerability (CWE-306: Missing Authentication for Critical Function) affecting Praisonai libraries in the npm ecosystem. The issue involves npm praisonai agentos exposes unauthenticated agent listing and invocation. Remediation is available by upgrading affected packages to version 1.7.2.
CVE-2026-57140 at a Glance
Security Impact
CVSS: 9.4
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L).
How to Fix CVE-2026-57140
To remediate this vulnerability, upgrade all affected Praisonai dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install praisonai@1.7.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls praisonai
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-57140, inspect your project dependencies using npm:
npm ls praisonai
Analyze the terminal output to locate any version of Praisonai in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.7.2), your application is affected.
Note: The npm ls praisonai command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-306: Missing Authentication for Critical Function, where the product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. In Praisonai, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-57140 Affected Praisonai Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
praisonai
|
npm |
≥ 1.6.0
< 1.7.2
|
1.7.2
|
References
Frequently Asked Questions
What is CVE-2026-57140?
Which Praisonai versions are affected?
What version fixes CVE-2026-57140?
Is praisonai affected?
What is the CVSS score of CVE-2026-57140?
What CWE is associated with CVE-2026-57140?
How can I check npm dependencies for CVE-2026-57140?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9752-mhqh-h34f",
"modified" : "2026-07-20T21:27:27Z",
"published" : "2026-06-18T14:26:42Z",
"aliases" : [ "CVE-2026-57140" ],
"summary" : "npm PraisonAI AgentOS exposes unauthenticated agent listing and invocation",
"details" : "## Summary\n\nThe published npm package `praisonai` ships a TypeScript `AgentOS` HTTP server that defaults to `host: \"0.0.0.0\"` and registers sensitive agent routes without any authentication or authorization middleware.\n\nWhen a developer starts `AgentOS`, a network attacker who can reach the service can:\n\n- read configured agent names, roles, and the first 100 characters of each agent's instructions through `GET /api/agents`; and\n- invoke the selected agent through `POST /api/chat` without credentials.\n\nThis is distinct from the existing Python/PyPI AgentOS and API-server advisories. The affected package here is `npm:praisonai`; the current published npm package is `1.7.1`, and the same TypeScript source is still present in refreshed `origin/main` at `v4.6.58`.\n\n## Technical Details\n\n`AgentOSConfig` exposes host, CORS, and API-prefix settings but no authentication token, auth mode, or authorization callback.\n\nRelevant current-head source:\n\n```text\nsrc/praisonai-ts/src/os/config.ts\n 26: host?: string; // default: \"0.0.0.0\"\n 35: corsOrigins?: string[]; // default: [\"*\"]\n 66: export const DEFAULT_AGENTOS_CONFIG = {\n 68: host: '0.0.0.0',\n 71: corsOrigins: ['*'],\n```\n\n`AgentOS._createApp()` registers JSON parsing and CORS handling, then immediately registers routes. There is no middleware between body parsing and route registration that validates an API key, bearer token, session, origin-bound secret, or any other credential.\n\nRelevant current-head source:\n\n```text\nsrc/praisonai-ts/src/os/agentos.ts\n 179: app.use(express.json());\n 182: // Add CORS middleware\n 204: // Register routes\n 205: this._registerRoutes(app);\n```\n\nThe sensitive routes are then exposed:\n\n```text\nsrc/praisonai-ts/src/os/agentos.ts\n 235: app.get(`${apiPrefix}/agents`, ...)\n 240: instructions: agent.instructions ? ... : null\n 250: app.post(`${apiPrefix}/chat`, ...)\n 273: const response = await agent.chat(message);\n 331: const host = options.host || this.config.host;\n 338: this._server = app.listen(port, host, ...)\n```\n\nBecause the default host is `0.0.0.0`, `await app.serve({ port: 8000 })` listens on all interfaces unless the developer explicitly overrides `host`.\n\n### Why This Is Not Intended Behavior\n\nPraisonAI's official TypeScript documentation describes the npm package as a production-ready multi-agent framework and directs users to install it with `npm install praisonai`.\n\nPraisonAI's security documentation says security reports should include affected versions, impact, reproduction steps, and a suggested fix, and states that GitHub Security Advisories are the preferred reporting method. The same security page also documents a prior hardening change where API servers were changed to require authentication by default and bind to `127.0.0.1` instead of `0.0.0.0`.\n\nThe TypeScript npm `AgentOS` implementation still does the opposite:\n\n- default bind address is `0.0.0.0`;\n- no auth config exists in `AgentOSConfig`;\n- `/api/agents` discloses agent metadata and instruction prefixes; and\n- `/api/chat` invokes `agent.chat(message)` directly.\n\nThe patched-control branch in the PoV confirms that adding a pre-route bearer-token middleware makes the same unauthenticated requests fail with `401`.\n\n## PoV\n\nThe PoV installs the published npm package in a temporary project, starts `AgentOS` on `127.0.0.1` with a mock agent, and sends loopback HTTP requests. It does not call any LLM provider or external service after package installation.\n\nRun from a local reproduction checkout:\n\n```fish\nnode poc/pov_poc.js 1.7.1\n```\n\nObserved result:\n\n```json\n{\n \"version\": \"1.7.1\",\n \"defaultHost\": \"0.0.0.0\",\n \"agentsStatus\": 200,\n \"agentsBody\": {\n \"agents\": [\n {\n \"name\": \"finance-admin\",\n \"role\": \"internal finance operations\",\n \"instructions\": \"poc SECRET: refund-wire-tool may alter customer balances\"\n }\n ]\n },\n \"chatStatus\": 200,\n \"chatBody\": {\n \"response\": \"agent-invoked:transfer-check\",\n \"agent_name\": \"finance-admin\"\n },\n \"invokedMessages\": [\n \"transfer-check\"\n ]\n}\n```\n\nNo `Authorization` header is sent in the vulnerable requests.\n\nThe PoV also applies a minimal local-only auth middleware patch to the temporary installed copy and reruns the same requests as a control:\n\n```json\n{\n \"patchedNoAuthAgents\": 401,\n \"patchedNoAuthChat\": 401,\n \"patchedWithAuthAgents\": 200,\n \"patchedWithAuthChat\": 200\n}\n```\n\nThis control demonstrates that the PoV is exercising the missing authentication boundary, not an artifact of the mock agent.\n\n## PoC\n\nThe PoV section above contains the local reproduction command, input, and decisive output.\n\n## Impact\n\nAn attacker who can reach a running TypeScript `AgentOS` server can invoke configured agents without credentials. Real impact depends on the deployed agent, but PraisonAI agents may have access to tools, memory, workflow state, external APIs, credentials in process environment, and business data. Unauthorized prompt injection through `/api/chat` can therefore affect confidentiality and integrity of downstream systems reachable by the configured agent.\n\n`GET /api/agents` also discloses agent names, roles, and instruction prefixes, which can reveal internal workflow details and help tailor prompts against the exposed agent.\n\nThis report does not claim arbitrary code execution by default. If the deployed agent has code, file, browser, MCP, or business-operation tools, the unauthenticated invocation endpoint can become the entry point for those tool-side effects.\n\n### Severity\n\nSuggested severity: Critical.\n\nRationale:\n\n- `AV`: the vulnerable component is an HTTP service and defaults to all-interface binding.\n- `AC`: exploitation is a direct HTTP request.\n- `PR`: no credentials are required.\n- `UI`: no user interaction is required after the server is running.\n- `S`: impact is within the vulnerable service and the configured agent's authority.\n- `C`: `/api/agents` exposes instructions and `/api/chat` can elicit data reachable by the agent.\n- `I`: `/api/chat` lets unauthenticated callers drive agent/tool actions.\n- `A`: unauthorized callers can consume model/API/server resources.\n\n## Suggested Fix\n\nRecommended minimum fix:\n\n1. Add an authentication configuration to TypeScript `AgentOSConfig`, for example `authToken`, `authRequired`, or an `authorize(req)` callback.\n2. Default externally reachable servers to authenticated. Prefer fail-closed behavior when `host` is not loopback.\n3. Change the default host from `0.0.0.0` to `127.0.0.1`, matching the documented Python API-server hardening.\n4. Register auth middleware before all non-health routes, including `/`, `/api/agents`, `/api/chat`, `/api/teams`, and `/api/flows`.\n5. Avoid returning agent instruction text from `/api/agents` unless the caller is authenticated and explicitly authorized.\n6. Add regression tests that:\n - unauthenticated `GET /api/agents` returns `401`;\n - unauthenticated `POST /api/chat` returns `401` and does not call `agent.chat`;\n - authenticated requests still work;\n - default `serve({ port })` binds to loopback or fails closed when auth is not configured.\n\n## Affected Package/Versions\n\n- Repository: `MervinPraison/PraisonAI`\n- Ecosystem: `npm`\n- Package: `praisonai`\n- Current npm version: `1.7.1`\n- Component: `src/praisonai-ts/src/os/agentos.ts`\n- Config component: `src/praisonai-ts/src/os/config.ts`\n- Refreshed repo head checked: `1ad58ca02975ff1398efeda694ea2ab78f20cf3e` (`v4.6.58`)\n\nConfirmed affected npm versions:\n\n```text\n>= 1.6.0, <= 1.7.1\n```\n\nBoundary:\n\n```text\n<= 1.5.4 did not ship dist/os/agentos.js in the npm tarball.\n```\n\nNo fixed npm version is known at the time of this report.\n\n### Version Sweep\n\nThe included sweep downloads npm tarballs and checks for the shipped `dist/os` implementation:\n\n```fish\nnode poc/version_sweep_poc.js\n```\n\nAffected rows:\n\n```text\nversion has_agentos default_host_0_0_0_0 has_api_agents_instructions has_api_chat_agent_invocation has_401_unauthorized_guard mentions_authorization_header\n1.6.0 true true true true false true\n1.7.0 true true true true false true\n1.7.1 true true true true false true\n```\n\nEarlier npm versions through `1.5.4` did not ship `dist/os/agentos.js`.\n\n`mentions_authorization_header` is true because CORS allows the `Authorization` header. The sweep separately verifies there is no 401/Unauthorized route guard.\n\n## Advisory History\n\nChecked:\n\n- public GitHub advisories for `MervinPraison/PraisonAI`;\n- private/triage advisories visible to this account; and\n- visible PraisonAI advisories and prior reports.\n\nNo public or private advisory row in that data targets `ecosystem: npm` / `package: praisonai`.\n\nClosest related advisories are Python/PyPI-scoped and do not cover the npm TypeScript package:\n\n- `GHSA-pm96-6xpr-978x`: PyPI `praisonai`, unauthenticated information disclosure via Python AgentOS `/api/agents`, affected `<= 4.5.120`.\n- `GHSA-892r-p3jq-jp24`: PyPI `praisonai`, Python AgentOS unauthenticated remote agent invocation, affected `>= 4.2.1, <= 4.6.57`.\n- `GHSA-6rmh-7xcm-cpxj`: PyPI `praisonai`, generated legacy API server authentication disabled by default, affected `>= 2.5.6, <= 4.6.33`.\n- `GHSA-r7v3-x45f-g7hp` / `GHSA-7ww9-85pg-cv4x`: PyPI `praisonai serve agents --api-key` ignored.\n\nThis report should be tracked separately because it affects the npm package and the TypeScript implementation under `src/praisonai-ts`, with npm affected range `>= 1.6.0, <= 1.7.1`.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "praisonai"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.6.0"
}, {
"fixed" : "1.7.2"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.7.1"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-9752-mhqh-h34f"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/MervinPraison/PraisonAI"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-306" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-18T14:26:42Z",
"nvd_published_at" : null
}
}