Symfony UX is a JavaScript ecosystem for Symfony. From 2.8.0 until 2.36.0 and 3.1.0, when a #[LiveProp] is typed as DateTimeInterface and no explicit format is configured, Symfony\UX\LiveComponent\LiveComponentHydrator::hydrateObjectValue() falls back to new $className($value), allowing client-supplied relative strings such as now, tomorrow, or +10 years to move a writable, format-less date prop past time-based business logic checks. This issue is fixed in versions 2.36.0 and 3.1.0.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/symfony/ux/commit/d24d78fda6df2d5964312255943ebf3a217b79a2 Patch
- https://github.com/symfony/ux/security/advisories/GHSA-89g7-22c8-3j23 Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.9 · symfonyNVD modified 2026-10-24 20:10
Affected (CPE criteria) 2
cpe:2.3:a:symfony:ux:*:*:*:*:*:*:*:*cpe:2.3:a:symfony:ux:3.0.0:*:*:*:*:*:*:*