CVE-2026-41240 | cure53 DOMPurify up to 3.3.x permissive list of allowed inputs

VDB-359153 · CVE-2026-41240 · GCVE-0-2026-41240 CURE53 DOMPURIFY UP TO 3.3.X PERMISSIVE LIST OF ALLOWED INPUTS HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.1 $0-$5k 1.82 Summaryinfo A vulnerability marked as problematic has been reported in cure53 DOMPurify up to 3.3.x. This vulnerability affects unknown code. The manipulation leads to permissive list of allowed inputs. This vulnerability is listed as CVE-2026-41240. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component. Detailsinfo A vulnerability was found in cure53 DOMPurify up to 3.3.x. It has been rated as problematic. This issue affects an unknown code. The manipulation with an unknown input leads to a permissive list of allowed inputs vulnerability. Using CWE to declare the problem leads to CWE-183. The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input that is unsafe, leading to resultant weaknesses. Impacted is integrity. The summary by CVE is: DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Versions prior to 3.4.0 have an inconsistency between FORBID_TAGS and FORBID_ATTR handling when function-based ADD_TAGS is used. Commit c361baa added an early exit for FORBID_ATTR at line 1214. The same fix was not applied to FORBID_TAGS. At line 1118-1123, when EXTRA_ELEMENT_HANDLING.tagCheck returns true, the short-circuit evaluation skips the FORBID_TAGS check entirely. This allows forbidden elements to survive sanitization with their attributes intact. Version 3.4.0 patches the issue. The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-41240 since 04/18/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. Upgrading to version 3.4.0 eliminates this vulnerability. Productinfo Vendor cure53 Name DOMPurify Version 3.0 3.1 3.2 3.3 Website Product: https://github.com/cure53/DOMPurify/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 4.3 VulDB Meta Temp Score: 4.1 VulDB Base Score: 4.3 VulDB Temp Score: 4.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Permissive list of allowed inputs CWE: CWE-183 / CWE-20 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: DOMPurify 3.4.0 Timelineinfo 04/18/2026 CVE reserved 04/23/2026 +5 days Advisory disclosed 04/23/2026 +0 days VulDB entry created 04/23/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-41240 (🔒) GCVE (CVE): GCVE-0-2026-41240 GCVE (VulDB): GCVE-100-359153 Entryinfo Created: 04/23/2026 18:15 Changes: 04/23/2026 18:15 (65) Complete: 🔍 Cache ID: 99:743:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸