SVG Injection via Unsanitized Options in @dicebear/core and @dicebear/initials

Exploitation

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

CVSS

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

EPSS

• CVE-2026-33311: 0.19% estimated exploitation activity in the next 30 days; percentile 8.49 (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.

Summary SVG attribute values derived from user-supplied options (backgroundColor, fontFamily, textColor) were not XML-escaped before interpolation into SVG output. This could allow Cross-Site Scripting (XSS) when applications pass untrusted input to createAvatar() and serve the resulting SVG inline or with Content-Type: image/svg+xml. Affected packages - @dicebear/core — backgroundColor option values interpolated into SVG attributes without escaping (affects solid and gradientLinear background types) - @dicebear/initials — fontFamily and textColor option values interpolated into SVG attributes without escaping Fix All affected SVG attribute values are now properly escaped using XML entity encoding. Users should upgrade to the listed patched versions. Mitigating factors - Applications that validate input against the library's JSON Schema before passing it to createAvatar() are not affected - The DiceBear CLI validates input via AJV and was not vulnerable - Exploitation requires that…

Published by the source

19 Mar 2026, 17:49 UTC

Last modified by the source

10 Sep 2026, 03:51 UTC

Source last checked

26 Oct 2026, 12:46 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-mr9r-mww3-v6gv

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-mr9r-mww3-v6gv

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

# Patch Next advisory brief: CVE-2026-33311

Advisory: SVG Injection via Unsanitized Options in @dicebear/core and @dicebear/initials
IDs: CVE-2026-33311, GHSA-mr9r-mww3-v6gv
Record: https://patchnext.com/advisories/cve-2026-33311 (revision 2, source checked 26 Oct 2026, 12:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @dicebear/initials 9.4.1, 8.0.3, 7.1.4, 6.1.4, 5.4.4; @dicebear/core 9.4.1, 8.0.3, 7.1.4, 6.1.4, 5.4.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @dicebear/initials: affected >= 5.0.0, <= 5.4.3; >= 6.0.0, <= 6.1.3; >= 7.0.0, <= 7.1.3; >= 8.0.0, <= 8.0.2; >= 9.0.0, <= 9.4.0; fixed in 8.0.3, 7.1.4, 9.4.1, 6.1.4, 5.4.4
- npm @dicebear/core: affected >= 5.0.0, <= 5.4.3; >= 6.0.0, <= 6.1.3; >= 7.0.0, <= 7.1.3; >= 8.0.0, <= 8.0.2; >= 9.0.0, <= 9.4.0; fixed in 8.0.3, 7.1.4, 9.4.1, 6.1.4, 5.4.4

## Suggested inspection (read-only)
- `npm ls @dicebear/initials --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @dicebear/core --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 @dicebear/initials, @dicebear/core.
- 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-mr9r-mww3-v6gv (OSV record GHSA-mr9r-mww3-v6gv lists affected ranges: npm @dicebear/core >=5.0.0 =6.0.0 =7.0.0 =8.0.0 =9.0.0 =5.0.0 =6.0.0 =7.0.0 =8.0.0 =9.0.0 <9.4.1 (fixed))
- Verified: https://github.com/advisories/GHSA-mr9r-mww3-v6gv (GitHub-reviewed advisory GHSA-mr9r-mww3-v6gv lists affected ranges: npm @dicebear/core >=5.0.0 =6.0.0 =7.0.0 =8.0.0 =9.0.0 =5.0.0 =6.0.0 =7.0.0 =8.0.0 =9.0.0 <=9.4.0)

Commands are suggestions: review each one before running it.