CVE-2026-49215: CWE-352: Cross-Site Request Forgery (CSRF) in symfony ux
Symfony UX is a JavaScript ecosystem for Symfony. From 2.22.0 until 2.36.0 and 3.1.0, Symfony\UX\LiveComponent\EventListener\LiveComponentSubscriber::isLiveComponentRequest() gates #[LiveAction] invocations on Accept: application/vnd.live-component+html, but the Accept header is CORS-safelisted and cross-origin fetch() can set it without preflight, allowing forged cross-origin #[LiveAction] requests against a victim session when applications use SameSite=None, credentials: 'include', a permissive cookie policy, or a same-origin pivot. This issue is fixed in versions 2.36.0 and 3.1.0.
AI Analysis
Technical Summary
Symfony UX's LiveComponentSubscriber::isLiveComponentRequest() method gates #[LiveAction] invocations based on the Accept header being 'application/vnd.live-component+html'. However, since this Accept header is CORS-safelisted, cross-origin fetch() calls can set it without triggering a preflight request. When applications use SameSite=None cookies with credentials: 'include', or have permissive cookie policies or same-origin pivots, this allows an attacker to forge cross-origin #[LiveAction] requests against a victim's session, resulting in a CSRF vulnerability. The issue is resolved in Symfony UX versions 2.36.0 and 3.1.0.
Potential Impact
An attacker can perform forged cross-origin LiveAction requests against a victim's session under specific cookie and credential configurations, potentially causing unintended actions in the affected application. The CVSS score is low (2.1), indicating limited impact and exploitability conditions.
Mitigation Recommendations
Upgrade Symfony UX to version 2.36.0 or later, or 3.1.0 or later, where this vulnerability is fixed. There is no official patch or temporary fix indicated beyond upgrading. If upgrading is not immediately possible, review cookie policies and credential usage to reduce exposure, but the primary mitigation is to apply the fixed versions.
CVE-2026-49215: CWE-352: Cross-Site Request Forgery (CSRF) in symfony ux
Description
Symfony UX is a JavaScript ecosystem for Symfony. From 2.22.0 until 2.36.0 and 3.1.0, Symfony\UX\LiveComponent\EventListener\LiveComponentSubscriber::isLiveComponentRequest() gates #[LiveAction] invocations on Accept: application/vnd.live-component+html, but the Accept header is CORS-safelisted and cross-origin fetch() can set it without preflight, allowing forged cross-origin #[LiveAction] requests against a victim session when applications use SameSite=None, credentials: 'include', a permissive cookie policy, or a same-origin pivot. This issue is fixed in versions 2.36.0 and 3.1.0.
CVSS v4.0
Score 2.1low
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
Symfony UX's LiveComponentSubscriber::isLiveComponentRequest() method gates #[LiveAction] invocations based on the Accept header being 'application/vnd.live-component+html'. However, since this Accept header is CORS-safelisted, cross-origin fetch() calls can set it without triggering a preflight request. When applications use SameSite=None cookies with credentials: 'include', or have permissive cookie policies or same-origin pivots, this allows an attacker to forge cross-origin #[LiveAction] requests against a victim's session, resulting in a CSRF vulnerability. The issue is resolved in Symfony UX versions 2.36.0 and 3.1.0.
Potential Impact
An attacker can perform forged cross-origin LiveAction requests against a victim's session under specific cookie and credential configurations, potentially causing unintended actions in the affected application. The CVSS score is low (2.1), indicating limited impact and exploitability conditions.
Mitigation Recommendations
Upgrade Symfony UX to version 2.36.0 or later, or 3.1.0 or later, where this vulnerability is fixed. There is no official patch or temporary fix indicated beyond upgrading. If upgrading is not immediately possible, review cookie policies and credential usage to reduce exposure, but the primary mitigation is to apply the fixed versions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-28T03:42:34.341Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5b5eb42d1edb114c7fb5db
Added to database: 07/18/2026, 11:08:36 UTC
Last enriched: 07/18/2026, 11:58:24 UTC
Last updated: 07/18/2026, 13:31:12 UTC
Views: 5
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.