CVE-2026-61434
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 an allowlist bypass vulnerability in shell command execution that allows attackers to execute restricted commands via find's built-in -exec, -execdir, and -delete actions. Attackers can craft find commands with these built-in actions to read blocked files, delete files, or execute non-allowlisted binaries without triggering shell metacharacter filters.
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 4.6.78 has an allowlist bypass in its shell command execution feature. Attackers can use find's built-in actions (-exec, -execdir, -delete) to bypass shell metacharacter filters and perform unauthorized operations including reading blocked files, deleting files, and executing non-allowlisted binaries.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check installed PraisonAI versionRun 'pip show praisonai' or check the package version in your Python environmentAffected if The installed version is before 4.6.78 (e.g., 4.6.77, 4.6.0, etc.)
-
Verify shell command execution feature is enabledInspect PraisonAI configuration files or environment settings for shell command execution settings, typically found in config files or environment variables controlling command executionAffected if Shell command execution feature is enabled and uses an allowlist to filter commands
-
Confirm find utility is accessibleRun 'which find' or 'find --version' to verify the find command is available on the systemAffected if The find utility is installed and accessible to the PraisonAI process
-
Check for shell metacharacter filteringReview PraisonAI source code or configuration for input validation logic that filters shell metacharacters, looking for patterns that block characters like ; | & $ or command substitutionAffected if Shell metacharacter filtering is present but does NOT explicitly block find built-in actions (-exec, -execdir, -delete)
-
Test allowlist bypass potentialIf you have access to the shell command interface, observe whether commands using find -exec, find -execdir, or find -delete can execute operations on files not in the allowlistAffected if Find built-in actions can bypass the command allowlist to access blocked files, delete files, or run non-allowlisted binaries
You are affected if PraisonAI version is before 4.6.78 AND the shell command execution feature with allowlist filtering is enabled, as attackers can use find built-in actions to bypass the filters.
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.
From vendor dataUpgrade to PraisonAI version 4.6.78 or later. Additionally, implement stricter input validation that blocks find command built-ins and consider applying command-level sandboxing.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-61434 — 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-61434 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