Unrated

Path Traversal in PraisonAI GitHub Template Cache Handling

IdentifiersCVE-2026-57113CWE-22

CVE-2026-57113 is a path traversal vulnerability in PraisonAI's handling of GitHub template cache paths. Crafted GitHub template reference components are incorporated into filesystem paths without sufficient validation or confinement to the intended cache root. As a result, attacker-controlled template owner, repository, path, or ref values can cause path resolution outside the template cache directory. The flaw allows writing cache metadata outside the cache boundary and, when a normal cache entry already exists for the same owner/repository/template prefix, can also trigger deletion of an attacker-selected directory reachable by the PraisonAI process. The vulnerability affects workflows that load attacker-supplied or otherwise untrusted GitHub template URIs.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can lead to unauthorized modification of files and directories accessible to the PraisonAI process. An attacker may write cache metadata outside the intended cache location, delete attacker-selected directories under reachable filesystem paths, and corrupt user configuration, project state, or other accessible application data. Depending on process privileges and deployment context, this may result in integrity loss, denial of service, and potential disruption of dependent workflows.

Mitigation

If you can’t patch tonight, do this now.

Do not load untrusted or attacker-supplied GitHub template URIs in PraisonAI until patched. Restrict or disable GitHub template loading where possible, particularly in configurations that permit arbitrary GitHub sources. Validate and sanitize template owner, repository, path, and ref values before use; reject absolute paths and traversal segments such as dot and dot-dot; and prefer hashing or encoding untrusted URI fields before using them as filesystem path components. Fail closed when GitHub template fetch or cache path validation fails.

Remediation

Patch, then assume compromise.

Upgrade PraisonAI to version 4.6.59 or later. The fix should ensure strict validation of all cache path segments derived from GitHub template references and enforce a final boundary check after path resolution so computed paths cannot escape the designated template cache directory.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

PraisonAIPraisonaiapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity