Is api-platform/core 3.3 vulnerable?
Composer · 16 releases from 3.3.0 to 3.3.15 · latest api-platform/core is 5.0.8 · checked 18 Nov 2026
Yes: 4 known advisories
Yes. api-platform/core 3.3.15, the last 3.3 release, is affected by 4 known security advisories (2 high, 2 medium), including CVE-2025-31485, CVE-2025-31481, CVE-2026-54164. 1 more affects earlier 3.3.x releases. Upgrade to 4.1.30 or later to fix all of them.
composer require api-platform/core:^4.1.30Is 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
Advisories affecting api-platform/core 3.3.15
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
GraphQL grant on a property might be cached with different objects
- Affected
- >=4.0.0-alpha.1 <4.0.22 · <3.4.17 · >=4.1.0-alpha.1 <4.1.5
- Fixed in
- 3.4.17, 4.0.22, 4.1.5
GraphQL query operations security can be bypassed
- Affected
- >=4.0.0-alpha.1 <4.0.22 · <3.4.17 · >=4.1.0-alpha.1 <4.1.5
- Fixed in
- 3.4.17, 4.0.22, 4.1.5
Fixed within 3.3.x, affecting earlier releases
API Platform Core does not call GraphQl securityAfterResolver
- Affected
- >=3.3.8 <3.3.15
- Fixed in
- 3.3.15
Every api-platform/core 3.3.x release
Affected: 3.3.0 to 3.3.15. Latest api-platform/core: 5.0.8.
| Version | Known advisories |
|---|---|
| api-platform/core 3.3.15 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481 |
| api-platform/core 3.3.14 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481, CVE-2025-23204 |
| api-platform/core 3.3.13 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481, CVE-2025-23204 |
| api-platform/core 3.3.12 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481, CVE-2025-23204 |
| api-platform/core 3.3.11 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481, CVE-2025-23204 |
| api-platform/core 3.3.10 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481, CVE-2025-23204 |
| api-platform/core 3.3.9 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481, CVE-2025-23204 |
| api-platform/core 3.3.8 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481, CVE-2025-23204 |
| api-platform/core 3.3.7 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481 |
| api-platform/core 3.3.6 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481 |
| api-platform/core 3.3.5 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481 |
| api-platform/core 3.3.4 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481 |
| api-platform/core 3.3.3 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481 |
| api-platform/core 3.3.2 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481 |
| api-platform/core 3.3.1 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481 |
| api-platform/core 3.3.0 | CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481 |
Which of your client projects are still on api-platform/core 3.3?
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.