CVE-2026-49215: symfony/ux-live-component CSRF Protection Bypass — Accept Vulnerability

LOW
Advisory Identifier: GHSA-4m4j-hmqq-3gxm
CWE-352
Published
Advisory Summary

CVE-2026-49215 is a LOW csrf protection bypass — accept vulnerability (CWE-352: Cross-Site Request Forgery (CSRF)) affecting symfony/ux-live-component libraries in the Packagist ecosystem. The issue involves csrf protection bypass — accept header is cors-safelisted. Remediation is available by upgrading affected packages to version 2.36.0, 3.1.0.

CVE-2026-49215 at a Glance

CVE Identifier CVE-2026-49215
GHSA Identifier GHSA-4m4j-hmqq-3gxm
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-352: Cross-Site Request Forgery (CSRF)
Affected Product symfony/ux-live-component
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix CVE-2026-49215

To remediate this vulnerability, upgrade all affected symfony/ux-live-component dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

symfony/ux-live-component fixed: 2.36.0
Upgrade symfony/ux-live-component to 2.36.0
symfony/ux-live-component fixed: 3.1.0
Upgrade symfony/ux-live-component to 3.1.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for symfony/ux-live-component

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-49215, inspect your project dependencies for symfony/ux-live-component:

inspect dependencies for symfony/ux-live-component

Analyze the terminal output to locate any version of symfony/ux-live-component in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.36.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-352: Cross-Site Request Forgery (CSRF), where the web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. In symfony/ux-live-component, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Description When using `symfony/ux-live-component`, methods annotated with `#[LiveAction]` are invokable from the browser and mutate server-side state via AJAX. `Symfony\UX\LiveComponent\EventListener\LiveComponentSubscriber::isLiveComponentRequest()` gated these invocations on the presence of `Accept: application/vnd.live-component+html`, with a code comment stating that this acted as a CSRF protection. The `Accept` header is a [CORS-safelisted request header](https://fetch.spec.whatwg.org/#cors-safelisted-request-header), so a cross-origin `fetch()` can set it without triggering a preflight. The header therefore provided no CSRF protection. Any `#[LiveAction]` could be forged cross-origin against a victim's session. In practice the attack is mitigated by `SameSite=Lax` session cookies (Symfony's default), but applications using `SameSite=None`, `credentials: 'include'` with a permissive cookie policy, or that have been pivoted from another same-origin vector remained exposed. ### Resolution `isLiveComponentRequest()` now additionally requires the request header `X-Requested-With: XMLHttpRequest`. This header is **not** CORS-safelisted, so the browser issues a preflight `OPTIONS` request for any cross-origin attempt; Symfony does not advertise CORS for LiveComponent endpoints, the preflight fails, and the real request is blocked before it reaches the application. The bundled Stimulus client already sends `X-Requested-With` on every LiveComponent request (`RequestBuilder.ts`), so standard usage is unaffected. Cross-origin callers must add `X-Requested-With` to their CORS `Access-Control-Allow-Headers` allow-list. The patch for this issue is available [here](https://github.com/symfony/ux/commit/aed7493db2b4b7bf1f9c79b33cda544f06904b27) for branch 2.x (and forward-ported to 3.x). ### Credits Symfony would like to thank Anthropic (via Project Glasswing) for reporting the issue and Hugo Alliaume for providing the fix.

CVE-2026-49215 Affected symfony/ux-live-component Versions

2 component(s)
Fixed Versions:
2.36.03.1.0
Product / Package Ecosystem Affected Versions Fixed Version
symfony/ux-live-component
Packagist
≥ 2.22.0
< 2.36.0
2.36.0
symfony/ux-live-component
Packagist
≥ 3.0.0
< 3.1.0
3.1.0

References

Frequently Asked Questions

What is CVE-2026-49215?
CVE-2026-49215 is a security vulnerability in symfony/ux-live-component involving CSRF Protection Bypass — Accept Header is CORS-Safelisted under CWE-352: Cross-Site Request Forgery (CSRF).
Which symfony/ux-live-component versions are affected?
Affected versions include releases prior to 2.36.0, 3.1.0 across affected packages: symfony/ux-live-component.
What version fixes CVE-2026-49215?
Upgrading to 2.36.0, 3.1.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is symfony/ux-live-component affected?
Yes, symfony/ux-live-component is affected in releases prior to 2.36.0, 3.1.0. Upgrade your dependency to 2.36.0, 3.1.0 or later.
What CWE is associated with CVE-2026-49215?
CVE-2026-49215 is classified under CWE-352: Cross-Site Request Forgery (CSRF) (The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.).
How can I check Packagist dependencies for CVE-2026-49215?
Run the dependency tree command: 'inspect dependencies for symfony/ux-live-component'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4m4j-hmqq-3gxm",
  "modified" : "2026-06-19T19:35:01Z",
  "published" : "2026-06-19T19:35:01Z",
  "aliases" : [ "CVE-2026-49215" ],
  "summary" : "symfony/ux-live-component: CSRF Protection Bypass — Accept Header is CORS-Safelisted",
  "details" : "### Description\n\nWhen using `symfony/ux-live-component`, methods annotated with `#[LiveAction]` are invokable from the browser and mutate server-side state via AJAX. `Symfony\\UX\\LiveComponent\\EventListener\\LiveComponentSubscriber::isLiveComponentRequest()` gated these invocations on the presence of `Accept: application/vnd.live-component+html`, with a code comment stating that this acted as a CSRF protection.\n\nThe `Accept` header is a [CORS-safelisted request header](https://fetch.spec.whatwg.org/#cors-safelisted-request-header), so a cross-origin `fetch()` can set it without triggering a preflight. The header therefore provided no CSRF protection. Any `#[LiveAction]` could be forged cross-origin against a victim's session.\n\nIn practice the attack is mitigated by `SameSite=Lax` session cookies (Symfony's default), but applications using `SameSite=None`, `credentials: 'include'` with a permissive cookie policy, or that have been pivoted from another same-origin vector remained exposed.\n\n### Resolution\n\n`isLiveComponentRequest()` now additionally requires the request header `X-Requested-With: XMLHttpRequest`. This header is **not** CORS-safelisted, so the browser issues a preflight `OPTIONS` request for any cross-origin attempt; Symfony does not advertise CORS for LiveComponent endpoints, the preflight fails, and the real request is blocked before it reaches the application. The bundled Stimulus client already sends `X-Requested-With` on every LiveComponent request (`RequestBuilder.ts`), so standard usage is unaffected. Cross-origin callers must add `X-Requested-With` to their CORS `Access-Control-Allow-Headers` allow-list.\n\nThe patch for this issue is available [here](https://github.com/symfony/ux/commit/aed7493db2b4b7bf1f9c79b33cda544f06904b27) for branch 2.x (and forward-ported to 3.x).\n\n### Credits\n\nSymfony would like to thank Anthropic (via Project Glasswing) for reporting the issue and Hugo Alliaume for providing the fix.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "symfony/ux-live-component"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.22.0"
      }, {
        "fixed" : "2.36.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "symfony/ux-live-component"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.1.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/symfony/ux/security/advisories/GHSA-4m4j-hmqq-3gxm"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/symfony/ux/commit/aed7493db2b4b7bf1f9c79b33cda544f06904b27"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/ux-live-component/CVE-2026-49215.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/symfony/ux"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-352" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-19T19:35:01Z",
    "nvd_published_at" : null
  }
}