{"items":[{"id":"NVI-00006896","kind":"vulnerability","title":"ux-live-component: Format-less date LiveProps parsed with the permissive DateTime constructor","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-89g7-22c8-3j23","CVE-2026-49208"],"plain_summary":"GitHub lists this reviewed advisory for symfony/ux-live-component, symfony/ux-live-component. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-5046d11098d1d0d97800826899df8ba8"],"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},{"summary":"The original advisory lists fixed boundaries 2.36.0 for symfony/ux-live-component. Confirm the publisher’s latest guidance.","source_ids":["sr-c6308eb9f5bb8d8b130bfe24adaf02a0"],"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-c6308eb9f5bb8d8b130bfe24adaf02a0"],"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":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.412%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.35456. Missing scores are unknown.","source_id":"sr-5046d11098d1d0d97800826899df8ba8"}],"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-4d69c2297a04e7f1ea1c4e31afbcf808","url":"https://github.com/advisories/GHSA-89g7-22c8-3j23","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-89g7-22c8-3j23","publisher":"GitHub Advisory Database","observed_at":"2026-11-06T07:19:16.585Z"},{"id":"sr-c6308eb9f5bb8d8b130bfe24adaf02a0","url":"https://github.com/advisories/GHSA-89g7-22c8-3j23","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-89g7-22c8-3j23","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.959Z"},{"id":"sr-5046d11098d1d0d97800826899df8ba8","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-49208","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.381Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4d69c2297a04e7f1ea1c4e31afbcf808"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a `#[LiveProp]` is typed as a `DateTimeInterface` and no explicit `format` is configured, `Symfony\\UX\\LiveComponent\\LiveComponentHydrator::hydrateObjectValue()` falls back to `new $className($value)`. The `DateTime` / `DateTimeImmutable` constructors accept relative strings such as `\"now\"`, `\"tomorrow\"`, or `\"+10 years\"`, so a writable, format-less date prop can be pushed to an arbitrary point in time by the client. Components that rely on a date prop to gate time-based business logic can be moved past those checks by a frontend payload that no maintainer would consider a valid date.\n\n### Resolution\n\n`hydrateObjectValue()` now parses format-less date props strictly with `createFromFormat(DateTimeInterface::RFC3339, ...)`, matching the format already emitted by `dehydrateObjectValue()`. Normal round-trips are unaffected; only inputs that aren't valid RFC 3339 are now rejected, which is consistent with how a format-configured prop already behaved.\n\nThe patch for this issue is available here for branch 2.x (and forward-ported to 3.x).\n\n### Credits\n\nSymfony would like to thank Pascal ","public_affected_ranges":[">= 2.8.0, < 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-4d69c2297a04e7f1ea1c4e31afbcf808"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a `#[LiveProp]` is typed as a `DateTimeInterface` and no explicit `format` is configured, `Symfony\\UX\\LiveComponent\\LiveComponentHydrator::hydrateObjectValue()` falls back to `new $className($value)`. The `DateTime` / `DateTimeImmutable` constructors accept relative strings such as `\"now\"`, `\"tomorrow\"`, or `\"+10 years\"`, so a writable, format-less date prop can be pushed to an arbitrary point in time by the client. Components that rely on a date prop to gate time-based business logic can be moved past those checks by a frontend payload that no maintainer would consider a valid date.\n\n### Resolution\n\n`hydrateObjectValue()` now parses format-less date props strictly with `createFromFormat(DateTimeInterface::RFC3339, ...)`, matching the format already emitted by `dehydrateObjectValue()`. Normal round-trips are unaffected; only inputs that aren't valid RFC 3339 are now rejected, which is consistent with how a format-configured prop already behaved.\n\nThe patch for this issue is available here for branch 2.x (and forward-ported to 3.x).\n\n### Credits\n\nSymfony would like to thank Pascal ","public_affected_ranges":[">= 3.0.0, < 3.1.0"]},{"certainty":"source_listed","source_ids":["sr-c6308eb9f5bb8d8b130bfe24adaf02a0"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a `#[LiveProp]` is typed as a `DateTimeInterface` and no explicit `format` is configured, `Symfony\\UX\\LiveComponent\\LiveComponentHydrator::hydrateObjectValue()` falls back to `new $className($value)`. The `DateTime` / `DateTimeImmutable` constructors accept relative strings such as `\"now\"`, `\"tomorrow\"`, or `\"+10 years\"`, so a writable, format-less date prop can be pushed to an arbitrary point in time by the client. Components that rely on a date prop to gate time-based business logic can be moved past those checks by a frontend payload that no maintainer would consider a valid date.\n\n### Resolution\n\n`hydrateObjectValue()` now parses format-less date props strictly with `createFromFormat(DateTimeInterface::RFC3339, ...)`, matching the format already emitted by `dehydrateObjectValue()`. Normal round-trips are unaffected; only inputs that aren't valid RFC 3339 are now rejected, which is consistent with how a format-configured prop already behaved.\n\nThe patch for this issue is available here for branch 2.x (and forward-ported to 3.x).\n\n### Credits\n\nSymfony would like to thank Pascal ","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-c6308eb9f5bb8d8b130bfe24adaf02a0"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a `#[LiveProp]` is typed as a `DateTimeInterface` and no explicit `format` is configured, `Symfony\\UX\\LiveComponent\\LiveComponentHydrator::hydrateObjectValue()` falls back to `new $className($value)`. The `DateTime` / `DateTimeImmutable` constructors accept relative strings such as `\"now\"`, `\"tomorrow\"`, or `\"+10 years\"`, so a writable, format-less date prop can be pushed to an arbitrary point in time by the client. Components that rely on a date prop to gate time-based business logic can be moved past those checks by a frontend payload that no maintainer would consider a valid date.\n\n### Resolution\n\n`hydrateObjectValue()` now parses format-less date props strictly with `createFromFormat(DateTimeInterface::RFC3339, ...)`, matching the format already emitted by `dehydrateObjectValue()`. Normal round-trips are unaffected; only inputs that aren't valid RFC 3339 are now rejected, which is consistent with how a format-configured prop already behaved.\n\nThe patch for this issue is available here for branch 2.x (and forward-ported to 3.x).\n\n### Credits\n\nSymfony would like to thank Pascal ","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.1.0"]}],"null_published_at":"2026-11-07T07:07:42.453Z","source_updated_at":"2026-06-19T19:23:56.000Z","source_disclosed_at":"2026-06-19T19:23:55.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:59.959Z"},{"id":"NVI-00006896","kind":"vulnerability","title":"ux-live-component: Format-less date LiveProps parsed with the permissive DateTime constructor","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-89g7-22c8-3j23","CVE-2026-49208"],"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-c6308eb9f5bb8d8b130bfe24adaf02a0"],"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-c6308eb9f5bb8d8b130bfe24adaf02a0"],"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-5046d11098d1d0d97800826899df8ba8"],"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.412%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.35456. Missing scores are unknown.","source_id":"sr-5046d11098d1d0d97800826899df8ba8"}],"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-c6308eb9f5bb8d8b130bfe24adaf02a0","url":"https://github.com/advisories/GHSA-89g7-22c8-3j23","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-89g7-22c8-3j23","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.959Z"},{"id":"sr-5046d11098d1d0d97800826899df8ba8","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-49208","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.381Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c6308eb9f5bb8d8b130bfe24adaf02a0"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a `#[LiveProp]` is typed as a `DateTimeInterface` and no explicit `format` is configured, `Symfony\\UX\\LiveComponent\\LiveComponentHydrator::hydrateObjectValue()` falls back to `new $className($value)`. The `DateTime` / `DateTimeImmutable` constructors accept relative strings such as `\"now\"`, `\"tomorrow\"`, or `\"+10 years\"`, so a writable, format-less date prop can be pushed to an arbitrary point in time by the client. Components that rely on a date prop to gate time-based business logic can be moved past those checks by a frontend payload that no maintainer would consider a valid date.\n\n### Resolution\n\n`hydrateObjectValue()` now parses format-less date props strictly with `createFromFormat(DateTimeInterface::RFC3339, ...)`, matching the format already emitted by `dehydrateObjectValue()`. Normal round-trips are unaffected; only inputs that aren't valid RFC 3339 are now rejected, which is consistent with how a format-configured prop already behaved.\n\nThe patch for this issue is available here for branch 2.x (and forward-ported to 3.x).\n\n### Credits\n\nSymfony would like to thank Pascal ","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-c6308eb9f5bb8d8b130bfe24adaf02a0"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a `#[LiveProp]` is typed as a `DateTimeInterface` and no explicit `format` is configured, `Symfony\\UX\\LiveComponent\\LiveComponentHydrator::hydrateObjectValue()` falls back to `new $className($value)`. The `DateTime` / `DateTimeImmutable` constructors accept relative strings such as `\"now\"`, `\"tomorrow\"`, or `\"+10 years\"`, so a writable, format-less date prop can be pushed to an arbitrary point in time by the client. Components that rely on a date prop to gate time-based business logic can be moved past those checks by a frontend payload that no maintainer would consider a valid date.\n\n### Resolution\n\n`hydrateObjectValue()` now parses format-less date props strictly with `createFromFormat(DateTimeInterface::RFC3339, ...)`, matching the format already emitted by `dehydrateObjectValue()`. Normal round-trips are unaffected; only inputs that aren't valid RFC 3339 are now rejected, which is consistent with how a format-configured prop already behaved.\n\nThe patch for this issue is available here for branch 2.x (and forward-ported to 3.x).\n\n### Credits\n\nSymfony would like to thank Pascal ","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.1.0"]}],"null_published_at":"2026-10-31T23:18:17.289Z","source_updated_at":"2026-09-10T03:50:48.829Z","source_disclosed_at":"2026-06-19T19:23:55.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:59.959Z"},{"id":"NVI-00006896","kind":"vulnerability","title":"ux-live-component: Format-less date LiveProps parsed with the permissive DateTime constructor","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-89g7-22c8-3j23","CVE-2026-49208"],"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-c6308eb9f5bb8d8b130bfe24adaf02a0"],"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-c6308eb9f5bb8d8b130bfe24adaf02a0"],"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-c6308eb9f5bb8d8b130bfe24adaf02a0","url":"https://github.com/advisories/GHSA-89g7-22c8-3j23","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-89g7-22c8-3j23","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.959Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-c6308eb9f5bb8d8b130bfe24adaf02a0"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a `#[LiveProp]` is typed as a `DateTimeInterface` and no explicit `format` is configured, `Symfony\\UX\\LiveComponent\\LiveComponentHydrator::hydrateObjectValue()` falls back to `new $className($value)`. The `DateTime` / `DateTimeImmutable` constructors accept relative strings such as `\"now\"`, `\"tomorrow\"`, or `\"+10 years\"`, so a writable, format-less date prop can be pushed to an arbitrary point in time by the client. Components that rely on a date prop to gate time-based business logic can be moved past those checks by a frontend payload that no maintainer would consider a valid date.\n\n### Resolution\n\n`hydrateObjectValue()` now parses format-less date props strictly with `createFromFormat(DateTimeInterface::RFC3339, ...)`, matching the format already emitted by `dehydrateObjectValue()`. Normal round-trips are unaffected; only inputs that aren't valid RFC 3339 are now rejected, which is consistent with how a format-configured prop already behaved.\n\nThe patch for this issue is available here for branch 2.x (and forward-ported to 3.x).\n\n### Credits\n\nSymfony would like to thank Pascal ","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-c6308eb9f5bb8d8b130bfe24adaf02a0"],"technology":"symfony/ux-live-component","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a `#[LiveProp]` is typed as a `DateTimeInterface` and no explicit `format` is configured, `Symfony\\UX\\LiveComponent\\LiveComponentHydrator::hydrateObjectValue()` falls back to `new $className($value)`. The `DateTime` / `DateTimeImmutable` constructors accept relative strings such as `\"now\"`, `\"tomorrow\"`, or `\"+10 years\"`, so a writable, format-less date prop can be pushed to an arbitrary point in time by the client. Components that rely on a date prop to gate time-based business logic can be moved past those checks by a frontend payload that no maintainer would consider a valid date.\n\n### Resolution\n\n`hydrateObjectValue()` now parses format-less date props strictly with `createFromFormat(DateTimeInterface::RFC3339, ...)`, matching the format already emitted by `dehydrateObjectValue()`. Normal round-trips are unaffected; only inputs that aren't valid RFC 3339 are now rejected, which is consistent with how a format-configured prop already behaved.\n\nThe patch for this issue is available here for branch 2.x (and forward-ported to 3.x).\n\n### Credits\n\nSymfony would like to thank Pascal ","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.1.0"]}],"null_published_at":"2026-10-31T22:13:14.302Z","source_updated_at":"2026-09-10T03:50:48.829Z","source_disclosed_at":"2026-06-19T19:23:55.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:59.959Z"}],"next_cursor":null,"snapshot_revision":"42594"}