NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Composer (PHP)

CVE-2025-31485: GraphQL grant on a property might be cached with different objects

highCVSS 3.1 7.5GHSA-428q-q3vv-3fq3

Original message: I found an issue with security grants on on properties in the GraphQL ItemNormalizer: If you use something like #[ApiProperty(security: 'isgranted("PROPERTYREAD", [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.

Published Apr 4, 2025 · Updated Aug 29, 2025

Affected packages

api-platform/graphql

Ecosystem
Composer (PHP)
Affected
< 3.4.17
Fixed in
3.4.17
Check
composer show api-platform/graphql

api-platform/core

Ecosystem
Composer (PHP)
Affected
< 3.4.17
Fixed in
3.4.17
Check
composer show api-platform/core

api-platform/graphql

Ecosystem
Composer (PHP)
Affected
>= 4.0.0-alpha.1, < 4.0.22
Fixed in
4.0.22
Check
composer show api-platform/graphql

api-platform/core

Ecosystem
Composer (PHP)
Affected
>= 4.0.0-alpha.1, < 4.0.22
Fixed in
4.0.22
Check
composer show api-platform/core

api-platform/core

Ecosystem
Composer (PHP)
Affected
>= 4.1.0-alpha.1, < 4.1.5
Fixed in
4.1.5
Check
composer show api-platform/core

api-platform/graphql

Ecosystem
Composer (PHP)
Affected
>= 4.1.0-alpha.1, < 4.1.5
Fixed in
4.1.5
Check
composer show api-platform/graphql

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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

Credited to ausi, alanpoulain, soyuka, Fafabian.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Composer (PHP) vulnerabilities

All Composer (PHP) entries