CVE-2026-49212: symfony/ux-live-component: LiveComponentHydrator HMAC checksum lacks component and slot binding
Description In symfony/ux-live-component, a component's server-side state is exposed to the browser as a set of props (#[LiveProp]-annotated properties). Props marked writable: true can be freely changed by the client. Read-only props are round-tripped to the browser and back, and their integrity is protected by an HMAC so the client cannot tamper with them.
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
In symfony/ux-live-component, a component's server-side state is exposed to the browser as a set of props (#[LiveProp]-annotated properties). Props marked writable: true can be freely changed by the client. Read-only props are round-tripped to the browser and back, and their integrity is protected by an HMAC so the client cannot tamper with them. Child components additionally receive a propsFromParent blob, also HMAC-signed.
The HMAC computed by Symfony\UX\LiveComponent\LiveComponentHydrator covered only the sorted prop key/value pairs. It didn't include the component name, the slot identifier (props vs propsFromParent), or any request context, and a single application-wide secret is used for every component. A signed blob the server minted for component A is therefore a valid signature for component B if the key names happen to match, and a props blob can be replayed in the propsFromParent slot (or the reverse). An attacker can use this to set a read-only prop on a target component to a value they were only ever allowed to choose as a writable prop on another component.
Resolution
The HMAC is now bound to its context: the component name and a slot identifier are included in the pre-image before hashing. Two constants (CHECKSUM_SLOT_PROPS and CHECKSUM_SLOT_PROPS_FROM_PARENT) name the two slots, and calculateChecksum(), verifyChecksum(), addChecksumToData(), and ChildComponentPartialRenderer thread these values through. Cross-component and cross-slot replays no longer verify.
The patch for this issue is available here for branch 2.x (and forward-ported to 3.x).
Credits
Symfony would like to thank Anthropic (via Project Glasswing) for reporting the issue and Hugo Alliaume for providing the fix.
Credited to Kocal.
References
- https://github.com/symfony/ux/security/advisories/GHSA-34w5-c283-j9fg
- https://github.com/symfony/ux/commit/a224b5af3e2e33ee14ac71356ae0e0877900a81c
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/ux-live-component/CVE-2026-49212.yaml
- https://github.com/advisories/GHSA-34w5-c283-j9fg
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-49210
symfony/ux-live-component: XSS via attacker-controlled child component tag
medium5.1Jun 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
