CVE-2026-34937
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 is a multi-agent teams system. Prior to version 1.5.90, run_python() in praisonai constructs a shell command string by interpolating user-controlled code into python3 -c "<code>" and passing it to subprocess.run(..., shell=True). The escaping logic only handles \ and ", leaving $() and backtick substitutions unescaped, allowing arbitrary OS command execution before Python is invoked. This issue has been patched in version 1.5.90.
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 confidenceThe run_python() function in PraisonAI constructs a shell command by interpolating user-controlled code into 'python3 -c "<code>"' and passing it to subprocess.run(..., shell=True). The escaping logic only handles backslash and double-quote characters, leaving command substitution syntax ($() and backticks) unescaped, enabling arbitrary OS command execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.5.90CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Identify PraisonAI installation and versionRun 'pip show praisonaiagents' or check your package manager to find the installed version of PraisonAIAffected if The installed version is lower than 1.5.90 (e.g., 1.5.89, 1.5.0, etc.)
-
Locate the run_python() function in your codebaseSearch for 'def run_python' in your PraisonAI source files or installed package to find the vulnerable functionAffected if The run_python() function exists in your environment (the function is present)
-
Inspect subprocess.run usage within run_python()Open the run_python() function source and verify if subprocess.run is called with shell=True and string interpolation of user inputAffected if subprocess.run is called with shell=True and user-controlled variables are directly interpolated into the command string
-
Check for unescaped command substitution charactersExamine the escaping logic in run_python() - look for how \ and " are handled versus $() and backticksAffected if The escaping logic only handles \ and " characters, leaving $() or backticks unescaped
You are affected if PraisonAI Praisonaiagents version is below 1.5.90 AND the run_python() function uses subprocess.run with shell=True and incomplete escaping of command substitution characters.
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 · scoped1.5.90
Upgrade to PraisonAI version 1.5.90 or later, which contains the patch for this vulnerability.
1.5.90
- Check the current installed version of praisonaiagents by running: pip show praisonaiagents or pip list | grep praisonai
- Upgrade praisonaiagents to version 1.5.90 or later using: pip install --upgrade praisonaiagents==1.5.90
- Verify the upgrade was successful by running: pip show praisonaiagents and confirming the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34937 — 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-34937 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