GHSA-8vp7-j5cj-vvm2
MEDIUMGHSA-8vp7-j5cj-vvm2 is a medium-severity (CVSS 4.4) CWE-444 vulnerability in sylius/resource-bundle. O3 Security confirms whether GHSA-8vp7-j5cj-vvm2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Ability to expose data in Sylius by using an unintended serialisation group
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-8vp7-j5cj-vvm2 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 0 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
sylius/resource-bundle🐘sylius/resource-bundle🐘sylius/resource-bundle🐘sylius/sylius🐘sylius/sylius🐘sylius/resource-bundleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Impact
ResourceBundle 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.
Anyone exposing an API with ResourceBundle's controller is affected. The vulnerable versions are: <1.3 || >=1.3.0 <=1.3.12 || >=1.4.0 <=1.4.5 || >=1.5.0 <=1.5.0 || >=1.6.0 <=1.6.2.
Patches
The 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.
After 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.
This behaviour might be a BC break for those using custom groups via the HTTP header, please adjust allowed_serialization_groups accordingly.
Workarounds
Service 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | sylius/resource-bundle | ≥ 1.4.0&&< 1.4.6 | 1.4.6 |
| 🐘Packagist | sylius/resource-bundle | ≥ 1.5.0&&< 1.5.1 | 1.5.1 |
| 🐘Packagist | sylius/resource-bundle | ≥ 1.6.0&&< 1.6.3 | 1.6.3 |
| 🐘Packagist | sylius/sylius | all versions | 1.3.12 |
| 🐘Packagist | sylius/sylius | ≥ 1.4.0&&< 1.4.4 | 1.4.4 |
| 🐘Packagist | sylius/resource-bundle | ≥ 1.0.0&&< 1.3.13 | 1.3.13 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sylius/resource-bundle. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update sylius/resource-bundle to 1.4.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8vp7-j5cj-vvm2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8vp7-j5cj-vvm2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-8vp7-j5cj-vvm2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8vp7-j5cj-vvm2 in your dependencies?
O3 detects GHSA-8vp7-j5cj-vvm2 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.