CVE-2026-49212: symfony/ux-live-component: LiveComponentHydrator HMAC checksum lacks component and slot binding
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.
References
- github.com/FriendsOfPHP/security-advisories/blob/master/symfony/ux-live-component/CVE-2026-49212.yaml
- github.com/advisories/GHSA-34w5-c283-j9fg
- github.com/symfony/ux/commit/a224b5af3e2e33ee14ac71356ae0e0877900a81c
- github.com/symfony/ux/security/advisories/GHSA-34w5-c283-j9fg
- nvd.nist.gov/vuln/detail/CVE-2026-49212
Code Behaviors & Features
Detect and mitigate CVE-2026-49212 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 →