CVE-2025-31485
highpriority · track · 0EPSS 0.006 · 50 %ileEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.9–7.5
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (8)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-428q-q3vv-3fq3GraphQL grant on a property might be cached with different objects2025-04-04ghsa · osvUS
### 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
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (14)
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/cve-2025-31485cnnvd
- https://github.com/api-platform/core/commit/7af65aad13037d7649348ee3dcd88e084ef771f8cnnvd
- https://github.com/api-platform/core/commit/cba3acfbd517763cf320167250c5bed6d569696acnnvd
- https://github.com/api-platform/core/releasesPatchcnnvd
- https://github.com/api-platform/core/releases/tag/v3.4.17cnnvd
- https://github.com/api-platform/core/security/advisories/GHSA-428q-q3vv-3fq3cnnvd
- https://github.com/api-platform/core/commit/7af65aad13037d7649348ee3dcd88e084ef771f8enisa_euvd
- https://github.com/api-platform/core/commit/cba3acfbd517763cf320167250c5bed6d569696aenisa_euvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan