# CVE-2026-105687: Penpot: A team admin (non-owner) can remove the team owner via ::delete-team-member — missing owner-protection

> A team admin can remove the team owner, locking them out of projects and files, due to missing authorization checks in the delete-member function.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-j83r-hph3-xpxc

## What is CVE-2026-105687?

CVE-2026-105687 is a medium-severity missing authorization vulnerability in penpot, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Penpot is an open-source design and prototyping platform. Prior to 2.18.0, the delete-team-member RPC allows a team administrator to remove any member other than themselves but does not protect the team owner. A non-owner administrator can delete the owner's team-profile-rel membership and lock the owner out of the team and its projects, files, fonts, and media. This issue is fixed in version 2.18.0.

Weakness: CWE-863 (Incorrect Authorization), CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-105687 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105687 is a medium-severity missing authorization vulnerability in penpot, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105687 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-105687/ (Markdown: https://insights.sbomify.com/CVE-2026-105687/index.md)
```

## Sources

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

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