dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-61427

HIGH · 7.3 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 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 4.6.78 exposes the MCP HTTP-stream transport without authentication by default: the CLI --api-key option defaults to None, and the server only enforces Authorization/Bearer checks when an API key is configured. When an operator runs 'praisonai mcp serve --transport http-stream' without an API key, an unauthenticated client (no Authorization header, and no Origin header, which is also permitted) can initialize a session, enumerate the available tools (tools/list), and invoke tools (tools/call). Additionally, the dispatcher forwards tool-call arguments to handlers without validating them against the advertised inputSchema. The server binds to 127.0.0.1 by default, so remote exploitation requires the operator to bind to a network-accessible address (e.g., --host 0.0.0.0).

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 4.6.78 has a default authentication bypass in its MCP HTTP-stream transport: the --api-key CLI option defaults to None, and the server skips Authorization/Bearer checks entirely when no key is configured. This allows any unauthenticated client to initialize sessions, enumerate tools via tools/list, and invoke arbitrary tools via tools/call. Additionally, the dispatcher forwards tool-call arguments without validating them against the advertised inputSchema. The server binds to 127.0.0.1 by default, so remote exploitation requires the operator to bind to a network-accessible address.

MitigationUpgrade to PraisonAI 4.6.78 or later and always configure a strong API key using --api-key when running the MCP server. Avoid binding to 0.0.0.0 unless network access is explicitly required, and implement inputSchema validation for tool-call arguments.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 for the installed version number
    Affected if Version is lower than 4.6.78 (e.g., 4.6.77, 4.6.70, etc.)
  2. Inspect MCP server startup command
    Review the command or script used to launch the PraisonAI MCP server; look for the --api-key argument and its value
    Affected if --api-key is not specified, is set to None, or is omitted entirely from the startup command
  3. Test unauthenticated access to tools/list
    Send an HTTP GET request to the MCP server endpoint (e.g., http://127.0.0.1:<port>/tools/list) without including an Authorization or Bearer token header
    Affected if The server returns a list of available tools without rejecting the request with a 401 or 403 status
  4. Test unauthenticated access to tools/call
    Send an HTTP POST request to the MCP server endpoint (e.g., http://127.0.0.1:<port>/tools/call) with a tool invocation payload, without any Authorization or Bearer token header
    Affected if The server executes the tool call and returns a response without rejecting the request with a 401 or 403 status
  5. Check server binding configuration
    Inspect the startup configuration or logs to determine which address the MCP server binds to (127.0.0.1 vs 0.0.0.0 or other network address)
    Affected if The server is bound to 0.0.0.0 or any non-loopback address, making it accessible from other machines on the network

You are affected if your PraisonAI version is before 4.6.78 AND the MCP server runs without an explicit --api-key configured, allowing unauthenticated access to tool listing and invocation, especially if bound to a network-accessible address.

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 4.6.78 or later and always configure a strong API key using --api-key when running the MCP server. Avoid binding to 0.0.0.0 unless network access is explicitly required, and implement inputSchema validation for tool-call arguments.

Recommended fix Moderate confidence

Upgrade to PraisonAI 4.6.78 or later

  1. Upgrade PraisonAI to version 4.6.78 or later using pip: pip install --upgrade praisonai
  2. Verify the upgrade was successful: pip show praisonai
  3. If using the MCP server, ensure you configure an API key using the --api-key option when starting the server
  4. After upgrade, test that authentication is properly enforced on the MCP HTTP-stream transport

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61427 — 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-61427 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