dbcve.org
DicebearApplication

CVE-2026-33418

HIGH · 7.5 CVSS v3.1 Published 2026-03-24
Fix available
A fix is available. Upgrade to 9.4.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
DiceBear is an avatar library for designers and developers. Prior to version 9.4.2, the `ensureSize()` function in `@dicebear/converter` used a regex-based approach to rewrite SVG `width`/`height` attributes, capping them at 2048px to prevent denial of service. This size capping could be bypassed by crafting SVG input that causes the regex to match a non-functional occurrence of `<svg` before the actual SVG root element. When the SVG is subsequently rendered via `@resvg/resvg-js` on the Node.js code path, it renders at the attacker-specified dimensions, potentially causing out-of-memory crashes. In version 9.4.2, the regex-based approach has been replaced with XML-aware processing using `fast-xml-parser` to correctly identify and modify the SVG root element's attributes. Additionally, a `fitTo` constraint has been added to the `renderAsync` call as defense-in-depth, ensuring the rendered output is always bounded regardless of SVG content.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The @dicebear/converter library used a regex-based approach in the ensureSize() function to cap SVG dimensions at 2048px. Attackers bypassed this by crafting malicious SVGs containing a decoy '<svg' tag before the actual root element, causing the regex to match and modify the wrong element. When rendered via @resvg/resvg-js, the SVG renders at attacker-specified dimensions causing potential out-of-memory crashes.

MitigationUpgrade @dicebear/converter to version 9.4.2 or later, which replaces the regex approach with XML-aware parsing using fast-xml-parser and adds a fitTo constraint as defense-in-depth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DicebearApplication
Affected:< 9.4.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify @dicebear/converter version
    Run 'npm list @dicebear/converter' or check package.json to see the installed version of @dicebear/converter
    Affected if The installed version is less than 9.4.2
  2. Check for SVG processing code
    Search codebase for imports or usage of @dicebear/converter, specifically look for calls to functions that process SVG images
    Affected if Code imports or uses @dicebear/converter to process SVG files
  3. Verify @resvg/resvg-js usage
    Search for '@resvg/resvg-js' in dependencies and code that renders SVGs using this library
    Affected if @resvg/resvg-js is used to render SVGs from @dicebear/converter output
  4. Check for untrusted SVG input
    Inspect whether user-supplied or externally-sourced SVG files are being passed to @dicebear/converter
    Affected if SVGs from untrusted or external sources are processed by the library
  5. Inspect ensureSize function implementation
    Examine the node_modules/@dicebear/converter source code for the ensureSize() function to see if it uses regex-based dimension capping
    Affected if The ensureSize() function uses regex rather than XML-aware parsing to limit SVG dimensions

You are affected if @dicebear/converter version is below 9.4.2 and your application processes SVG files (especially from untrusted sources) using the vulnerable regex-based ensureSize() function with @resvg/resvg-js rendering.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.4.2 or later
Fixed in 9.4.2
Interim mitigation

Upgrade @dicebear/converter to version 9.4.2 or later, which replaces the regex approach with XML-aware parsing using fast-xml-parser and adds a fitTo constraint as defense-in-depth.

Recommended fix High confidence

@dicebear/converter version 9.4.2 or later (upgrade entire DiceBear to version 9.4.2 or later for consistency)

  1. Identify all DiceBear packages in your project that depend on @dicebear/converter using `npm list @dicebear/converter` or `yarn list @dicebear/converter`
  2. Update the @dicebear/converter package to version 9.4.2 or later by running `npm install @dicebear/converter@^9.4.2` or `yarn add @dicebear/converter@^9.4.2`
  3. Run `npm install` or `yarn install` to update all transitive dependencies
  4. Verify the installed version matches 9.4.2 or later using `npm list @dicebear/converter`
  5. Test your application's avatar rendering functionality to ensure the upgrade does not break existing functionality
  6. If using a lockfile, commit the updated package-lock.json or yarn.lock
Caveat Minimal risk; the fix replaces internal regex processing with XML parsing and adds defense-in-depth constraints. No breaking API changes are mentioned in the advisory.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dicebear Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33418 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33418 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data