dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-61443

HIGH · 8.1 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click 5 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 SkillTools.run_skill_script() that executes scripts without path containment validation. Attackers can supply absolute file paths to execute arbitrary scripts from any filesystem location, including those outside the intended working directory.

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

PraisonAI versions before 1.6.78 have a remote code execution vulnerability in the SkillTools.run_skill_script() function. The function accepts a script path parameter and executes it without validating that the path remains within an intended working directory. Attackers can provide absolute file paths (e.g., /etc/passwd, /tmp/malicious.sh) to cause execution of arbitrary scripts located anywhere on the filesystem, leading to full system compromise.

MitigationUpgrade PraisonAI to version 1.6.78 or later. As a temporary mitigation, restrict network access to the affected service and implement Web Application Firewall rules to block requests containing absolute paths or path traversal sequences.

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
None

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

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 if PraisonAI is installed
    Run 'pip show praisonai' or check your project's dependency file (requirements.txt, package.json, Pipfile.lock) for the praisonai package entry
    Affected if PraisonAI package is present in the environment
  2. Determine installed PraisonAI version
    Extract the version from the pip show output or dependency file and compare it to the affected range (versions before 1.6.78)
    Affected if Installed version is lower than 1.6.78 (e.g., 1.6.77, 1.5.0, etc.)
  3. Identify exposure of SkillTools.run_skill_script function
    Review application code, API endpoints, or web interface to determine if the SkillTools module and its run_skill_script method are exposed and callable by users or remote attackers
    Affected if The run_skill_script function is accessible via an API endpoint, web route, or other user-facing interface without additional authentication or sandboxing
  4. Assess network accessibility of the vulnerable service
    Check if the PraisonAI service is bound to a network interface (0.0.0.0) or exposed via reverse proxy, load balancer, or container networking
    Affected if The service is reachable from the network rather than localhost only

You are affected if PraisonAI version is below 1.6.78 AND the SkillTools.run_skill_script function is exposed to users or remote attackers.

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 PraisonAI to version 1.6.78 or later. As a temporary mitigation, restrict network access to the affected service and implement Web Application Firewall rules to block requests containing absolute paths or path traversal sequences.

Recommended fix Moderate confidence

PraisonAI 1.6.78 or later

  1. 1. Identify the current PraisonAI installation version by checking the installed package (e.g., `pip show praisonai` or `poetry show praisonai`)
  2. 2. If the installed version is before 1.6.78, upgrade to version 1.6.78 or later using the appropriate package manager: `pip install --upgrade praisonai` or `poetry update praisonai`
  3. 3. Verify the upgrade was successful by checking the new version: `pip show praisonai`
  4. 4. Test that the SkillTools.run_skill_script() function properly validates paths and restricts execution to intended directories
  5. 5. If running in production, review any custom integrations that use run_skill_script() to ensure compatibility with the updated version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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