CVE-2026-66010Disclosure(cure53 / dompurify)

LOWCVSS 5.1 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

DOMPurify before 3.4.12 fails to execute afterSanitizeElements hook for custom elements allowed via CUSTOM_ELEMENT_HANDLING.tagNameCheck, allowing attributes to bypass application security policies. Attackers can preserve sensitive attributes on custom elements that later re-inject them into innerHTML sinks, creating second-order XSS gadgets.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-79

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

NONE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • dompurify

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 1 total mentions across 1 day

Affected systems

Vendors
Products
dompurify

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-07-24: 1Technical Details · 2026-07-24: 107-24
Signal classification1 categories
Disclosure
1100.0%
Referenced assets1 URL
By indicator
Full discourse1 post
  • Vulmon Vulnerability Feed@VulmonFeeds
    Disclosure

    CVE-2026-66010 DOMPurify Before 3.4.12 Attribute Bypass in Custom Elements Allows Second-Order XSS https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-66010

    Post summary

    This entry reports the disclosure of an attribute bypass in DOMPurify (versions before 3.4.ылара) that permits second‑order XSS in custom elements, with no PoC, exploit, active exploitation, or patch information provided.

    00000101
    4.1K followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appcure53dompurify---

Explore more