dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-61435

HIGH · 8.2 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 →
91/100
Remediation priority · Urgent
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 contains an authentication bypass in the Call API agent invocation endpoints (src/praisonai/praisonai/api/agent_invoke.py) when PRAISONAI_CALL_AUTH=disabled is configured. The safeguard intended to restrict the disabled-auth opt-out to localhost binding derives the bind host from request.url.hostname, which is taken from the client-controlled HTTP Host header. A remote, unauthenticated attacker who can reach the service over the network can send a spoofed 'Host: 127.0.0.1' header to bypass the localhost-only restriction and list (GET /api/v1/agents) and invoke (POST /api/v1/agents/{agent_id}/invoke) registered 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 · moderate confidence

PraisonAI before 4.6.78 has an authentication bypass where the application validates localhost-only access by deriving the bind host from request.url.hostname, which is sourced from the client-controlled HTTP Host header. An unauthenticated remote attacker can send a spoofed 'Host: 127.0.0.1' header to bypass this check and access the /api/v1/agents listing and /api/v1/agents/{agent_id}/invoke endpoints without authentication.

MitigationUpgrade to PraisonAI 4.6.78 or later; ensure proper authentication is enabled and do not use client-provided headers for security-critical decisions like localhost validation.

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
High
Availability
None

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

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. Identify installed PraisonAI version
    Run 'pip show praisonai' or 'pip list | grep -i praisonai' to see the installed version. Alternatively, import praisonai and check its __version__ attribute if accessible.
    Affected if The installed version is before 4.6.78 (e.g., 4.6.77, 4.6.0, etc.)
  2. Verify network exposure of the service
    Check the startup configuration or command-line arguments to see what address the application binds to. Look for 0.0.0.0 or public IP bindings versus 127.0.0.1/localhost-only binding.
    Affected if The service is bound to 0.0.0.0 or a public IP address, making it accessible from untrusted networks
  3. Test for Host header injection on the agents endpoint
    Send a GET request to /api/v1/agents with a spoofed 'Host: 127.0.0.1' header (e.g., curl -H 'Host: 127.0.0.1' http://<actual-server-ip>:<port>/api/v1/agents). No authentication should be required for a successful bypass.
    Affected if The request returns agent data or a 200 OK response instead of a 401/403 authentication error when using a spoofed Host header from a remote IP
  4. Test the agent invoke endpoint for the same bypass
    Send a POST request to /api/v1/agents/<agent_id>/invoke with 'Host: 127.0.0.1' header and observe if the call executes without authentication.
    Affected if The invoke endpoint processes the request and returns success or data without requiring authentication when accessed remotely with a spoofed Host header

You are affected if running PraisonAI version before 4.6.78 AND the service is network-accessible AND the /api/v1/agents endpoints respond without authentication when a 'Host: 127.0.0.1' header is sent from a non-localhost client.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to PraisonAI 4.6.78 or later; ensure proper authentication is enabled and do not use client-provided headers for security-critical decisions like localhost validation.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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