CVE-2025-31481 is a high-severity (CVSS 7.5) CWE-863 vulnerability in api-platform/graphql. A fix is available for api-platform/graphql — see the affected versions and patch details below.
GraphQL query operations security can be bypassed
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-31481.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
api-platform/graphql🐘api-platform/core🐘api-platform/graphql🐘api-platform/core🐘api-platform/graphql🐘api-platform/coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Using the Relay special node type you can bypass the configured security on an operation.
Details
Here is an example of how to apply security configurations for the GraphQL operations:
#[ApiResource(
security: "is_granted('ROLE_USER')",
operations: [ /* ... */ ],
graphQlOperations: [
new Query(security: "is_granted('ROLE_USER')"),
//...
],
)]
class Book { /* ... */ }
This indeed checks is_granted('ROLE_USER') as expected for a GraphQL query like the following:
query {
book(id: "/books/1") {
title
}
}
But the security check can be bypassed by using the node field (that is available by default) on the root query type like that:
query {
node(id: "/books/1") {
... on Book {
title
}
}
}
This does not execute any security checks and can therefore be used to access any entity without restrictions by everyone that has access to the API.
Impact
Everyone using GraphQl with the security attribute. Not sure whereas this works with custom resolvers nor if this also applies on mutation.
Patched at https://github.com/api-platform/core/commit/60747cc8c2fb855798c923b5537888f8d0969568
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | api-platform/graphql | ≥ 4.0.0-alpha.1&&< 4.0.22 | 4.0.22composer require api-platform/graphql:^4.0.22 |
| 🐘Packagist | api-platform/core | ≥ 4.0.0-alpha.1&&< 4.0.22 | 4.0.22composer require api-platform/core:^4.0.22 |
| 🐘Packagist | api-platform/graphql | all versions | 3.4.17composer require api-platform/graphql:^3.4.17 |
| 🐘Packagist | api-platform/core | all versions | 3.4.17composer require api-platform/core:^3.4.17 |
| 🐘Packagist | api-platform/graphql | ≥ 4.1.0-alpha.1&&< 4.1.5 | 4.1.5composer require api-platform/graphql:^4.1.5 |
| 🐘Packagist | api-platform/core | ≥ 4.1.0-alpha.1&&< 4.1.5 | 4.1.5composer require api-platform/core:^4.1.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for api-platform/graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update api-platform/graphql to 4.0.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-31481 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2025-31481 in your dependencies?
Find it across Packagist, including transitive dependencies.