CVE-2026-105694 penpot CVE debrief

Who should care

Penpot administrators, users with file-edit permissions, and security teams responsible for monitoring and protecting design and prototyping platforms should assess exposure and prioritize patching.

Why it matters

This stored XSS vulnerability in Penpot allows attackers to execute malicious JavaScript, potentially leading to unauthorized actions and data access. Penpot administrators and security teams should prioritize patching and verify exposure, especially in environments with untrusted user uploads.

• Execution of attacker-controlled JavaScript in the context of the Penpot origin
• Potential for unauthorized requests and data access with victim's session authority
• Need for verification of affected versions and user exposure
• Priority for patching and restricting file-edit permissions

Technical summary

The vulnerability allows authenticated users with file-edit permission to upload SVG media containing scripts, event-handler attributes, and foreignObject elements without sanitization. When a victim navigates to the asset URL, the attacker-controlled JavaScript is executed in the Penpot origin, enabling requests and data access with the victim's Penpot session authority. This issue was fixed in version 2.18.0. Affected Penpot instances should be identified, and defenders should verify user exposure, especially in environments with untrusted user uploads.

Defensive priority

Medium-priority patching and verification recommended for Penpot instances, especially those with untrusted user uploads.

Recommended defensive actions

• Apply the patch by updating to Penpot version 2.18.0 or later
• Restrict file-edit permissions to trusted users
• Monitor for suspicious SVG uploads and user activity
• Consider implementing additional security measures for user-uploaded content
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and fixed version. However, there is limited information on potential exploits or victim impact. To verify exposure, defenders should check for affected Penpot instances, review user upload permissions, and monitor for suspicious SVG uploads. Additional security measures, such as restricting file-edit permissions and implementing content security policies, may be necessary.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.