CVE-2026-49208: CWE-20: Improper Input Validation in symfony ux
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.
AI Analysis
Technical Summary
The vulnerability in Symfony UX arises when a #[LiveProp] property typed as DateTimeInterface lacks an explicit format configuration. The LiveComponentHydrator::hydrateObjectValue() method falls back to instantiating a new DateTime object using the client-supplied string directly. This allows relative date strings to be interpreted and accepted, potentially enabling attackers to manipulate date-based logic by supplying values like 'now' or '+10 years'. The flaw affects versions >=2.8.0 <2.36.0 and >=3.0.0 <3.1.0 and has been resolved in 2.36.0 and 3.1.0.
Potential Impact
An attacker can supply relative date strings that bypass intended time-based business logic checks, potentially leading to incorrect application behavior or logic bypass. There is no indication of privilege escalation or remote code execution. The CVSS 4.0 base score is 6.9 (medium severity), indicating a moderate impact with network attack vector and no user interaction required.
Mitigation Recommendations
This vulnerability is fixed in Symfony UX versions 2.36.0 and 3.1.0. Users should upgrade to these versions or later to remediate the issue. No official temporary fixes or workarounds are indicated. Patch status is not explicitly stated as 'patchAvailable' but the vendor fixed the issue in these versions. Therefore, upgrading to the fixed versions is the recommended remediation.
CVE-2026-49208: CWE-20: Improper Input Validation in symfony ux
Description
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.
CVSS v4.0
Score 6.9medium
Affected software
pkg:github/symfony/uxRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Symfony UX arises when a #[LiveProp] property typed as DateTimeInterface lacks an explicit format configuration. The LiveComponentHydrator::hydrateObjectValue() method falls back to instantiating a new DateTime object using the client-supplied string directly. This allows relative date strings to be interpreted and accepted, potentially enabling attackers to manipulate date-based logic by supplying values like 'now' or '+10 years'. The flaw affects versions >=2.8.0 <2.36.0 and >=3.0.0 <3.1.0 and has been resolved in 2.36.0 and 3.1.0.
Potential Impact
An attacker can supply relative date strings that bypass intended time-based business logic checks, potentially leading to incorrect application behavior or logic bypass. There is no indication of privilege escalation or remote code execution. The CVSS 4.0 base score is 6.9 (medium severity), indicating a moderate impact with network attack vector and no user interaction required.
Mitigation Recommendations
This vulnerability is fixed in Symfony UX versions 2.36.0 and 3.1.0. Users should upgrade to these versions or later to remediate the issue. No official temporary fixes or workarounds are indicated. Patch status is not explicitly stated as 'patchAvailable' but the vendor fixed the issue in these versions. Therefore, upgrading to the fixed versions is the recommended remediation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-28T03:42:34.340Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5b5ebc2d1edb114c7fb83d
Added to database: 07/18/2026, 11:08:44 UTC
Last enriched: 07/25/2026, 22:42:08 UTC
Last updated: 08/29/2026, 10:52:09 UTC
Views: 88
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.