How severe is GHSA-gvj8-4cj4-h776?

No CVSS score has been assigned to GHSA-gvj8-4cj4-h776 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gvj8-4cj4-h776?

GHSA-gvj8-4cj4-h776 affects the following packages: ibexa/core (Packagist), ibexa/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-gvj8-4cj4-h776?

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.

How do I detect GHSA-gvj8-4cj4-h776 in my Packagist dependencies?

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.

How do I mitigate GHSA-gvj8-4cj4-h776 if there is no patch (or I can't update yet)?

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.

Is GHSA-gvj8-4cj4-h776 actively exploited in the wild?

No public exploit code has been indexed for GHSA-gvj8-4cj4-h776 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-gvj8-4cj4-h776 published, and has it been updated?

GHSA-gvj8-4cj4-h776 was published on April 29, 2022 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Object state limitation has no effect

Real-World Exposure

2 pkgs affected

🐘ibexa/core🐘ibexa/core

Real-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

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ibexa/core`	≥ 4.0.0&&< 4.0.5	4.0.5`composer require ibexa/core:^4.0.5`
🐘Packagist	`ibexa/core`	≥ 4.1.0&&< 4.1.2	4.1.2`composer require ibexa/core:^4.1.2`

Detection & mitigation playbook

Open-source dependency

Detect
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.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-gvj8-4cj4-h776 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Object state limitation has no effectGHSA-gvj8-4cj4-h776