dbcve.org
CWE-1188Weakness · CWE-1188

CVE-2026-61439

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 versions before 4.6.78 contain a prompt injection defense misconfiguration where the block threshold defaults to CRITICAL severity, allowing HIGH-level threats to pass through unblocked. Attackers can submit single-vector prompt injection attacks such as instruction overrides or financial manipulation that trigger HIGH severity detection but are logged without blocking, enabling system prompt extraction and unauthorized tool invocations.

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 versions before 4.6.78 have a prompt injection defense misconfiguration where the block threshold defaults to CRITICAL severity, causing HIGH severity threats to be logged but not blocked. Attackers can submit prompt injection attacks (instruction overrides, financial manipulation) that bypass the defense, enabling system prompt extraction and unauthorized tool invocations.

MitigationLower the prompt injection block threshold from CRITICAL to include HIGH severity threats, or upgrade to version 4.6.78 or later which addresses this misconfiguration.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 PraisonAI installation and version
    Run 'pip show praisonai' or check your package manager to retrieve the installed version number
    Affected if Version is below 4.6.78
  2. Locate prompt injection configuration
    Search for configuration files named 'prompt_injection', 'security', or similar in the PraisonAI install directory or user config directory
    Affected if A configuration file exists that controls prompt injection defense settings
  3. Inspect block threshold setting
    Open the configuration file and look for a setting named 'block_threshold', 'threshold', or similar that controls which severity levels are blocked versus logged
    Affected if The threshold is set to 'CRITICAL' only, excluding 'HIGH' severity threats from being blocked
  4. Test defense behavior with HIGH severity prompts
    Submit a prompt injection test case of HIGH severity (instruction override, system prompt extraction attempt) and verify whether it is blocked or merely logged
    Affected if HIGH severity prompts are logged but not blocked, allowing the injection to execute

If PraisonAI is installed with a version before 4.6.78 and the prompt injection block threshold is configured to block only CRITICAL severity (not HIGH), the environment is vulnerable to the injection attacks described in this CVE.

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

Lower the prompt injection block threshold from CRITICAL to include HIGH severity threats, or upgrade to version 4.6.78 or later which addresses this misconfiguration.

Recommended fix Moderate confidence

PraisonAI version 4.6.78 or later

  1. Upgrade PraisonAI to version 4.6.78 or later to resolve the prompt injection defense misconfiguration
  2. After upgrading, verify that the block threshold is appropriately configured to block HIGH severity threats, not only CRITICAL severity threats
  3. Test the fix by submitting known HIGH-level prompt injection payloads to confirm they are now blocked rather than just logged
  4. Review system logs to confirm HIGH severity prompts are being blocked post-upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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