Is ibexa/core 4.1 vulnerable?
Composer · 6 releases from 4.1.0 to 4.1.5 · latest ibexa/core is 5.0.11 · checked 18 Nov 2026
No known advisories in the last release
ibexa/core 4.1.5, the last 4.1 release, has no known advisories. 2 advisories affect earlier 4.1.x releases, so update to 4.1.5.
composer require ibexa/core:^4.1.5Is your project on an affected ibexa/core?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 4.1.x, affecting earlier releases
Login timing attack in ibexa/core
- Affected
- >=4.0.0 <4.0.7 · >=4.1.0 <4.1.4
- Fixed in
- 4.0.7, 4.1.4
Object state limitation has no effect
- Affected
- >=4.0.0 <4.0.5 · >=4.1.0 <4.1.2
- Fixed in
- 4.0.5, 4.1.2
Every ibexa/core 4.1.x release
Affected: 4.1.0 to 4.1.3. 4.1.4 and later are not affected. Latest ibexa/core: 5.0.11.
| Version | Known advisories |
|---|---|
| ibexa/core 4.1.5 | None |
| ibexa/core 4.1.4 | None |
| ibexa/core 4.1.3 | GHSA-2x4v-g8cx-jxrq |
| ibexa/core 4.1.2 | GHSA-2x4v-g8cx-jxrq |
| ibexa/core 4.1.1 | GHSA-2x4v-g8cx-jxrq, GHSA-gvj8-4cj4-h776 |
| ibexa/core 4.1.0 | GHSA-2x4v-g8cx-jxrq, GHSA-gvj8-4cj4-h776 |
Which of your client projects are still on ibexa/core 4.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact ibexa/core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other ibexa/core versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.