CVE-2026-49210: symfony/ux-live-component: XSS via attacker-controlled child component tag
Description Symfony\UX\LiveComponent\Util\ChildComponentPartialRenderer::createHtml() interpolates the $childTag argument directly into the HTML output as a tag name, without escaping or validation. The value originates from client-controlled JSON (children[id].tag) parsed by LiveComponentSubscriber and propagated through InterceptChildComponentRenderSubscriber, so an attacker who can reach the Live Component…
Published Jun 19, 2026
Affected packages
symfony/ux-live-component
- Ecosystem
- Composer (PHP)
- Affected
- >= 2.8.0, < 2.36.0
- Fixed in
- 2.36.0
- Check
composer show symfony/ux-live-component
symfony/ux-live-component
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.0.0, < 3.1.0
- Fixed in
- 3.1.0
- Check
composer show symfony/ux-live-component
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Description
Symfony\UX\LiveComponent\Util\ChildComponentPartialRenderer::createHtml() interpolates the $childTag argument directly into the HTML output as a tag name, without escaping or validation. The value originates from client-controlled JSON (children[id].tag) parsed by LiveComponentSubscriber and propagated through InterceptChildComponentRenderSubscriber, so an attacker who can reach the Live Component endpoint can inject arbitrary HTML, including <script> tags, on any re-render of a Live Component that contains at least one child component.
In the default configuration, the Live Component endpoint is gated by an Accept: application/vnd.live-component+html request-header check that cannot be set cross-origin without a CORS preflight, so the issue is primarily a defense-in-depth gap. It becomes directly exploitable on applications that have relaxed CORS to allow this header from untrusted origins, or that have been pivoted from another same-origin XSS.
Resolution
ChildComponentPartialRenderer now validates $childTag against a strict HTML tag-name regex before interpolating it, and rejects any value that doesn't match. Anything that wouldn't be a valid HTML tag is dropped before reaching the response.
The patch for this issue is available here for branch 2.x (and forward-ported to 3.x).
Credits
Symfony would like to thank Pascal Cescon for reporting the issue and Hugo Alliaume for providing the fix.
Credited to Amoifr, Kocal.
References
- https://github.com/symfony/ux/security/advisories/GHSA-38x5-rcv4-xf7x
- https://github.com/symfony/ux/commit/fbc5e9a1bda7e4556be21bb1d970f382760ed9a9
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/ux-live-component/CVE-2026-49210.yaml
- https://github.com/advisories/GHSA-38x5-rcv4-xf7x
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-49208
ux-live-component: Format-less date LiveProps parsed with the permissive DateTime constructor
medium6.9Jun 19, 2026CVE-2026-49209
symfony/ux-live-component: Denial of service via unbounded batch action requests
low1.3Jun 19, 2026CVE-2026-49212
symfony/ux-live-component: LiveComponentHydrator HMAC checksum lacks component and slot binding
low2.3Jun 19, 2026CVE-2026-49215
symfony/ux-live-component: CSRF Protection Bypass — Accept Header is CORS-Safelisted
low2.1Jun 19, 2026CVE-2025-47946
Symfony UX allows unsanitized HTML attribute injection via ComponentAttributes
medium6.1May 19, 2025
