Is api-platform/core 4.2 vulnerable?
Composer · 27 releases from 4.2.0 to 4.2.26 · latest api-platform/core is 5.0.8 · checked 18 Nov 2026
No known advisories in the last release
api-platform/core 4.2.26, the last 4.2 release, has no known advisories. 2 advisories affect earlier 4.2.x releases, so update to 4.2.26.
composer require api-platform/core:^4.2.26Is your project on an affected api-platform/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.2.x, affecting earlier releases
API Platform Core: Relation IRIs are not type-checked: a related resource can be denormalised as the wrong resource type (type confusion)
- Affected
- <4.1.30 · >=4.2.0 <4.2.26 · >=4.3.0 <4.3.12
- Fixed in
- 4.1.30, 4.2.26, 4.3.12
API Platform Core vulnerable to cross-user attribute leak in JSON:API and HAL item normalizers due to missing isCacheKeySafe gate
- Affected
- >=2.6.0 <4.1.29 · >=4.2.0 <4.2.25 · >=4.3.0 <4.3.8
- Fixed in
- 4.1.29, 4.2.25, 4.3.8
Every api-platform/core 4.2.x release
Affected: 4.2.0 to 4.2.25. 4.2.26 is not affected. Latest api-platform/core: 5.0.8.
| Version | Known advisories |
|---|---|
| api-platform/core 4.2.26 | None |
| api-platform/core 4.2.25 | CVE-2026-54164 |
| api-platform/core 4.2.24 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.23 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.22 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.21 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.20 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.19 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.18 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.17 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.16 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.15 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.14 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.13 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.12 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.11 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.10 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.9 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.8 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.7 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.6 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.5 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.4 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.3 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.2 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.1 | CVE-2026-54164, CVE-2026-49858 |
| api-platform/core 4.2.0 | CVE-2026-54164, CVE-2026-49858 |
Which of your client projects are still on api-platform/core 4.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact api-platform/core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other api-platform/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.