# CVE-2026-105696: Missing authorization in penpot

> An attacker with a valid share link can read unauthorized page data in Penpot files by bypassing page-scope restrictions in the get-page RPC command.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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-x9xg-qphx-8grr

## What is CVE-2026-105696?

CVE-2026-105696 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 get-page RPC accepts a share-link permission object with blanket read access but does not verify that the caller-selected page-id belongs to the link's authorized pages set. An attacker with both a valid share link and the attacker's own authenticated Penpot session can retrieve the complete shape and design data of another page in the same file when its identifier is known, because get-page requires authentication. The related get-file-fragment RPC also permits share-link access without mapping fragments to authorized pages. This issue is fixed in version 2.18.0.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-105696 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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