CVE-2026-49208: ux-live-component: Format-less date LiveProps parsed with the permissive DateTime constructor
Description When a #[LiveProp] is typed as a DateTimeInterface and no explicit format is configured, Symfony\UX\LiveComponent\LiveComponentHydrator::hydrateObjectValue() falls back to new $className($value). The DateTime / DateTimeImmutable constructors accept relative strings such as "now", "tomorrow", or "+10 years", so a writable, format-less date prop can be pushed to an arbitrary point in time by the client.
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
When a #[LiveProp] is typed as a DateTimeInterface and no explicit format is configured, Symfony\UX\LiveComponent\LiveComponentHydrator::hydrateObjectValue() falls back to new $className($value). The DateTime / DateTimeImmutable constructors accept relative strings such as "now", "tomorrow", or "+10 years", so a writable, format-less date prop can be pushed to an arbitrary point in time by the client. Components that rely on a date prop to gate time-based business logic can be moved past those checks by a frontend payload that no maintainer would consider a valid date.
Resolution
hydrateObjectValue() now parses format-less date props strictly with createFromFormat(DateTimeInterface::RFC3339, ...), matching the format already emitted by dehydrateObjectValue(). Normal round-trips are unaffected; only inputs that aren't valid RFC 3339 are now rejected, which is consistent with how a format-configured prop already behaved.
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-89g7-22c8-3j23
- https://github.com/symfony/ux/commit/d24d78fda6df2d5964312255943ebf3a217b79a2
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/ux-live-component/CVE-2026-49208.yaml
- https://github.com/advisories/GHSA-89g7-22c8-3j23
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-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-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
