{"items":[{"id":"NVI-00002908","kind":"vulnerability","title":"Symfony possible session fixation vulnerability","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-m2wj-r6g3-fxfx","CVE-2023-46733"],"plain_summary":"OSV carries this publisher advisory for symfony/security-http, symfony/security-http, symfony/symfony, symfony/symfony. 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 5.4.31 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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 6.3.8 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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 5.4.31 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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 6.3.8 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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-24bd0a9124fccbd9c10d9be2e7d03ddb"],"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-06-17T06:31:26.587Z","value":"6.5 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-db26e167cda538cd89b23959e9ca67e8"},{"kind":"CVSS","as_of":"2026-06-17T06:31:26.587Z","value":"6.5 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-db26e167cda538cd89b23959e9ca67e8"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.689%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.52808. Missing scores are unknown.","source_id":"sr-24bd0a9124fccbd9c10d9be2e7d03ddb"}],"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-2b4589d1438363247f133ee308638464","url":"https://github.com/advisories/GHSA-m2wj-r6g3-fxfx","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m2wj-r6g3-fxfx","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.972Z"},{"id":"sr-db26e167cda538cd89b23959e9ca67e8","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-46733","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2023-46733","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:58:51.607Z"},{"id":"sr-24bd0a9124fccbd9c10d9be2e7d03ddb","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-2023-46733","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:42:56.080Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 5.4.21; fixed 5.4.31"]},{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 6.2.7; fixed 6.3.8"]},{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 5.4.21; fixed 5.4.31"]},{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 6.2.7; fixed 6.3.8"]}],"null_published_at":"2026-11-08T19:53:33.545Z","source_updated_at":"2026-09-10T03:50:04.290Z","source_disclosed_at":"2023-11-12T15:51:54.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:42:30.972Z"},{"id":"NVI-00002908","kind":"vulnerability","title":"Symfony possible session fixation vulnerability","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-m2wj-r6g3-fxfx","CVE-2023-46733"],"plain_summary":"OSV carries this publisher advisory for symfony/security-http, symfony/security-http, symfony/symfony, symfony/symfony. 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 5.4.31 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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 6.3.8 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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 5.4.31 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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 6.3.8 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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-1a760c57b4faf825828cfdcb57d47a89"],"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-06-17T06:31:26.587Z","value":"6.5 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-db26e167cda538cd89b23959e9ca67e8"},{"kind":"CVSS","as_of":"2026-06-17T06:31:26.587Z","value":"6.5 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-db26e167cda538cd89b23959e9ca67e8"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.689%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.52775. Missing scores are unknown.","source_id":"sr-1a760c57b4faf825828cfdcb57d47a89"}],"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-2b4589d1438363247f133ee308638464","url":"https://github.com/advisories/GHSA-m2wj-r6g3-fxfx","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m2wj-r6g3-fxfx","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.972Z"},{"id":"sr-db26e167cda538cd89b23959e9ca67e8","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-46733","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2023-46733","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:58:51.607Z"},{"id":"sr-1a760c57b4faf825828cfdcb57d47a89","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-2023-46733","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:27:48.610Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 5.4.21; fixed 5.4.31"]},{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 6.2.7; fixed 6.3.8"]},{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 5.4.21; fixed 5.4.31"]},{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 6.2.7; fixed 6.3.8"]}],"null_published_at":"2026-11-07T22:29:23.459Z","source_updated_at":"2026-09-10T03:50:04.290Z","source_disclosed_at":"2023-11-12T15:51:54.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:42:30.972Z"},{"id":"NVI-00002908","kind":"vulnerability","title":"Symfony possible session fixation vulnerability","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m2wj-r6g3-fxfx","CVE-2023-46733"],"plain_summary":"OSV carries this publisher advisory for symfony/security-http, symfony/security-http, symfony/symfony, symfony/symfony. 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 5.4.31 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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 6.3.8 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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 5.4.31 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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 6.3.8 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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-1a760c57b4faf825828cfdcb57d47a89"],"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-11-01T12:00:16.000Z","value":"0.689%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.52775. Missing scores are unknown.","source_id":"sr-1a760c57b4faf825828cfdcb57d47a89"}],"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-2b4589d1438363247f133ee308638464","url":"https://github.com/advisories/GHSA-m2wj-r6g3-fxfx","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m2wj-r6g3-fxfx","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.972Z"},{"id":"sr-1a760c57b4faf825828cfdcb57d47a89","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-2023-46733","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:27:48.610Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 5.4.21; fixed 5.4.31"]},{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 6.2.7; fixed 6.3.8"]},{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 5.4.21; fixed 5.4.31"]},{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 6.2.7; fixed 6.3.8"]}],"null_published_at":"2026-11-04T18:04:03.089Z","source_updated_at":"2026-09-10T03:50:04.290Z","source_disclosed_at":"2023-11-12T15:51:54.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:42:30.972Z"},{"id":"NVI-00002908","kind":"vulnerability","title":"Symfony possible session fixation vulnerability","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m2wj-r6g3-fxfx","CVE-2023-46733"],"plain_summary":"OSV carries this publisher advisory for symfony/security-http, symfony/security-http, symfony/symfony, symfony/symfony. 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 5.4.31 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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 6.3.8 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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 5.4.31 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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 6.3.8 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-2b4589d1438363247f133ee308638464"],"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-2b4589d1438363247f133ee308638464","url":"https://github.com/advisories/GHSA-m2wj-r6g3-fxfx","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m2wj-r6g3-fxfx","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.972Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 5.4.21; fixed 5.4.31"]},{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 6.2.7; fixed 6.3.8"]},{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 5.4.21; fixed 5.4.31"]},{"certainty":"source_listed","source_ids":["sr-2b4589d1438363247f133ee308638464"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations.\n\n### Resolution\n\nSymfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nWe would like to thank Robert Meijers for reporting the issue and providing the fix.","public_affected_ranges":["ECOSYSTEM: introduced 6.2.7; fixed 6.3.8"]}],"null_published_at":"2026-10-31T22:12:38.458Z","source_updated_at":"2026-09-10T03:50:04.290Z","source_disclosed_at":"2023-11-12T15:51:54.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:42:30.972Z"}],"next_cursor":null,"snapshot_revision":"42594"}