CVE-2026-55852
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 · uneditedFrappe is a full-stack web application framework. Prior to 16.23.0 and 15.112.0, TarSlip RCE was possible in Package Import because tarfile members were not sufficiently checked before extraction. This issue is fixed in versions 16.23.0 and 15.112.0.
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 confidenceFrappe framework versions prior to 15.112.0 and 16.23.0 contained a TarSlip vulnerability in the Package Import feature. The application did not sufficiently validate tarfile member paths before extraction, allowing attackers to craft malicious tar archives containing path traversal sequences (e.g., ../../etc/) to write files outside the intended extraction directory, achieving remote code execution.
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
- High
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Identify Frappe framework installationLocate the Frappe installation by checking for the 'frappe' Python package (e.g., run 'pip show frappe' or 'pip list | grep -i frappe') or check for the 'frappe' directory in your Python environment or application rootAffected if Frappe framework is not installed - this CVE does not apply
-
Determine installed Frappe versionRun 'bench version' if using Frappe Bench, or check the version attribute in the frappe module (e.g., 'python -c "import frappe; print(frappe.__version__)"')Affected if Version is below 15.112.0 or below 16.23.0 (the exact version can be compared against the affected ranges)
-
Verify Package Import feature accessibilityCheck if the Package Import functionality is available in the Frappe desk by navigating to the module or checking the UI for import options. In Frappe, the Package Import is typically found under Settings or as a module that can be accessed via the desk interfaceAffected if Package Import feature exists and is accessible in the deployment - exploitation requires this feature to be present and reachable
Your environment is affected if Frappe framework versions 15.x below 15.112.0 or 16.x below 16.23.0 are installed AND the Package Import feature is accessible in your deployment
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 · scopedUpgrade Frappe to version 15.112.0 or 16.23.0 or later to obtain the patched tarfile validation. If immediate upgrade is not possible, disable or restrict the Package Import functionality until the upgrade can be completed.
Frappe version 15.112.0 or 16.23.0 (depending on your major version branch)
- 1. Identify the current Frappe version currently running in your environment (check via bench version or Frappe About page)
- 2. If running Frappe 15.x, upgrade to version 15.112.0 or later
- 3. If running Frappe 16.x, upgrade to version 16.23.0 or later
- 4. Run database migrations after upgrade: bench migrate
- 5. Verify the upgrade was successful and the tarfile extraction is now properly validated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-55852 — 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-55852 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