GraphQL grant on a property might be cached with different objects

CAO 7.5CVE-2025-31485 · GHSA-428q-q3vv-3fq3 · Công bố 03/04/2025 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2025-31485 là lỗ hổng mức CAO (CVSS 7.5) ảnh hưởng api-platform/core, api-platform/graphql.
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.63%, cao hơn 50.2% các lỗ hổng khác.
Cách xử lý: cập nhật lên 4.0.22, 4.1.5, 3.4.17 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
api-platform/core Packagist	`≥ 4.0.0-alpha.1, < 4.0.22≥ 4.1.0-alpha.1, < 4.1.5< 3.4.17`	`4.0.224.1.53.4.17`
api-platform/graphql Packagist	`≥ 4.0.0-alpha.1, < 4.0.22≥ 4.1.0-alpha.1, < 4.1.5< 3.4.17`	`4.0.224.1.53.4.17`

Mô tả

Original message:

I found an issue with security grants on on properties in the GraphQL ItemNormalizer:

If you use something like #[ApiProperty(security: 'is_granted("PROPERTY_READ", [object, property])')] on a member of an entity, the grant gets cached and is only evaluated once, even if the object in question is a different one.

There is the ApiPlatform\GraphQl\Serializer\ItemNormalizer::isCacheKeySafe() method that seems to be intended to prevent this: https://github.com/api-platform/core/blob/88f5ac50d20d6510686a7552310cc567fcca45bf/src/GraphQl/Serializer/ItemNormalizer.php#L160-L164
and in its usage on line 90 it does indeed not create a cache key, but the parent::normalize() that is called afterwards still creates the cache key and causes the issue.

Impact

It grants access to properties that it should not.

Workarounds

Override the ItemNormalizer.

Patched at: https://github.com/api-platform/core/commit/7af65aad13037d7649348ee3dcd88e084ef771f8

Mô tả của NVD

API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. Prior to 4.0.22 and 3.4.17, a GraphQL grant on a property might be cached with different objects. The ApiPlatform\GraphQl\Serializer\ItemNormalizer::isCacheKeySafe() method is meant to prevent the caching but the parent::normalize method that is called afterwards still creates the cache key and causes the issue. This vulnerability is fixed in 4.0.22 and 3.4.17.