GHSA-gvj8-4cj4-h776 — ibexa/core
GHSA-gvj8-4cj4-h776 is a security vulnerability in ibexa/core. A fix is available for ibexa/core — see the affected versions and patch details below.
Object state limitation has no effect
Real-World Exposure
ibexa/core🐘ibexa/coreReal-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
Object state limitation is a policy you can use in your roles to limit access to content based on specific object state values. Due to a flawed earlier update, these limitations were ineffective in releases made since February 16th 2022. They would grant access to the given content regardless of the object state. Depending on how your frontent is designed, knowing the URL to the content may or may not be required to access it. If you are using object state limitations in your roles, this issue is critical. Please apply the fix as soon as possible.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | ibexa/core | ≥ 4.0.0&&< 4.0.5 | 4.0.5composer require ibexa/core:^4.0.5 |
| 🐘Packagist | ibexa/core | ≥ 4.1.0&&< 4.1.2 | 4.1.2composer require ibexa/core:^4.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ibexa/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ibexa/core to 4.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gvj8-4cj4-h776 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-gvj8-4cj4-h776 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-gvj8-4cj4-h776. 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-gvj8-4cj4-h776 in your dependencies?
O3 Security finds GHSA-gvj8-4cj4-h776 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.