Skip to content

← Actionable
Medium, CVSS 6.5amended

enshrined/svg-sanitize: Denial of Service via DTD Attribute Declaration Crash

CVE-2026-107379GHSA-v383-3rw5-q8rf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (enshrined/svg-sanitize 1.0.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-107379: 0.53% estimated exploitation activity in the next 30 days; percentile 44.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A crafted SVG file (1009 bytes) crashes the PHP process when sanitized by enshrined/svg-sanitize (any version through 0.22.x). The sanitizer's cleanAttributesOnWhitelist() method calls DOMElement::removeAttribute() twice on the same attribute name — first removing the explicit attribute, then attempting to remove the DTD #FIXED default — triggering a PHP ext/dom type confusion that kills the PHP-FPM worker. Affected installations: - enshrined/svg-sanitize: 45.2M Packagist downloads, 1.3M/month, 90+ dependents - WordPress Safe SVG plugin: 1M+ active installs - TYPO3: svg-sanitize integrated into core since v9 - Drupal: community module wrapping svg-sanitize Vulnerability Details Trigger Flow Root cause in svg-sanitize: The sanitizer does not strip DOCTYPE/DTD declarations before processing. The cleanAttributesOnWhitelist() method at Sanitizer.php:303-330 has a double-removal pattern where the whitelist check and the href safety check can both call removeAttribute() on the same…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-v383-3rw5-q8rf

  2. Revision 1 · created ·

    Published from osv record GHSA-v383-3rw5-q8rf

Agent brief

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

# Patch Next advisory brief: CVE-2026-107379

Advisory: enshrined/svg-sanitize: Denial of Service via DTD Attribute Declaration Crash
IDs: CVE-2026-107379, GHSA-v383-3rw5-q8rf
Record: https://patchnext.com/advisories/cve-2026-107379 (revision 2, source checked 26 Oct 2026, 14:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: enshrined/svg-sanitize 1.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist enshrined/svg-sanitize: affected <= 0.22.0; fixed in 1.0.0

## Suggested inspection (read-only)
- Packagist enshrined/svg-sanitize: check the installed version with your package manager.

## 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 enshrined/svg-sanitize.
- 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-v383-3rw5-q8rf (OSV record GHSA-v383-3rw5-q8rf lists affected ranges: Packagist enshrined/svg-sanitize >=0 <1.0.0 (fixed))
- Verified: https://github.com/advisories/GHSA-v383-3rw5-q8rf (GitHub-reviewed advisory GHSA-v383-3rw5-q8rf lists affected ranges: Packagist enshrined/svg-sanitize >=0 <=0.22.0)

Commands are suggestions: review each one before running it.

Loading voting…