dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-61426

HIGH · 8.6 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
PraisonAI before 1.7.3 contains an insecure default configuration that binds to all interfaces with no API key requirement and wildcard CORS. Unauthenticated attackers can call GET /api/agents to read agent instructions and system prompts, or POST /api/chat to invoke agents without authentication.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

PraisonAI before version 1.7.3 ships with an insecure default configuration that binds the web service to all network interfaces (0.0.0.0) without requiring API key authentication and with wildcard CORS headers enabled. This allows any unauthenticated remote attacker to access GET /api/agents (reading sensitive agent instructions and system prompts) and POST /api/chat (executing agent actions) without any credentials.

MitigationUpgrade to PraisonAI 1.7.3 or later, configure the service to bind only to localhost or trusted networks, enable and enforce API key authentication, and restrict CORS to specific trusted origins.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed PraisonAI version
    Run 'pip show praisonai' or check your package manager to identify the installed version number
    Affected if Version is before 1.7.3
  2. Verify service binding configuration
    Inspect the startup configuration, environment variables, or config file for the host binding setting. Look for '0.0.0.0' or 'bind' settings
    Affected if Service is bound to 0.0.0.0 (all network interfaces) instead of localhost or a specific trusted IP
  3. Confirm API key authentication is enforced
    Review your configuration files and API endpoint code to verify that authentication is required for /api/agents and /api/chat endpoints
    Affected if No API key or authentication mechanism is configured or enforced on these endpoints
  4. Inspect CORS policy configuration
    Examine your CORS configuration settings for allowed origins
    Affected if CORS is set to allow wildcard (*) or includes untrusted origins

You are affected if running PraisonAI version before 1.7.3 with default configuration (bound to 0.0.0.0, no API key auth, and wildcard CORS), as this exposes agent instructions and chat execution to unauthenticated remote attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to PraisonAI 1.7.3 or later, configure the service to bind only to localhost or trusted networks, enable and enforce API key authentication, and restrict CORS to specific trusted origins.

Recommended fix High confidence

1.7.3 or later

  1. Upgrade PraisonAI to version 1.7.3 or later to remediate the insecure default configuration vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61426 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-61426 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data