{"items":[{"id":"NVI-00003266","kind":"vulnerability","title":"Ability to expose data in Sylius by using an unintended serialisation group","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-8vp7-j5cj-vvm2"],"plain_summary":"OSV carries this publisher advisory for sylius/resource-bundle, sylius/resource-bundle, sylius/resource-bundle, sylius/sylius, sylius/sylius. 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 1.4.6 for sylius/resource-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-38de89eb900fa84d2942c51af9652529"],"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 1.5.1 for sylius/resource-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-38de89eb900fa84d2942c51af9652529"],"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 1.6.3 for sylius/resource-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-38de89eb900fa84d2942c51af9652529"],"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 1.3.12 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-38de89eb900fa84d2942c51af9652529"],"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 1.4.4 for sylius/sylius. Confirm the publisher’s latest guidance.","source_ids":["sr-38de89eb900fa84d2942c51af9652529"],"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 1.3.13 for sylius/resource-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-38de89eb900fa84d2942c51af9652529"],"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-38de89eb900fa84d2942c51af9652529","url":"https://github.com/advisories/GHSA-8vp7-j5cj-vvm2","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-8vp7-j5cj-vvm2","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.675Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-38de89eb900fa84d2942c51af9652529"],"technology":"sylius/resource-bundle","known_exclusions":[],"conditions_summary":"### Impact\n\nResourceBundle accepts and uses any serialisation groups to be passed via a HTTP header. This might lead to data exposure by using an unintended serialisation group - for example it could make Shop API use a more permissive group from Admin API.\n\nAnyone exposing an API with ResourceBundle's controller is affected. The vulnerable versions are: `=1.3.0 =1.4.0 =1.5.0 =1.6.0 <=1.6.2`.\n\n### Patches\n\nThe patch is provided for ResourceBundle 1.3.13, 1.4.6, 1.5.1 and 1.6.3, but not for any versions below 1.3.\n\nAfter it is applied, It allows to choose only the groups that are defined in `serialization_groups` or `allowed_serialization_groups` route definition. Any group not defined in those will not be used.\n\nThis behaviour might be a BC break for those using custom groups via the HTTP header, please adjust `allowed_serialization_groups` accordingly.\n\n### Workarounds\n\nService `sylius.resource_controller.request_configuration_factory` can be overridden with an implementation copied from `\\Sylius\\Bundle\\ResourceBundle\\Controller\\RequestConfigurationFactory` where the part that handles custom serialisation groups is deleted.","public_affected_ranges":["ECOSYSTEM: introduced 1.4.0; fixed 1.4.6"]},{"certainty":"source_listed","source_ids":["sr-38de89eb900fa84d2942c51af9652529"],"technology":"sylius/resource-bundle","known_exclusions":[],"conditions_summary":"### Impact\n\nResourceBundle accepts and uses any serialisation groups to be passed via a HTTP header. This might lead to data exposure by using an unintended serialisation group - for example it could make Shop API use a more permissive group from Admin API.\n\nAnyone exposing an API with ResourceBundle's controller is affected. The vulnerable versions are: `=1.3.0 =1.4.0 =1.5.0 =1.6.0 <=1.6.2`.\n\n### Patches\n\nThe patch is provided for ResourceBundle 1.3.13, 1.4.6, 1.5.1 and 1.6.3, but not for any versions below 1.3.\n\nAfter it is applied, It allows to choose only the groups that are defined in `serialization_groups` or `allowed_serialization_groups` route definition. Any group not defined in those will not be used.\n\nThis behaviour might be a BC break for those using custom groups via the HTTP header, please adjust `allowed_serialization_groups` accordingly.\n\n### Workarounds\n\nService `sylius.resource_controller.request_configuration_factory` can be overridden with an implementation copied from `\\Sylius\\Bundle\\ResourceBundle\\Controller\\RequestConfigurationFactory` where the part that handles custom serialisation groups is deleted.","public_affected_ranges":["ECOSYSTEM: introduced 1.5.0; fixed 1.5.1"]},{"certainty":"source_listed","source_ids":["sr-38de89eb900fa84d2942c51af9652529"],"technology":"sylius/resource-bundle","known_exclusions":[],"conditions_summary":"### Impact\n\nResourceBundle accepts and uses any serialisation groups to be passed via a HTTP header. This might lead to data exposure by using an unintended serialisation group - for example it could make Shop API use a more permissive group from Admin API.\n\nAnyone exposing an API with ResourceBundle's controller is affected. The vulnerable versions are: `=1.3.0 =1.4.0 =1.5.0 =1.6.0 <=1.6.2`.\n\n### Patches\n\nThe patch is provided for ResourceBundle 1.3.13, 1.4.6, 1.5.1 and 1.6.3, but not for any versions below 1.3.\n\nAfter it is applied, It allows to choose only the groups that are defined in `serialization_groups` or `allowed_serialization_groups` route definition. Any group not defined in those will not be used.\n\nThis behaviour might be a BC break for those using custom groups via the HTTP header, please adjust `allowed_serialization_groups` accordingly.\n\n### Workarounds\n\nService `sylius.resource_controller.request_configuration_factory` can be overridden with an implementation copied from `\\Sylius\\Bundle\\ResourceBundle\\Controller\\RequestConfigurationFactory` where the part that handles custom serialisation groups is deleted.","public_affected_ranges":["ECOSYSTEM: introduced 1.6.0; fixed 1.6.3"]},{"certainty":"source_listed","source_ids":["sr-38de89eb900fa84d2942c51af9652529"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\n\nResourceBundle accepts and uses any serialisation groups to be passed via a HTTP header. This might lead to data exposure by using an unintended serialisation group - for example it could make Shop API use a more permissive group from Admin API.\n\nAnyone exposing an API with ResourceBundle's controller is affected. The vulnerable versions are: `=1.3.0 =1.4.0 =1.5.0 =1.6.0 <=1.6.2`.\n\n### Patches\n\nThe patch is provided for ResourceBundle 1.3.13, 1.4.6, 1.5.1 and 1.6.3, but not for any versions below 1.3.\n\nAfter it is applied, It allows to choose only the groups that are defined in `serialization_groups` or `allowed_serialization_groups` route definition. Any group not defined in those will not be used.\n\nThis behaviour might be a BC break for those using custom groups via the HTTP header, please adjust `allowed_serialization_groups` accordingly.\n\n### Workarounds\n\nService `sylius.resource_controller.request_configuration_factory` can be overridden with an implementation copied from `\\Sylius\\Bundle\\ResourceBundle\\Controller\\RequestConfigurationFactory` where the part that handles custom serialisation groups is deleted.","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.3.12"]},{"certainty":"source_listed","source_ids":["sr-38de89eb900fa84d2942c51af9652529"],"technology":"sylius/sylius","known_exclusions":[],"conditions_summary":"### Impact\n\nResourceBundle accepts and uses any serialisation groups to be passed via a HTTP header. This might lead to data exposure by using an unintended serialisation group - for example it could make Shop API use a more permissive group from Admin API.\n\nAnyone exposing an API with ResourceBundle's controller is affected. The vulnerable versions are: `=1.3.0 =1.4.0 =1.5.0 =1.6.0 <=1.6.2`.\n\n### Patches\n\nThe patch is provided for ResourceBundle 1.3.13, 1.4.6, 1.5.1 and 1.6.3, but not for any versions below 1.3.\n\nAfter it is applied, It allows to choose only the groups that are defined in `serialization_groups` or `allowed_serialization_groups` route definition. Any group not defined in those will not be used.\n\nThis behaviour might be a BC break for those using custom groups via the HTTP header, please adjust `allowed_serialization_groups` accordingly.\n\n### Workarounds\n\nService `sylius.resource_controller.request_configuration_factory` can be overridden with an implementation copied from `\\Sylius\\Bundle\\ResourceBundle\\Controller\\RequestConfigurationFactory` where the part that handles custom serialisation groups is deleted.","public_affected_ranges":["ECOSYSTEM: introduced 1.4.0; fixed 1.4.4"]},{"certainty":"source_listed","source_ids":["sr-38de89eb900fa84d2942c51af9652529"],"technology":"sylius/resource-bundle","known_exclusions":[],"conditions_summary":"### Impact\n\nResourceBundle accepts and uses any serialisation groups to be passed via a HTTP header. This might lead to data exposure by using an unintended serialisation group - for example it could make Shop API use a more permissive group from Admin API.\n\nAnyone exposing an API with ResourceBundle's controller is affected. The vulnerable versions are: `=1.3.0 =1.4.0 =1.5.0 =1.6.0 <=1.6.2`.\n\n### Patches\n\nThe patch is provided for ResourceBundle 1.3.13, 1.4.6, 1.5.1 and 1.6.3, but not for any versions below 1.3.\n\nAfter it is applied, It allows to choose only the groups that are defined in `serialization_groups` or `allowed_serialization_groups` route definition. Any group not defined in those will not be used.\n\nThis behaviour might be a BC break for those using custom groups via the HTTP header, please adjust `allowed_serialization_groups` accordingly.\n\n### Workarounds\n\nService `sylius.resource_controller.request_configuration_factory` can be overridden with an implementation copied from `\\Sylius\\Bundle\\ResourceBundle\\Controller\\RequestConfigurationFactory` where the part that handles custom serialisation groups is deleted.","public_affected_ranges":["ECOSYSTEM: introduced 1.0.0; fixed 1.3.13"]}],"null_published_at":"2026-10-31T22:12:43.402Z","source_updated_at":"2026-07-08T06:49:46.850Z","source_disclosed_at":"2020-01-31T18:00:43.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:10.675Z"}],"next_cursor":null,"snapshot_revision":"42594"}