# CVE-2026-17613: CVE-2026-17613

> Authenticated users can overwrite arbitrary files and exfiltrate data due to missing authorization checks on the import-binfile RPC command.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-7ff3-w2cq-gmpq

## What is CVE-2026-17613?

CVE-2026-17613 is a high-severity missing authorization vulnerability in Penpot, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Penpot’s ::import-binfile RPC command lacks authorization on the optional file-id parameter, allowing any authenticated user to overwrite any files on the target server and subscribe to WebSocket events, enabling full data exfiltration and data poisoning.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-17613?


## How do I fix CVE-2026-17613?

No fix has been published for CVE-2026-17613 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-17613 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-17613 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-17613 and fix it if it is affected.

What it is: CVE-2026-17613 is a high-severity missing authorization vulnerability in Penpot, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-17613 exists.

Affected product: Penpot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-17613/ (Markdown: https://insights.sbomify.com/CVE-2026-17613/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-17613
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-17613
- OSV: https://osv.dev/vulnerability/CVE-2026-17613

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-17613/
Summaries are generated and may contain mistakes; the official description above is the record.