Fabric.js Affected by Stored XSS via SVG Export

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L

EPSS

• CVE-2026-27013: 0.33% estimated exploitation activity in the next 30 days; percentile 25.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

fabric.js applies escapeXml() to text content during SVG export (src/shapes/Text/TextSVGExportMixin.ts:186) but fails to apply it to other user-controlled string values that are interpolated into SVG attribute markup. When attacker-controlled JSON is loaded via loadFromJSON() and later exported via toSVG(), the unescaped values break out of XML attributes and inject arbitrary SVG elements including event handlers. Deserialization Path (no sanitization) loadFromJSON() (src/canvas/StaticCanvas.ts:1229) calls enlivenObjects() which calls fromObject() (src/shapes/Object/Object.ts:1902). fromObject passes all deserialized properties to the shape constructor via new this(enlivedObjectOptions). The constructor ultimately calls setOptions() (src/CommonMethods.ts:9) which iterates over every property and assigns it to the object via this.set(prop, options[prop]). There is no allowlist or sanitization - any property in the JSON, including id, is set verbatim on the fabric object. --- Finding…

Published by the source

18 Feb 2026, 22:44 UTC

Last modified by the source

22 Feb 2026, 23:24 UTC

Source last checked

26 Oct 2026, 12:42 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-hfvx-25r5-qc3w

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-hfvx-25r5-qc3w

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-27013

Advisory: Fabric.js Affected by Stored XSS via SVG Export
IDs: CVE-2026-27013, GHSA-hfvx-25r5-qc3w
Record: https://patchnext.com/advisories/cve-2026-27013 (revision 2, source checked 26 Oct 2026, 12:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: fabric 7.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm fabric: affected < 7.2.0; fixed in 7.2.0

## Suggested inspection (read-only)
- `npm ls fabric --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on fabric.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-hfvx-25r5-qc3w (OSV record GHSA-hfvx-25r5-qc3w lists affected ranges: npm fabric >=0 <7.2.0 (fixed))
- Verified: https://github.com/advisories/GHSA-hfvx-25r5-qc3w (GitHub-reviewed advisory GHSA-hfvx-25r5-qc3w lists affected ranges: npm fabric >=0 <7.2.0)

Commands are suggestions: review each one before running it.