CVE-2026-49212: symfony/ux-live-component LiveComponentHydrator HMAC Checksum Lacks Component Vulnerability

LOW
Advisory Identifier: GHSA-34w5-c283-j9fg
CWE-345
Published
Advisory Summary

CVE-2026-49212 is a LOW livecomponenthydrator hmac checksum lacks component vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting symfony/ux-live-component libraries in the Packagist ecosystem. The issue involves livecomponenthydrator hmac checksum lacks component and slot binding. Remediation is available by upgrading affected packages to version 2.36.0, 3.1.0.

CVE-2026-49212 at a Glance

CVE Identifier CVE-2026-49212
GHSA Identifier GHSA-34w5-c283-j9fg
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product symfony/ux-live-component
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix CVE-2026-49212

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-49212, 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-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. 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 In `symfony/ux-live-component`, a component's server-side state is exposed to the browser as a set of props (`#[LiveProp]`-annotated properties). Props marked `writable: true` can be freely changed by the client. Read-only props are round-tripped to the browser and back, and their integrity is protected by an HMAC so the client cannot tamper with them. Child components additionally receive a `propsFromParent` blob, also HMAC-signed. The HMAC computed by `Symfony\UX\LiveComponent\LiveComponentHydrator` covered only the sorted prop key/value pairs. It didn't include the component name, the slot identifier (`props` vs `propsFromParent`), or any request context, and a single application-wide secret is used for every component. A signed blob the server minted for component A is therefore a valid signature for component B if the key names happen to match, and a `props` blob can be replayed in the `propsFromParent` slot (or the reverse). An attacker can use this to set a read-only prop on a target component to a value they were only ever allowed to choose as a writable prop on another component. ### Resolution The HMAC is now bound to its context: the component name and a slot identifier are included in the pre-image before hashing. Two constants (`CHECKSUM_SLOT_PROPS` and `CHECKSUM_SLOT_PROPS_FROM_PARENT`) name the two slots, and `calculateChecksum()`, `verifyChecksum()`, `addChecksumToData()`, and `ChildComponentPartialRenderer` thread these values through. Cross-component and cross-slot replays no longer verify. The patch for this issue is available [here](https://github.com/symfony/ux/commit/a224b5af3e2e33ee14ac71356ae0e0877900a81c) 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-49212 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.8.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-49212?
CVE-2026-49212 is a security vulnerability in symfony/ux-live-component involving LiveComponentHydrator HMAC checksum lacks component and slot binding under CWE-345: Insufficient Verification of Data Authenticity.
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-49212?
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-49212?
CVE-2026-49212 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check Packagist dependencies for CVE-2026-49212?
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-34w5-c283-j9fg",
  "modified" : "2026-06-19T19:34:56Z",
  "published" : "2026-06-19T19:34:56Z",
  "aliases" : [ "CVE-2026-49212" ],
  "summary" : "symfony/ux-live-component: LiveComponentHydrator HMAC checksum lacks component and slot binding",
  "details" : "### Description\n\nIn `symfony/ux-live-component`, a component's server-side state is exposed to the browser as a set of props (`#[LiveProp]`-annotated properties). Props marked `writable: true` can be freely changed by the client. Read-only props are round-tripped to the browser and back, and their integrity is protected by an HMAC so the client cannot tamper with them. Child components additionally receive a `propsFromParent` blob, also HMAC-signed.\n\nThe HMAC computed by `Symfony\\UX\\LiveComponent\\LiveComponentHydrator` covered only the sorted prop key/value pairs. It didn't include the component name, the slot identifier (`props` vs `propsFromParent`), or any request context, and a single application-wide secret is used for every component. A signed blob the server minted for component A is therefore a valid signature for component B if the key names happen to match, and a `props` blob can be replayed in the `propsFromParent` slot (or the reverse). An attacker can use this to set a read-only prop on a target component to a value they were only ever allowed to choose as a writable prop on another component.\n\n### Resolution\n\nThe HMAC is now bound to its context: the component name and a slot identifier are included in the pre-image before hashing. Two constants (`CHECKSUM_SLOT_PROPS` and `CHECKSUM_SLOT_PROPS_FROM_PARENT`) name the two slots, and `calculateChecksum()`, `verifyChecksum()`, `addChecksumToData()`, and `ChildComponentPartialRenderer` thread these values through. Cross-component and cross-slot replays no longer verify.\n\nThe patch for this issue is available [here](https://github.com/symfony/ux/commit/a224b5af3e2e33ee14ac71356ae0e0877900a81c) 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:H/AT:N/PR:L/UI:N/VC:N/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.8.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-34w5-c283-j9fg"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/symfony/ux/commit/a224b5af3e2e33ee14ac71356ae0e0877900a81c"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/ux-live-component/CVE-2026-49212.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/symfony/ux"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-19T19:34:56Z",
    "nvd_published_at" : null
  }
}