Skip to main content
Mallory
← Back to News
endpoint-software-vulnerabilitywidely-deployed-product-advisory

Browser Sanitizer APIs Strengthen XSS Defenses After Chrome Bypasses

Vulnerability Disclosure · 2 sources · Updated 3mo ago · First seen Apr 7, 2026

Browser Sanitizer APIs Strengthen XSS Defenses After Chrome Bypasses

Mozilla introduced setHTML in Firefox 148 as a safer alternative to innerHTML, using built-in HTML sanitization to reduce cross-site scripting (XSS) exposure when applications insert untrusted markup. The change aims to give developers a browser-native mechanism that avoids unsafe parsing and rendering patterns associated with direct HTML injection.

Researchers also identified two XSS bypasses in Chrome 146's Sanitizer API implementation. One used SVG animation and the malformed namespaced attribute xlink:href:x to evade an attribute-blocking check; another allowed an invalid javascript: URL that GET-form URL rewriting converted into executable JavaScript. Chrome remediated both flaws in version 147, released April 7, 2026; organizations should ensure managed Chrome deployments are updated and treat browser sanitization APIs as defense-in-depth rather than a substitute for contextual output encoding and input controls.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Feb 26, 2026 – Apr 7, 2026
  1. Apr 7, 20268mo ago

    Chrome 147 releases fixes for two Sanitizer API XSS bypasses

    Chrome 147 was released with fixes for both Sanitizer API XSS bypasses: the malformed SVG `xlink:href` animation bypass and the invalid JavaScript form-action URL bypass.

    Two Bypasses for Chrome's Sanitizer API
  2. Mar 3, 20269mo ago

    Chrome lands JavaScript-URL Sanitizer API fix

    A patch to the `ProtocolIsJavaScript` handling landed to address a second Sanitizer API bypass involving invalid JavaScript URLs that could become executable after GET-form URL rewriting.

    Two Bypasses for Chrome's Sanitizer API
  3. Mar 1, 20269mo ago

    Chrome patches malformed xlink:href Sanitizer API bypass

    Chrome patched the SVG animation bypass by using the SVG attribute parser instead of a direct string comparison when filtering animation attributes.

    Two Bypasses for Chrome's Sanitizer API
  4. Feb 26, 20269mo ago

    Chrome receives report of SVG Sanitizer API XSS bypass

    A bypass affecting Chrome 146's Sanitizer API was reported. It used an SVG animation element with a malformed `attributeName="xlink:href:x"` value to evade filtering and animate an SVG link to a `javascript:` URL.

    Two Bypasses for Chrome's Sanitizer API
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.