CVE-2026-61444
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 · uneditedPraisonAI versions before 4.6.78 contain a code injection vulnerability in deploy/api.py where the agents_file parameter is directly interpolated into an f-string without sanitization. Attackers can inject arbitrary Python code that executes when the generated server code runs via subprocess.Popen().
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 confidencePraisonAI before version 4.6.78 contains a critical code injection vulnerability in deploy/api.py where the agents_file parameter is directly interpolated into an f-string without any sanitization. This allows attackers to inject arbitrary Python code that executes when the generated server code runs via subprocess.Popen().
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed PraisonAI versionRun 'pip show praisonai' or 'pip list | grep praisonai' to find the installed version numberAffected if The installed version is lower than 4.6.78 (e.g., 4.6.77, 4.6.76, etc.)
-
Locate the vulnerable fileFind deploy/api.py in the PraisonAI installation directory (typically in site-packages/praisonai/deploy/ or the source repository)Affected if The file deploy/api.py exists in the installation
-
Inspect the code for the vulnerable patternOpen deploy/api.py and search for f-string usage of 'agents_file' parameter, particularly around subprocess.Popen() callsAffected if The code contains an f-string that directly interpolates the agents_file parameter without any sanitization or validation function applied to it
-
Check if the deployment API is in useIdentify if the application exposes any API endpoint that accepts an agents_file parameter and invokes the vulnerable code pathAffected if The API endpoint that uses the agents_file parameter from deploy/api.py is accessible and can accept user-supplied input
You are affected if PraisonAI version is below 4.6.78 AND the deploy/api.py file contains unsanitized f-string interpolation of agents_file into subprocess execution.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to PraisonAI version 4.6.78 or later which includes proper input validation and sanitization for the agents_file parameter before interpolation.
PraisonAI 4.6.78 or later
- Upgrade PraisonAI to version 4.6.78 or later using pip: pip install --upgrade PraisonAI
- Verify the upgrade was successful by checking the installed version: pip show PraisonAI
- If using a requirements.txt or poetry.lock file, update the version constraint to require PraisonAI>=4.6.78 and regenerate dependencies
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-61444 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-61444 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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