CVE-2026-41886: locize Client SDK: Cross-origin DOM XSS & Handler Hijack Through Missing e.origin Validation in InContext Editor
(updated )
Versions of the locize client SDK (the browser module that wires up the locize InContext translation editor) prior to 4.0.21 register a window.addEventListener("message", …) handler that dispatches to registered internal handlers (editKey, commitKey, commitKeys, isLocizeEnabled, requestInitialize, …) without validating event.origin.
The pre-patch listener in src/api/postMessage.js gates dispatch on event.data.sender === "i18next-editor-frame" — that value sits inside the attacker-controlled message payload, not the browser-enforced origin. Any web page that could embed or be embedded by a locize-enabled host — an iframe on a third-party page, a window.open-ed victim, a parent frame reaching down — could send a crafted postMessage and trigger the internal handlers.
References
- developer.mozilla.org/en-US/docs/Web/API/Window/postMessage
- github.com/advisories/GHSA-w937-fg2h-xhq2
- github.com/locize/locize
- github.com/locize/locize/commit/d006b75fadb8e8ab77b023e462850fc6e9170735
- github.com/locize/locize/releases/tag/v4.0.21
- github.com/locize/locize/security/advisories/GHSA-w937-fg2h-xhq2
- nvd.nist.gov/vuln/detail/CVE-2026-41886
Code Behaviors & Features
Detect and mitigate CVE-2026-41886 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →