Batched HTTP requests may set incorrect cache-control response header

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 In Apollo Server 3 and 4, the cache-control HTTP response header may not reflect the cache policy that should apply to an HTTP request when that HTTP request contains multiple operations using HTTP batching. This could lead to data being inappropriately cached and shared. Apollo Server allows clients to send multiple operations in a single HTTP request. The results of these operations are returned in a single HTTP response, with a single set of headers. Apollo Client Web and Apollo Kotlin both have opt-in features to use batched requests. Apollo Server has several features relating to caching. This advisory is about the ability to set the cache-control response header based on field- and operation-specific cache hints. (It is not about the "response cache plugin".) This header can be interpreted by a reverse proxy such as a CDN in front of your server, or by a browser. In Apollo Server 2, plugins such as the cache control plugin could not control the HTTP headers of responses…

Published by the source

2 Nov 2022, 18:18 UTC

Last modified by the source

8 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 12:06 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-8r69-3cvp-wxc3

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-8r69-3cvp-wxc3

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

# Patch Next advisory brief: GHSA-8r69-3cvp-wxc3

Advisory: Batched HTTP requests may set incorrect `cache-control` response header
IDs: GHSA-8r69-3cvp-wxc3
Record: https://patchnext.com/advisories/ghsa-8r69-3cvp-wxc3 (revision 2, source checked 26 Oct 2026, 12:06 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 4.1.0; apollo-server-core 3.11.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @apollo/server: affected < 4.1.0; fixed in 4.1.0
- npm apollo-server-core: affected >= 3.0.0, < 3.11.0; fixed in 3.11.0

## 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`.
- `npm ls apollo-server-core --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, apollo-server-core.
- 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-8r69-3cvp-wxc3 (OSV record GHSA-8r69-3cvp-wxc3 lists affected ranges: npm apollo-server-core >=3.0.0 =0 <4.1.0 (fixed))
- Verified: https://github.com/advisories/GHSA-8r69-3cvp-wxc3 (GitHub-reviewed advisory GHSA-8r69-3cvp-wxc3 lists affected ranges: npm apollo-server-core >=3.0.0 =0 <4.1.0)

Commands are suggestions: review each one before running it.