CVE-2026-57118

CVE-2026-57118 is a critical-severity missing authentication for critical function vulnerability in praisonaiagents (pip), affecting versions < 1.6.59. It is fixed in 1.6.59.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

PraisonAI AgentTeam.launch exposes unauthenticated remote agent listing and invocation endpoints

Impact

If an operator follows the documented remote-server pattern and exposes an AgentTeam.launch() server on a reachable interface, any network client can invoke the deployed agents without credentials.

Depending on the deployed agents, an unauthenticated caller may be able to:

  • enumerate available agent IDs and names through GET /{path}/list;
  • trigger model/API spend by repeatedly invoking agents;
  • drive agents connected to local tools, internal APIs, SaaS integrations, browsers, files, or workflow actions;
  • trigger side effects through per-agent endpoints even if the operator expected only the team endpoint to be used;
  • access responses generated from connected private context, memory, or knowledge sources.

The impact is deployment-dependent, but the missing access control is in the framework's advertised network server path rather than in user application code.

A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.

CVE-2026-57118 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.6.59); upgrading removes the vulnerable code path.

Affected versions

praisonaiagents (< 1.6.59)

Security releases

praisonaiagents → 1.6.59 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Recommended approach:

  1. Add a shared authentication helper for all network-facing agent invocation servers.
  2. Make AgentTeam.launch() fail closed for non-loopback binds unless a token/API key is configured.
  3. Require Authorization: Bearer <token> or an explicit documented API-key header for POST /{path}, GET /{path}/list, and POST /{path}/{agent_id}.
  4. Default AgentTeam.launch() to host="127.0.0.1" unless an explicit unsafe/remote option plus auth is configured.
  5. Add regression tests proving:
    • no token returns 401;
    • wrong token returns 403;
    • correct token can list agents;
    • correct token can invoke the team endpoint;
    • correct token can invoke the per-agent endpoint;
    • external bind without auth fails at startup.

If unauthenticated local development remains supported, require loopback binding and a loud explicit unsafe opt-out for externally bound unauthenticated servers.

Frequently Asked Questions

  1. What is CVE-2026-57118? CVE-2026-57118 is a critical-severity missing authentication for critical function vulnerability in praisonaiagents (pip), affecting versions < 1.6.59. It is fixed in 1.6.59. A critical operation is accessible without requiring any authentication.
  2. How severe is CVE-2026-57118? CVE-2026-57118 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of praisonaiagents are affected by CVE-2026-57118? praisonaiagents (pip) versions < 1.6.59 is affected.
  4. Is there a fix for CVE-2026-57118? Yes. CVE-2026-57118 is fixed in 1.6.59. Upgrade to this version or later.
  5. Is CVE-2026-57118 exploitable, and should I be worried? Whether CVE-2026-57118 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2026-57118 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2026-57118? Upgrade praisonaiagents to 1.6.59 or later.

Other vulnerabilities in praisonaiagents

Stop the waste.
Protect your environment with Kodem.