Is CVE-2026-54164 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-54164 being exploited in the wild.

How severe is CVE-2026-54164?

Medium severity, with a CVSS score of 6.5, published 1 July 2026.

Which products and versions are affected?

api-platform/core (Packagist) ECOSYSTEM:introduced=0,fixed=4.1.30.

Is there a fix for CVE-2026-54164?

Yes. api-platform/core (Packagist): upgrade to 4.1.30 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-54164 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-54164?

Check whether you run api-platform/core (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-54164: API Platform Core type confusion in AbstractItemNormalizer

CVE-2026-54164 · Severity: medium · CVSS 6.5 · Published 2026-07-01

API Platform Core, a framework for building web APIs, contains a vulnerability where it fails to verify if a linked data object is of the correct type during data updates. An attacker with basic account access can exploit this to link unrelated data types together, potentially bypassing business logic or corrupting the application's data integrity. This could lead to unexpected application behavior or the corruption of records that rely on specific data relationships.

Technologies: api-platform/core (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-54164 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-54164 being exploited in the wild.
How severe is CVE-2026-54164?: Medium severity, with a CVSS score of 6.5, published 1 July 2026.
Which products and versions are affected?: api-platform/core (Packagist) ECOSYSTEM:introduced=0,fixed=4.1.30.
Is there a fix for CVE-2026-54164?: Yes. api-platform/core (Packagist): upgrade to 4.1.30 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54164 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-54164?: Check whether you run api-platform/core (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

api-platform/core (Packagist): upgrade to 4.1.30 or later
```
composer require api-platform/core:^4.1.30
```

Technical details

A type confusion vulnerability exists in API Platform Core's 'AbstractItemNormalizer' due to missing type validation when resolving Internationalized Resource Identifiers (IRIs) for relations. When processing write requests (POST/PUT/PATCH), the 'getResourceFromIri()' method fails to pass an operation context to the 'IriConverter', causing it to skip 'is_a' type guards. For legacy untyped properties (using @var annotations), this allows an attacker to assign an object of an incorrect class to a relation, leading to CWE-843. While modern PHP 8.x typed properties are partially protected by Symfony's PropertyAccessor, the vulnerability still affects untyped properties and collections of mixed-type interfaces. Patches are available in versions 4.1.30, 4.2.26, and 4.3.12.

Affected products

api-platform core < 4.1.30, >= 4.2.0 < 4.2.26, >= 4.3.0 < 4.3.12

Identifiers

CVE-2026-54164
GHSA-9rjg-x2p2-h68h

Timeline

2026-06-13: disclosed
2026-07-01: advisory: NVD publication date
2026-08-07: patched: GitHub Advisory reviewed and updated

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.