Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-17613 – Missing Authorization / Cross-Team File Takeover – Penpot versions up to and includ

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-17613 is a missing authorization vulnerability (CWE-862) in the open-source design and prototyping platform Penpot. The flaw resides in the ::import-binfile RPC command, which fails to enforce proper authorization on an optional caller-supplied file-id parameter, allowing an authenticated user to overwrite arbitrary files and subscribe to related WebSocket events. It is rated HIGH with a CVSS v3.1 base score of 7.5.

Technical details

  • Root cause: The ::import-binfile RPC command validates edit permissions on the caller’s own project but does not verify authorization for a caller-supplied file-id parameter; that file-id is passed straight through and used without a matching permission check.
  • Trigger conditions: An authenticated user invokes the import with an "in-place" file-id parameter, supplying a valid Penpot archive as payload and a target file identifier. The handler overwrites the existing file and re-parents it to the attacker’s project.
  • Attack vector: Network (remote). On installations with open self-registration, an attacker needs no prior relationship to the victim.
  • Impact: Arbitrary files can be overwritten with attacker-controlled data, file ownership can be transferred to the attacker, and shared design libraries can be poisoned across teams, resulting in data corruption and loss of access.

Affected software

  • Penpot versions 0 through 2.17.0 (inclusive).

Severity

  • CVSS v3.1 Base Score: 7.5 (HIGH)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Mitigation and recommended actions

  • Immediate: No fixed release was confirmed at the time of disclosure (published August 5, 2026). Monitor the official Penpot release channel and apply the vendor’s security update as soon as it is published.
  • If no patch is available: Restrict who can reach the deployment — disable open self-registration, place the instance behind authenticated access controls, and limit network exposure of the Penpot backend to trusted users only. Review team and file access boundaries and audit for unexpected changes in file ownership or content.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Penpot
  • Raw response body: globalThis.penpotVersion =, window.penpot, /api/rpc/command/
  • URL of a loaded script: /js/config.js

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge