Is api-platform/core 3.2 vulnerable?

Composer · 27 releases from 3.2.0 to 3.2.26 · latest api-platform/core is 5.0.8 · checked 18 Nov 2026

Yes: 4 known advisories

Yes. api-platform/core 3.2.26, the last 3.2 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.2.x releases. Upgrade to 4.1.30 or later to fix all of them.

Upgrade with:composer require api-platform/core:^4.1.30

Is your project on an affected api-platform/core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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

  • MediumCVE-2026-54164GHSA-9rjg-x2p2-h68h7 Aug 2026

    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
  • MediumCVE-2026-49858GHSA-pjhx-3c3w-9v2310 Jul 2026

    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
  • HighCVE-2025-31485GHSA-428q-q3vv-3fq34 Apr 2025

    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
  • HighCVE-2025-31481GHSA-cg3c-245w-728m4 Apr 2025

    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.2.x, affecting earlier releases

  • MediumCVE-2023-47639GHSA-rfw5-cqjj-7v9r3 Apr 2025

    API Platform Core can leak exceptions message that may contain sensitive information

    Affected
    >=3.2.0 <3.2.5
    Fixed in
    3.2.5

Every api-platform/core 3.2.x release

Affected: 3.2.0 to 3.2.26. Latest api-platform/core: 5.0.8.

VersionKnown advisories
api-platform/core 3.2.26CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.25CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.24CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.23CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.22CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.21CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.20CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.19CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.18CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.17CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.16CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.15CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.14CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.13CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.12CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.11CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.10CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.9CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.8CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.7CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.6CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.5CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481
api-platform/core 3.2.4CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481, CVE-2023-47639
api-platform/core 3.2.3CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481, CVE-2023-47639
api-platform/core 3.2.2CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481, CVE-2023-47639
api-platform/core 3.2.1CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481, CVE-2023-47639
api-platform/core 3.2.0CVE-2026-54164, CVE-2026-49858, CVE-2025-31485, CVE-2025-31481, CVE-2023-47639

Which of your client projects are still on api-platform/core 3.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.