MediumCVE-2026-41240

    DOMPurify: Permissive List of Allowed Inputs (CVE-2026-41240)

    Published

    What is affected, what to do

    A flaw was found in DOMPurify, a DOM-only cross-site scripting sanitizer. A remote attacker could exploit an inconsistency in how forbidden tags and attributes are handled when function-based tag additions are used.

    An exploit is publicly available. Update Cure53 DOMPurify to version 3.4.0.

    Affected
    • Cure53 DOMPurify lt *..3.4.0
    Fixed in
    • Cure53 DOMPurify 3.4.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    6.1

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    6.1

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 33.3

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    63.87 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    PoC (publicly reported)
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    6.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    6.1
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    6.0
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.4 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    33.3
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-183, CWE-79

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    A flaw was found in DOMPurify, a DOM-only cross-site scripting sanitizer. A remote attacker could exploit an inconsistency in how forbidden tags and attributes are handled when function-based tag additions are used. This allows malicious HTML, MathML, or SVG elements to bypass sanitization and execute arbitrary code in the user's browser, leading to Cross-Site Scripting (XSS).

    Source: BSI WID Portal

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    VendorProductAffected versionsFixed in
    cure53DOMPurify
    • < 3.4.0
    • 3.4.0
    cure53dompurify
    • < 3.4.0
    • 3.4.0
    IBMConcert
    • < 3.0.0
    • 3.0.0
    OracleConstruction and Engineering
    • 21.12.0.0-21.12.21.8
    • 22.12.0.0-22.12.21.3
    • 23.12.0.0-23.12.19.0
    • 24.12.0.0-24.12.15.0
    • 25.12.0.0-25.12.6.0
    • —
    • —
    • —
    • —
    • —
    Red HatEnterprise Linux
    • Apicurio Registry <3.3.1 GA
    • —
    npmdompurify
    • —
    • —
    From bundled advisories, not CVE-specific (5)

    Product list of a bundled advisory that does not state which product this CVE affects.

    Products from bundled advisories
    VendorProductAffected versionsFixed in
    IBMApp Connect Enterprise
    • 12.0.1.0-12.0.12.25
    • 13.0.1.0-13.0.7.1
    • —
    • —
    IBMApp Connect Enterprise Certified Container Operator
    • < 12.0.23
    • < 13.1.0
    • 12.0.23
    • 13.1.0
    Red HatEnterprise Linux
    • 9 Multicluster Engine for Kubernetes 2.8.6
    • —

    Weakness classes (CWE)

    • CWE-183Permissive List of Allowed Inputs

      Base

      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.

      Entry at MITRE CWE-183
    • CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

      Base

      The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

      Entry at MITRE CWE-79

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    SourceReferenceMaturityPublished
    Reference tagged as exploitgithub.com (opens in a new tab)PoC (publicly reported)reported, not verified—

    References & sources

    • github.comcure53/DOMPurify/security/advisories/GHSA-h7mw-gpvr-xq4mweb, x_refsource_CONFIRM, Exploit, Mitigation, Patch, Vendor advisory
    • NVD (NIST)vuln/detail/CVE-2026-41240advisory
    • github.comcure53/DOMPurify/commit/c361baa18dbdcb3344a41110f4c48ad85bf48f80web, x_refsource_MISC, Patch
    • github.comcure53/DOMPurifypackage
    • github.comcure53/DOMPurify/releases/tag/3.4.0web, x_refsource_MISC, Product, Release notes

    Linked CVEs

    Linked CVEs
    SeverityCVETitleCVSSExploitation
    MediumCVE-2026-41240Cure53 DOMPurify: Permissive List of Allowed Inputs6.1—
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-41240
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-41240"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-41240.svg?lang=en" alt="CVE-2026-41240 – NEOSEC Intel" height="20"></a>