Is CVE-2026-61426 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-61426 being exploited in the wild.

How severe is CVE-2026-61426?

High severity, with a CVSS score of 8.6, published 11 July 2026.

Which products and versions are affected?

praisonai (npm) < 1.7.3, SEMVER:introduced=0,fixed=1.7.3.

Is there a fix for CVE-2026-61426?

Yes. praisonai (npm): upgrade to 1.7.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-61426 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-61426?

Check whether you run praisonai (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-61426: MervinPraison PraisonAI missing authentication in AgentOS API

Q: Which products and versions are affected?

praisonai (npm) < 1.7.3, SEMVER:introduced=0,fixed=1.7.3.

Q: Is there a fix for CVE-2026-61426?

Yes. praisonai (npm): upgrade to 1.7.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-61426 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-61426?

Check whether you run praisonai (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-61426 · Severity: high · CVSS 8.6 · Published 2026-07-11

PraisonAI, a framework for managing AI agents, contains a security flaw where its server component is accessible to anyone on the network by default without a password. An unauthorized person could connect to the service to steal sensitive AI system prompts or interact with the AI agents, potentially leading to unauthorized data access or unexpected financial costs from AI usage. This issue affects users who deployed the software using the default settings in versions prior to 1.7.3.

Technologies: praisonai (npm). Vendors: npm.

Quick answers

Is CVE-2026-61426 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-61426 being exploited in the wild.
How severe is CVE-2026-61426?: High severity, with a CVSS score of 8.6, published 11 July 2026.
Which products and versions are affected?: praisonai (npm) < 1.7.3, SEMVER:introduced=0,fixed=1.7.3.
Is there a fix for CVE-2026-61426?: Yes. praisonai (npm): upgrade to 1.7.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-61426 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-61426?: Check whether you run praisonai (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

praisonai (npm): upgrade to 1.7.3 or later
```
npm install praisonai@1.7.3
```

Technical details

The AgentOS server in the PraisonAI TypeScript/npm package implements an insecure default configuration in `src/praisonai-ts/src/os/config.ts`. By default, the server binds to 0.0.0.0, sets an empty API key, and enables wildcard CORS with credentials. The authentication middleware in `src/praisonai-ts/src/os/agentos.ts` is only registered if a non-empty API key is provided, leading to a 'fail-open' state when no key is configured. Remote unauthenticated attackers can access `GET /api/agents` to leak system prompts and `POST /api/chat` to trigger agent execution. The vulnerability is addressed in version 1.7.3 by requiring authentication and changing default binding behavior.

Affected products

MervinPraison PraisonAI < 1.7.3

Identifiers

CVE-2026-61426
GHSA-6wjp-v33h-5cvq

Timeline

2026-06-25: advisory: GitHub Security Advisory published
2026-07-11: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.