CVE-2026-105696: Penpot: Share-link page-scope escalation: a share-link holder reads pages outside the link's authorized scope via the get-page RPC command

Published Oct 5, 2026
·
Updated

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.

Affected Software

1 affected component
Penpot Penpot<2.18.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Penpot to a version that resolves this vulnerability.

    Fixed in 2.18.0

Event History

Oct 5, 2026
CVE Published
via MITRE·08:05 PM
Data Sourced
via MITRE·08:05 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Penpot instances running versions before 2.18.0 are affected. Exposure requires files that use share links with access limited to selected pages, because the flaw allows access beyond that selected-page scope within the same file.

2

What does an attacker need to exploit it?

The attacker needs a valid share link and their own authenticated Penpot session. They must also know the identifier of a different page in the same file to retrieve that page's shape and design data through get-page.

3

Are unauthenticated share-link visitors affected?

The get-page attack requires authentication, so a share link alone is not sufficient for that RPC path. However, the related get-file-fragment RPC permits share-link access without mapping fragments to authorized pages.

4

What should teams do to remediate the issue?

Upgrade Penpot to version 2.18.0, which fixes the issue. Until upgrade, treat share links for files containing sensitive pages as potentially able to expose other pages in the same file to authenticated link holders.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203