{"items":[{"id":"NVI-00004327","kind":"vulnerability","title":"symfony/ux-live-component: LiveComponentHydrator HMAC checksum lacks component and slot binding","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-34w5-c283-j9fg","CVE-2026-49212"],"plain_summary":"OSV carries this publisher advisory for symfony/ux-live-component, symfony/ux-live-component. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.36.0 for symfony/ux-live-component. Confirm the publisher’s latest guidance.","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.1.0 for symfony/ux-live-component. Confirm the publisher’s latest guidance.","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-3b2f3199e100c895c69b521d013e1026"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-24T20:10:00.137Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-a1606b2638d91dac4cff47669d398988"},{"kind":"CVSS","as_of":"2026-10-24T20:10:00.137Z","value":"6.9 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-a1606b2638d91dac4cff47669d398988"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.242%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.1536. Missing scores are unknown.","source_id":"sr-3b2f3199e100c895c69b521d013e1026"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-620f2c87745c9a69dcba2ce47bbe4857","url":"https://github.com/advisories/GHSA-34w5-c283-j9fg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-34w5-c283-j9fg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.650Z"},{"id":"sr-a1606b2638d91dac4cff47669d398988","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49212","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-49212","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"},{"id":"sr-3b2f3199e100c895c69b521d013e1026","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-49212","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.281Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### 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 an","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### 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 an","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.1.0"]}],"null_published_at":"2026-11-08T19:53:48.760Z","source_updated_at":"2026-09-10T03:51:07.649Z","source_disclosed_at":"2026-06-19T19:34:56.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:49.650Z"},{"id":"NVI-00004327","kind":"vulnerability","title":"symfony/ux-live-component: LiveComponentHydrator HMAC checksum lacks component and slot binding","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-34w5-c283-j9fg","CVE-2026-49212"],"plain_summary":"OSV carries this publisher advisory for symfony/ux-live-component, symfony/ux-live-component. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.36.0 for symfony/ux-live-component. Confirm the publisher’s latest guidance.","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.1.0 for symfony/ux-live-component. Confirm the publisher’s latest guidance.","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-2c87d577f26b4dc489c7c1c9577d2f1b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-24T20:10:00.137Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-a1606b2638d91dac4cff47669d398988"},{"kind":"CVSS","as_of":"2026-10-24T20:10:00.137Z","value":"6.9 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-a1606b2638d91dac4cff47669d398988"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.242%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.15366. Missing scores are unknown.","source_id":"sr-2c87d577f26b4dc489c7c1c9577d2f1b"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-620f2c87745c9a69dcba2ce47bbe4857","url":"https://github.com/advisories/GHSA-34w5-c283-j9fg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-34w5-c283-j9fg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.650Z"},{"id":"sr-a1606b2638d91dac4cff47669d398988","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49212","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-49212","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"},{"id":"sr-2c87d577f26b4dc489c7c1c9577d2f1b","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-49212","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### 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 an","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### 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 an","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.1.0"]}],"null_published_at":"2026-11-06T15:18:17.649Z","source_updated_at":"2026-09-10T03:51:07.649Z","source_disclosed_at":"2026-06-19T19:34:56.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:41:49.650Z"},{"id":"NVI-00004327","kind":"vulnerability","title":"symfony/ux-live-component: LiveComponentHydrator HMAC checksum lacks component and slot binding","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-34w5-c283-j9fg","CVE-2026-49212"],"plain_summary":"OSV carries this publisher advisory for symfony/ux-live-component, symfony/ux-live-component. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.36.0 for symfony/ux-live-component. Confirm the publisher’s latest guidance.","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.1.0 for symfony/ux-live-component. Confirm the publisher’s latest guidance.","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-2c87d577f26b4dc489c7c1c9577d2f1b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.242%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.15366. Missing scores are unknown.","source_id":"sr-2c87d577f26b4dc489c7c1c9577d2f1b"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-620f2c87745c9a69dcba2ce47bbe4857","url":"https://github.com/advisories/GHSA-34w5-c283-j9fg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-34w5-c283-j9fg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.650Z"},{"id":"sr-2c87d577f26b4dc489c7c1c9577d2f1b","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-49212","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### 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 an","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### 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 an","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.1.0"]}],"null_published_at":"2026-10-31T22:27:15.276Z","source_updated_at":"2026-09-10T03:51:07.649Z","source_disclosed_at":"2026-06-19T19:34:56.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:49.650Z"},{"id":"NVI-00004327","kind":"vulnerability","title":"symfony/ux-live-component: LiveComponentHydrator HMAC checksum lacks component and slot binding","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-34w5-c283-j9fg","CVE-2026-49212"],"plain_summary":"OSV carries this publisher advisory for symfony/ux-live-component, symfony/ux-live-component. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 2.36.0 for symfony/ux-live-component. Confirm the publisher’s latest guidance.","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.1.0 for symfony/ux-live-component. Confirm the publisher’s latest guidance.","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-620f2c87745c9a69dcba2ce47bbe4857","url":"https://github.com/advisories/GHSA-34w5-c283-j9fg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-34w5-c283-j9fg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.650Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### 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 an","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-620f2c87745c9a69dcba2ce47bbe4857"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### 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 an","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.1.0"]}],"null_published_at":"2026-10-31T22:12:52.642Z","source_updated_at":"2026-09-10T03:51:07.649Z","source_disclosed_at":"2026-06-19T19:34:56.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:49.650Z"}],"next_cursor":null,"snapshot_revision":"42594"}