Quick answers
- Is CVE-2026-47666 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47666 being exploited in the wild.
- How severe is CVE-2026-47666?
- High severity, with a CVSS score of 7.6, published 26 August 2026.
- Which products and versions are affected?
- Penpot up to and including 2.14.3.
- Is there a fix for CVE-2026-47666?
- A patch was published on 2026-05-14: Fix committed on 2026-05-14; patch released in version 2.15.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47666 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-47666?
- 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.
Technical details
The vulnerability is a stored cross-site scripting (XSS) flaw in the font family naming functionality. The backend accepts arbitrary font family names in the create-font-variant and update-font RPC endpoints with no validation, and the frontend interpolates the user-controlled font name directly into a @font-face CSS rule, then injects it via innerHTML without sanitization. An attacker can craft a font name containing markup such as </style><script> to break out of the style element and execute arbitrary JavaScript on the Penpot origin. The attack is passive: any team member who opens a file referencing the malicious font triggers script execution simply by rendering the page. The vulnerability requires low privileges (ability to create or rename fonts within a team) and affects versions up to and including 2.14.3. The fix, released in version 2.15.3, implements a whitelist validator for font family names that restricts characters to letters, digits, spaces, hyphens, underscores, and dots.
Affected products
- Penpot Penpot up to and including 2.14.3
Timeline
- 2026-08-26: disclosed
- 2026-05-14: patched: Fix committed on 2026-05-14; patch released in version 2.15.3