Issue Task Resolved

#110108Update npm package dompurify to v3.4.11 (no vulnerability in TYPO3)

Oliver Hader 06/26/26, 08:21 updated 06/26/26, 12:30

Description

None of the known vulnerabilities between the installed version 3.4.5 and 3.4.11 of dompurify is actually used in TYPO3. Thus, there is no real attack vector in TYPO3:

  • GHSA-x4vx-rjvf-j5p4 requires IN_PLACE: true — not used — not affected
  • GHSA-hpcv-96wg-7vj8 requires IN_PLACE: true (cross-realm) — not used — not affected
  • GHSA-r47g-fvhr-h676 requires IN_PLACE: true (clobbered root) — not used — not affected
  • GHSA-rp9w-3fw7-7cwq requires IN_PLACE: true + shadow root in <template> — not used — not affected
  • GHSA-vxr8-fq34-vvx9 requires RETURN_TRUSTED_TYPE + clearConfig() — not used — not affected
  • GHSA-cmwh-pvxp-8882 requires setConfig() for ALLOWED_ATTR pollution — not used — not affected
  • GHSA-gvmj-g25r-r7wr requires SAFE_FOR_TEMPLATES + DOM output mode — not used — not affected
  • GHSA-76mc-f452-cxcm requires a hook that mutates data.allowedTags/@data.allowedAttributes@; TYPO3’s afterSanitizeAttributes hook only calls node.setAttribute('target', '_blank') — not affected

Reviews 3

History 36

  1. Oliver Hader changed subject Update npm package dompurify (no vulnerability in TYPO3) Update npm package dompurify to v3.4.11 (no vulnerability in TYPO3) <span data-processor="relativetime" data-value="2026-06-26T10:19:57+00:00" > 06/26/26, 10:19 </span>

  2. Oliver Hader commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-06-26T12:30:54+00:00" > 06/26/26, 12:30 </span>

    Applied in changeset commit:e5237ab4e9b263e0af411aa871ba8431399e0aa4.