CVE-2026-105690: Penpot session token replay via logout bypass

CVE-2026-105690 · Severity: medium · CVSS 5.9 · Published 2026-10-05

Penpot is an open-source design and prototyping platform that enables collaborative design work. Before version 2.18.0, logging out only cleared the browser cookie but did not revoke the server-side session, allowing an attacker who previously captured a session token to continue making authenticated requests as the victim indefinitely or until the token naturally expires. This permits unauthorized access to the victim's projects, designs, and account data.

Technologies: Penpot. Vendors: Penpot.

Quick answers

Is CVE-2026-105690 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-105690 being exploited in the wild.
How severe is CVE-2026-105690?
Medium severity, with a CVSS score of 5.9, published 5 October 2026.
Which products and versions are affected?
Penpot prior to 2.18.0.
Is there a fix for CVE-2026-105690?
Yes: fixed in 2.18.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-105690 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-105690?
Check whether you run Penpot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 2.18.0

Technical details

The logout function clears the auth-token browser cookie but fails to invalidate the corresponding server-side session due to a code path issue where the session ID is not properly available for deletion. An attacker with a previously captured session token (CWE-613: Insufficient Session Expiration) can replay it to bypass authentication checks. The fix in 2.18.0 corrects the delete function to properly revoke the server-side session when the user logs out.

Affected products

  • Penpot Penpot prior to 2.18.0

Timeline

  • 2026-10-05: disclosed
  • 2026-09-23: patched: Version 2.18.0 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.