GraphQl securityAfterResolver not called
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| api-platform | core | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Api-platform | Core | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-7991 | API Platform Core does not call GraphQl securityAfterResolver |
Github GHSA |
GHSA-7mxx-3cgm-xxv3 | API Platform Core does not call GraphQl securityAfterResolver |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.301% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. Starting in version 3.3.8, a security check that gets called after GraphQl resolvers is always replaced by another one as there's no break in a clause. As this falls back to `security`, the impact is there only when there's only a security after resolver and none inside security. The test in version 3.3.8 is probably broken. As of time of publication, a fixed version is not available. | API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. Starting in version 3.3.8, a security check that gets called after GraphQl resolvers is always replaced by another one as there's no break in a clause. As this falls back to `security`, the impact is there only when there's only a security after resolver and none inside security. Version 3.3.15 contains a patch for the issue. |
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. Starting in version 3.3.8, a security check that gets called after GraphQl resolvers is always replaced by another one as there's no break in a clause. As this falls back to `security`, the impact is there only when there's only a security after resolver and none inside security. The test in version 3.3.8 is probably broken. As of time of publication, a fixed version is not available. | |
| Title | GraphQl securityAfterResolver not called | |
| Weaknesses | CWE-20 | |
| References |
|
|
| Metrics |
cvssV3_1
|