CVE-2026-26202 in Penpot
Summary
by MITRE • 02/19/2026
Penpot is an open-source design tool for design and code collaboration. Prior to version 2.13.2, an authenticated user can read arbitrary files from the server by supplying a local file path (e.g. `/etc/passwd`) as a font data chunk in the `create-font-variant` RPC endpoint, resulting in the file contents being stored and retrievable as a "font" asset. This is an arbitrary file read vulnerability. Any authenticated user with team edit permissions can read arbitrary files accessible to the Penpot backend process on the host filesystem. This can lead to exposure of sensitive system files, application secrets, database credentials, and private keys, potentially enabling further compromise of the server. In containerized deployments, the blast radius may be limited to the container filesystem, but environment variables, mounted secrets, and application configuration are still at risk. Version 2.13.2 contains a patch for the issue.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 02/19/2026
The vulnerability CVE-2026-26202 represents a critical arbitrary file read flaw in Penpot, an open-source design collaboration platform that facilitates both design and code workflows. This security weakness exists within the application's RPC endpoint handling specifically in the create-font-variant functionality, where authenticated users can manipulate input parameters to access sensitive system resources. The vulnerability stems from inadequate input validation and sanitization mechanisms that fail to properly restrict file path access when processing font data chunks, creating a direct path for unauthorized file retrieval from the underlying host system.
The technical exploitation of this vulnerability occurs through the manipulation of the create-font-variant RPC endpoint, where attackers can supply local file paths such as /etc/passwd as font data chunks. When processed by the backend, these malicious inputs result in the contents of specified files being stored and retrievable as legitimate "font" assets within the application's asset management system. This flaw specifically affects authenticated users who possess team edit permissions, eliminating the need for additional privilege escalation while maintaining the ability to access files that the Penpot backend process can read. The vulnerability aligns with CWE-22, which describes improper limitation of a pathname to a restricted directory, and represents a classic path traversal attack vector that has been documented across numerous applications and platforms.
The operational impact of this vulnerability extends beyond simple information disclosure, potentially enabling attackers to extract sensitive credentials, private keys, database connection strings, and other confidential application configuration data. In containerized deployments, while the immediate blast radius may be constrained to the container filesystem, the vulnerability still poses significant risks to environment variables, mounted secrets, and application configuration files that are accessible within the containerized environment. This exposure can facilitate further compromise of the system through credential theft, lateral movement, or privilege escalation attacks that leverage the stolen information. The vulnerability particularly impacts organizations using Penpot in production environments where sensitive data may be stored in accessible locations within the application's file hierarchy.
Organizations utilizing Penpot must prioritize immediate remediation by upgrading to version 2.13.2 or later, which includes the necessary patch to address the arbitrary file read vulnerability. Security teams should conduct comprehensive assessments of their Penpot deployments to identify any potential exploitation attempts and review access controls to ensure that only authorized personnel possess team edit permissions. Additional mitigations include implementing network segmentation to limit access to Penpot services, monitoring for unusual file access patterns, and conducting regular security audits of the application's file handling mechanisms. The vulnerability demonstrates the importance of proper input validation and access control enforcement in web applications, particularly those handling user-supplied data that may be processed and stored within the application's asset management system. Organizations should also consider implementing principle of least privilege access controls and regularly review user permissions to minimize potential impact from similar vulnerabilities in other application components.