Quick answers
- Is CVE-2026-47344 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47344 being exploited in the wild.
- How severe is CVE-2026-47344?
- Medium severity, with a CVSS score of 4, published 8 June 2026.
- Which products and versions are affected?
- typo3/html-sanitizer (Packagist) < 2.3.2, ECOSYSTEM:introduced=0,fixed=2.3.2; Typo3 Html-Sanitizer < 2.3.2.
- Is there a fix for CVE-2026-47344?
- Yes. typo3/html-sanitizer (Packagist): upgrade to 2.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47344 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47344?
- Check whether you run typo3/html-sanitizer (Packagist) or Typo3 Html-Sanitizer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- typo3/html-sanitizer (Packagist): upgrade to 2.3.2 or later
composer require typo3/html-sanitizer:^2.3.2
Technical details
A cross-site scripting (XSS) vulnerability exists in the TYPO3 HTML Sanitizer when the ALLOW_INSECURE_RAW_TEXT configuration is enabled. The root cause is a discrepancy between how the sanitizer and web browsers parse closing tags containing whitespace characters (such as tabs). While the sanitizer fails to recognize these as valid end tags, browsers treat them as legitimate, allowing an attacker to break out of raw text elements (like <style> or <script>) and inject malicious markup. This bypasses the library's primary XSS prevention mechanism. The issue is fixed in version 2.3.2.
Affected products
- TYPO3 html-sanitizer < 2.3.2
Identifiers
- CVE-2026-47344
- GHSA-jvf5-rxvv-3mcg
Timeline
- 2026-06-08: disclosed
- 2026-06-12: advisory