All reports
High

GraphQL query operations security can be bypassed

Affected versions

Version ranges need review.

Affected versions
>= 4.0.0-alpha.1, < 4.0.22
Fixed version
4.0.22
Affected versions
>= 4.1.0-alpha.1, < 4.1.5
Fixed version
4.1.5
Affected versions
< 3.4.17
Fixed version
3.4.17
Affected versions
<3.4.17|>=4.0.0,<4.0.22|>=4.1.0,<4.1.5
Fixed version
Not reported
Affected versions
>= 4.0.0-alpha.1, < 4.0.22
Fixed version
4.0.22
Affected versions
>= 4.1.0-alpha.1, < 4.1.5
Fixed version
4.1.5
Affected versions
<3.4.17|>=4.0.0,<4.0.22|>=4.1.0,<4.1.5
Fixed version
Not reported
Affected versions
< 3.4.17
Fixed version
3.4.17

Exploitation

CVE-2025-31481

Probability of exploitation in the next 30 days: 0.48%

FIRST EPSS · 2026-11-21

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

Links

Credits

  • soyuka
  • ausi
  • alanpoulain