CVE-2026-34938
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, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. 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 confidencePraisonAI's execute_code() function contains a sandbox bypass vulnerability where a str subclass with an overridden startswith() method can be passed to the _safe_getattr wrapper, circumventing the three-layer sandbox protection and allowing arbitrary OS command execution on the host.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed PraisonAI versionRun 'pip show praisonaiagents' or 'pip list | grep -i praison' to see the installed versionAffected if The version shown is below 1.5.90
-
Locate the execute_code functionSearch for 'execute_code' in the codebase: grep -r 'execute_code' . --include='*.py' or check if the function is imported/used in your projectAffected if The execute_code function from PraisonAI is being called in your code
-
Inspect _safe_getattr implementationFind the _safe_getattr function in the PraisonAI package: python -c "import praisonaiagents; import os; print(os.path.dirname(praisonaiagents.__file__))" then look for _safe_getattr in the sourceAffected if The _safe_getattr wrapper does not include defenses against str subclass override of startswith()
-
Check sandbox configurationLook for sandbox-related config or code that uses execute_code - check if code execution is enabled or if external code execution is permitted in your deploymentAffected if The sandbox allows user-supplied code to reach execute_code() without additional validation layers
You are affected if you have PraisonAI agents installed with a version below 1.5.90 and your application uses the execute_code function with user-controlled input that reaches the _safe_getattr wrapper.
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
- Upgrade praisonai-agents to version 1.5.90 or later using pip: pip install praisonai-agents>=1.5.90
- Verify the upgrade was successful by checking the installed version: pip show praisonai-agents
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34938 — 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-34938 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