# CVE-2026-105692: Penpot: IDOR in Share-Link Deletion Allows Any File Editor to Delete Share-Links They Did Not Create

> Any file editor can delete share-links created by others, revoking external access, due to missing ownership checks in Penpot.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-8257-pm4f-cfhq

## What is CVE-2026-105692?

CVE-2026-105692 is a medium-severity missing authorization vulnerability in penpot, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Penpot is an open-source design and prototyping platform. Prior to 2.18.0, the delete-share-link RPC retrieves a caller-selected share-link ID and verifies only that the caller can edit the parent file. It does not verify that the caller created the share link or has owner or administrator authority, allowing any file editor who knows a share-link UUID to delete links created by other users and revoke external reviewers' access. This issue is fixed in version 2.18.0.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-105692 being exploited?

There is no known exploitation of CVE-2026-105692 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105692 is a medium-severity missing authorization vulnerability in penpot, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105692 in the wild and no public exploit code.

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-105692/ (Markdown: https://insights.sbomify.com/CVE-2026-105692/index.md)
```

## Sources

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

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