CVE-2025-31485GHSA-428Q-Q3VV-3FQ3
GraphQL grant on a property might be cached with different objects
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.0.22, 3.4.17, 4.1.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- api-platform core
From 4.0.0-alpha.1 · fixed in 4.0.22; fixed in 3.4.17
- api-platform/graphqlPackagist
From 4.0.0-alpha.1 · fixed in 4.0.22
- api-platform/corePackagist
From 4.0.0-alpha.1 · fixed in 4.0.22
- api-platform/graphqlPackagist
fixed in 3.4.17
- api-platform/corePackagist
fixed in 3.4.17
- api-platform/corePackagist
From 4.1.0-alpha.1 · fixed in 4.1.5
- api-platform/graphqlPackagist
From 4.1.0-alpha.1 · fixed in 4.1.5