CVE-2026-49210: Symfony UX: XSS in symfony/ux-live-component via attacker-controlled child component tag

Published Jun 19, 2026
·
Updated

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.

Other sources

Symfony UX is a JavaScript ecosystem for Symfony. From 2.8.0 until 2.36.0 and 3.1.0, Symfony\UX\LiveComponent\Util\ChildComponentPartialRenderer::createHtml() interpolates the client-controlled children[id].tag value from LiveComponentSubscriber and InterceptChildComponentRenderSubscriber directly into HTML as a tag name without escaping or validation, allowing arbitrary HTML, including <script> tags, on any Live Component re-render that contains at least one child component. This issue is fixed in versions 2.36.0 and 3.1.0.

MITRE

Affected Software

4 affected componentsFixes available
composer/symfony/ux-live-component>=3.0.0<3.1.0
3.1.0
composer/symfony/ux-live-component>=2.8.0<2.36.0
2.36.0
Symfony UX>=2.8.0<2.36.0
Symfony UX=3.0.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/symfony/ux-live-component to a version that resolves this vulnerability.

    Fixed in 3.1.0
  2. Upgrade

    Upgrade composer/symfony/ux-live-component to a version that resolves this vulnerability.

    Fixed in 2.36.0
  3. Upgrade

    Upgrade Symfony UX live-component (symfony/ux-live-component) to a version that resolves this vulnerability.

    Fixed in 2.36.0
  4. Upgrade

    Upgrade Symfony UX live-component (symfony/ux-live-component) to a version that resolves this vulnerability.

    Fixed in 3.1.0
  5. Compensating control

    Keep the Live Component endpoint gated by the `Accept: application/vnd.live-component+html` request-header check, and avoid relaxing CORS to allow this header from untrusted origins (otherwise the attacker can reach the Live Component endpoint and inject arbitrary HTML via attacker-controlled `children[id].tag`).

Event History

Jun 19, 2026
Advisory Published
via GitHub·07:34 PM
Data Sourced
via GitHub·07:34 PM
DescriptionWeaknessAffected Software
Jul 17, 2026
CVE Published
via MITRE·04:09 PM
Data Sourced
via MITRE·04:09 PM
DescriptionWeakness
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-49210?

The severity of CVE-2026-49210 is classified as low with a CVSS score of 4.0.

2

What does CVE-2026-49210 exploit?

CVE-2026-49210 exploits a cross-site scripting (XSS) vulnerability in Symfony UX through attacker-controlled child component tags.

3

How do I fix CVE-2026-49210?

To fix CVE-2026-49210, update to the latest version of symfony/ux-live-component where the vulnerability has been addressed.

4

What is affected by CVE-2026-49210?

CVE-2026-49210 affects versions of composer/symfony/ux-live-component that allow unvalidated input to create HTML output.

5

Is CVE-2026-49210 a high-risk vulnerability?

CVE-2026-49210 is not considered high-risk due to its low severity rating, but it still poses a potential XSS threat.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203