Skip to main content
Menu
CVEs

Penpot stored XSS in SVG sanitizer via prefixed elements

CVE-2026-133704Published , updated

5.1MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.18.2
Who is exposed
Not reported

Summary

Penpot, the open-source design tool, is affected by a stored cross-site scripting flaw in versions from 2.18.0 up to (but not including) 2.18.2. An attacker with edit rights, reachable over the network after logging in, can upload an SVG file that uses namespace-prefixed elements to slip past the sanitizer and run JavaScript in the browsers of other users who open it, which requires a user to take an action.

Written by a model

Original description

Penpot 2.18.0 before 2.18.2 contains a stored cross-site scripting vulnerability that allows authenticated users with edit rights to bypass the sanitize-svg-element blocklist using namespace-prefixed SVG elements. Attackers can upload SVGs containing elements like x:script or attributes like x:onload, which are served inline as image/svg+xml to run JavaScript in victims' Penpot sessions.

What to do

Upgrade to a fixed version: 2.18.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133704 (Penpot 2.18.0 before 2.18.2 Stored XSS via Namespace-Prefixed SVG Elements), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133704 (entry last updated 2026-11-20):
Affected:
- penpot penpot: from 2.18.0, fixed in 2.18.2
Fixed versions: 2.18.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133704 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133704 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/penpot/penpot/security/advisories/GHSA-82p2-67qr-4rwf
- https://github.com/penpot/penpot/commit/238a4d8613d4799b92eab0e38e5194fb72dc116d
- https://github.com/penpot/penpot/blob/2.18.0/backend/src/app/media/svg.clj
- https://github.com/penpot/penpot/releases/tag/2.18.2
- https://www.vulncheck.com/advisories/penpot-2.18.0-before-2.18.2-stored-xss-via-namespace-prefixed-svg-elements
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133704
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133704"}.

Affected versions

cve.now Index

8Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.1/10CVSS 5.1
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 7

Questions about CVE-2026-133704

Is CVE-2026-133704 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133704?

penpot: from 2.18.0 before 2.18.2.

Source: cve.now feed data

How do I fix CVE-2026-133704?

Upgrade to a fixed version: 2.18.2.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.