dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-61447

CRITICAL · 10.0 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 →
100/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.6.78 contains a remote code execution vulnerability in CodeAgent._execute_python() that executes LLM-generated Python code without AST validation, import restrictions, or sandbox enforcement. Attackers can influence LLM output through prompt injection to exfiltrate all environment secrets and execute arbitrary code on the host system.

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

PraxonAI before 1.6.78 contains a critical RCE vulnerability in CodeAgent._execute_python() which executes LLM-generated Python code without any security controls. The function lacks AST validation, import restrictions, and sandbox enforcement, allowing attackers to use prompt injection to manipulate the LLM into generating malicious code that can exfiltrate environment secrets and execute arbitrary commands on the host.

MitigationUpgrade to PraisonAI version 1.6.78 or later which implements proper AST validation, import restrictions, and sandbox enforcement for LLM-generated code execution.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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 'pip list | grep -i praisonai' to retrieve the installed version number
    Affected if Version is lower than 1.6.78 (e.g., 1.6.77, 1.6.0, etc.)
  2. Verify CodeAgent module is present
    Check if the 'praisonai' package contains a 'CodeAgent' class or module by inspecting the installed package files or importing it in Python with 'from praisonai import CodeAgent'
    Affected if CodeAgent class exists and can be imported in the environment
  3. Confirm _execute_python method exists
    Inspect the CodeAgent class for the '_execute_python' method using 'dir()' or by examining the source code if accessible
    Affected if The _execute_python method is present in the CodeAgent implementation
  4. Check if CodeAgent is instantiated in your application
    Search your codebase for instances where CodeAgent is imported or instantiated, such as 'from praisonai import CodeAgent' or 'CodeAgent(...)' in your Python files
    Affected if Your application directly uses CodeAgent or leverages it indirectly through higher-level APIs that call this component

You are affected if PraisonAI version is below 1.6.78 AND your application uses the CodeAgent component with its _execute_python method, as this function allows unsandboxed execution of LLM-generated Python code.

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 version 1.6.78 or later which implements proper AST validation, import restrictions, and sandbox enforcement for LLM-generated code execution.

Recommended fix Moderate confidence

1.6.78 or later

  1. 1. Identify the current installed version of PraisonAI by checking your environment (e.g., pip show praisonai or requirements.txt)
  2. 2. Upgrade PraisonAI to version 1.6.78 or later using: pip install --upgrade praisonai
  3. 3. Verify the upgrade was successful by checking the installed version: pip show praisonai
  4. 4. Test that the application functions correctly after the upgrade
  5. 5. Review any configuration changes needed for CodeAgent to ensure AST validation or sandboxing is properly enabled in the new version

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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