CVE-2026-17613 Penpot Unauthorized File Takeover and Cross-Team Hijacking via import-binfile

Here is a concise Markdown summary based on the webpage screenshot content: --- CVE-2026-17613: Penpot Cross-Team File Takeover Vulnerability (import-binfile) Vulnerability Overview Penpot's RPC command accepts an optional parameter , intended to "import a file into an existing file rather than creating a new one." This handler verifies that the caller has edit permissions for the provided , but fails to verify whether the belongs to the caller. Consequently, any authenticated user can specify an arbitrary to overwrite a target file and reassign the file's ownership to the attacker's team, enabling cross-team file takeover. > ⚠️ This vulnerability requires no prerequisites (such as shared links or library enumeration). On default open-registration instances, attackers can exploit it without any prior relationship with the target. --- Impact Scope Affected Product: Penpot (open-source design and prototyping platform by Kaleidos) Affected Versions: v1.20 and above (including self-hosted Community Edition and Penpot Cloud) Severity: Critical (CVSS v3.1 Base Score 9.9) Impact Types: - Data destruction (file content is overwritten) - Persistent takeover (file ownership is transferred to the attacker's team) - Library contamination (if it is a shared design library, it can contaminate all downstream synchronized teams) - Cross-team scope (no trust relationship required; directly crosses security boundaries) --- Remediation Temporary Mitigations (as of publication, no patch available): 1. Disable open self-registration → Removes the path for attackers to create accounts autonomously, reducing the attack surface. 2. Assume all accounts have write access to all files within the instance → If the deployment relies on team isolation for confidentiality, consider separating instances for sensitive client work. 3. Audit for signs of prior exploitation → Look for changes in the field without corresponding user actions in the line; or files with no normal editing history in their version control but belonging to a non-member team—these may be signals of hijacking. 4. Maintain local backups → Since there is no built-in recovery mechanism, regularly export snapshots and store them externally. Root Cause Fix Recommendations: In the handler, add an additional verification of edit permissions for the (not limited to ). Reject any "in-place import" requests that move files into different projects (blocking the reassignment logic). --- Proof of Concept (POC) > The server will overwrite the victim's file with the attacker's content and reassign the file's ownership to the attacker's team. The file will subsequently disappear from the victim's project and appear in the attacker's project, where it can be opened, exported, copied, or shared. --- Additional Notes This vulnerability is accompanied by a lower-severity related issue: real-time WebSocket channels allow clients to subscribe to arbitrary file/team topics without permission checks, potentially leading to collaboration editing leaks. The vulnerability was discovered on 2026-05-27. After reporting to the vendor, there was no response for 21 days, leading to coordinated public disclosure via CERT/CC. As of publication (2026-08-04), no official patch is available. --- ✅ It is recommended to apply temporary mitigations immediately and monitor for anomalies in file ownership.

Goal Reached Thanks to every supporter — we hit 100%!

CVE-2026-17613 Penpot Unauthorized File Takeover and Cross-Team Hijacking via import-binfile