The graphql-upload library included in Apollo Server 2 is vulnerable to CSRF mutations

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact The graphql-upload npm package can execute GraphQL operations contained in content-type: multipart/form-data POST requests. Because they are POST requests, they can contain GraphQL mutations. Because they use content-type: multipart/form-data, they can be "simple requests" which are not preflighted by browsers. If your GraphQL server uses graphql-upload and uses SameSite=None cookies for authentication, then JS on any origin can cause browsers to send cookie-authenticated mutations to your GraphQL server, which will be executed without checking your CORS policy first. (The attack won't be able to see the response to the mutation if your CORS policy is set up properly, but the side effects of the mutation will still happen.) Additionally, if your GraphQL server uses graphql-upload and relies on network properties for security (whether by explicitly looking at the client's IP address or by only being available on a private network), then JS on any origin can cause browsers…

Published by the source

12 Oct 2022, 14:15 UTC

Last modified by the source

31 Jul 2023, 20:39 UTC

Source last checked

26 Oct 2026, 12:24 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2p3c-p3qw-69r4

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-2p3c-p3qw-69r4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-2p3c-p3qw-69r4

Advisory: The graphql-upload library included in Apollo Server 2 is vulnerable to CSRF mutations
IDs: GHSA-2p3c-p3qw-69r4
Record: https://patchnext.com/advisories/ghsa-2p3c-p3qw-69r4 (revision 2, source checked 26 Oct 2026, 12:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: apollo-server 2.25.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm apollo-server: affected >= 2.0.0, < 2.25.4; fixed in 2.25.4

## Suggested inspection (read-only)
- `npm ls apollo-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on apollo-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2p3c-p3qw-69r4 (OSV record GHSA-2p3c-p3qw-69r4 lists affected ranges: npm apollo-server >=2.0.0 <2.25.4 (fixed))
- Verified: https://github.com/advisories/GHSA-2p3c-p3qw-69r4 (GitHub-reviewed advisory GHSA-2p3c-p3qw-69r4 lists affected ranges: npm apollo-server >=2.0.0 <2.25.4)

Commands are suggestions: review each one before running it.