Frappe Framework Patches High-Severity TarSlip RCE Bug in Package Import (CVE-2026-55852)

A newly disclosed vulnerability in the widely used Frappe Framework could have allowed attackers to achieve remote code execution simply by tricking an administrator into importing a malicious package file, according to a security advisory published last week.

Security researchers AarDG10, ivanovanton, pucagit, and ilyass-armadin identified and reported the flaw, tracked as CVE-2026-55852 and cataloged under GHSA-58w2-4cjg-hvp6.

The issue was formally disclosed on GitHub’s Security Advisory database, with AarDG10 credited as the remediation developer who helped push the fix into the codebase.

Frappe Framework Patches High-Severity

Frappe is a full-stack, low-code web application framework that powers popular business software like ERPNext, making it a critical piece of infrastructure across thousands of enterprise deployments.nvd.

The flaw is a classic “TarSlip” issue, a specific type of path traversal vulnerability that occurs when an application extracts tar archive contents without properly validating file paths embedded inside the archive.

In Frappe’s case, the vulnerable code path lives in the framework’s Package Import functionality, a feature that lets administrators load Packages, which function as lightweight, portable app bundles built directly through the Frappe UI.

Because the underlying tarfile extraction logic did not sanitize entry names before writing files to disk, a specially crafted archive could contain path traversal sequences that escape the intended extraction directory.

An attacker able to get a malicious package file imported into a Frappe instance could overwrite arbitrary files on the server’s filesystem, ultimately achieving remote code execution.

GitHub’s advisory database rates the flaw as High severity, reflecting the potential for full server compromise despite requiring some level of interaction from a privileged user to trigger the malicious import.

The vulnerability affects all Frappe Framework releases prior to version 16.23.0 on the newer branch and prior to 15.112.0 on the older, still-supported branch.

Unlike some vulnerabilities that can be temporarily mitigated with configuration changes, the Frappe security team has made it clear that no workaround exists for this issue.

Organizations running self-hosted Frappe or ERPNext instances must upgrade to the patched releases, 16.23.0 or 15.112.0 depending on their branch, to eliminate the risk entirely.

Given the absence of mitigating controls, security teams managing Frappe-based deployments should treat this as an urgent patching priority rather than something to schedule for a routine maintenance window.

Audit all Frappe and ERPNext instances to confirm current version numbers against the vulnerable ranges.
Restrict Package Import functionality to trusted, verified administrators only until patches are applied.
Upgrade immediately to Frappe 16.23.0 or 15.112.0, whichever branch applies to the deployment.
Review server file integrity logs for signs of unexpected file writes tied to recent package imports.
Monitor GitHub’s advisory feed for Frappe going forward, given the framework’s recent pattern of high-severity findings.