Quick answers
- Is CVE-2026-105686 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105686 being exploited in the wild.
- How severe is CVE-2026-105686?
- Informational severity, published 5 October 2026.
- Which products and versions are affected?
- Penpot before 2.18.0.
- Is there a fix for CVE-2026-105686?
- Yes: fixed in Penpot 2.18.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105686 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-105686?
- 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: Penpot 2.18.0
Technical details
The chunked media upload RPC validates that a chunk index is within range but does not reject duplicate uploads of the same index, allowing each request to allocate an additional temporary object. An authenticated attacker can exploit this to amplify storage usage beyond the upload session's declared logical size. The fix in version 2.18.0 rejects duplicate chunk indices via transaction locking and caps individual chunk size at 30 MiB.
Affected products
- Penpot Penpot before 2.18.0
Timeline
- 2026-10-05: disclosed
- 2026-09-23: patched