Skip to content

← Actionable
Unratedamended

Introspection in schema validation in Apollo Server

GHSA-w42g-7vfc-xf37

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (apollo-server-cloud-functions 2.14.2; apollo-server-micro 2.14.2; apollo-server 2.14.2; apollo-server-cache-memcached 2.14.2; apollo-server-cloudflare 2.14.2; 7 more packages under Affected packages), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

We encourage all users of Apollo Server to read this advisory in its entirety to understand the impact. The Resolution section contains details on patched versions. Impact If subscriptions: false is passed to the ApolloServer constructor options, there is no impact. If implementors were not expecting validation rules to be enforced on the WebSocket subscriptions transport and are unconcerned about introspection being enabled on the WebSocket subscriptions transport (or were not expecting that), then this advisory is not applicable. If introspection: true is passed to the ApolloServer constructor options, the impact is limited to user-provided validation rules (i.e., using validationRules) since there would be no expectation that introspection was disabled. The enforcement of user-provided validation rules on the HTTP transport is working as intended and is unaffected by this advisory. Similarly, disabling introspection on the HTTP transport is working as intended and is unaffected by…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-w42g-7vfc-xf37

  2. Revision 1 · created ·

    Published from osv record GHSA-w42g-7vfc-xf37

Agent brief

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

# Patch Next advisory brief: GHSA-w42g-7vfc-xf37

Advisory: Introspection in schema validation in Apollo Server
IDs: GHSA-w42g-7vfc-xf37
Record: https://patchnext.com/advisories/ghsa-w42g-7vfc-xf37 (revision 2, source checked 26 Oct 2026, 12:07 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-cloud-functions 2.14.2; apollo-server-micro 2.14.2; apollo-server 2.14.2; apollo-server-cache-memcached 2.14.2; apollo-server-cloudflare 2.14.2; apollo-server-lambda 2.14.2; apollo-server-koa 2.14.2; apollo-server-core 2.14.2; apollo-server-hapi 2.14.2; apollo-server-azure-functions 2.14.2; apollo-server-express 2.14.2; apollo-server-fastify 2.14.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm apollo-server-cloud-functions: affected < 2.14.2; fixed in 2.14.2
- npm apollo-server-micro: affected < 2.14.2; fixed in 2.14.2
- npm apollo-server: affected < 2.14.2; fixed in 2.14.2
- npm apollo-server-cache-memcached: affected < 2.14.2; fixed in 2.14.2
- npm apollo-server-cloudflare: affected < 2.14.2; fixed in 2.14.2
- npm apollo-server-lambda: affected < 2.14.2; fixed in 2.14.2
- npm apollo-server-koa: affected < 2.14.2; fixed in 2.14.2
- npm apollo-server-core: affected < 2.14.2; fixed in 2.14.2
- npm apollo-server-hapi: affected < 2.14.2; fixed in 2.14.2
- npm apollo-server-azure-functions: affected < 2.14.2; fixed in 2.14.2
- npm apollo-server-express: affected < 2.14.2; fixed in 2.14.2
- npm apollo-server-fastify: affected < 2.14.2; fixed in 2.14.2

## Suggested inspection (read-only)
- `npm ls apollo-server-cloud-functions --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls apollo-server-micro --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `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-cache-memcached --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls apollo-server-cloudflare --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls apollo-server-lambda --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls apollo-server-koa --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`.
- `npm ls apollo-server-hapi --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls apollo-server-azure-functions --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls apollo-server-express --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls apollo-server-fastify --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-cloud-functions, apollo-server-micro, apollo-server, apollo-server-cache-memcached, apollo-server-cloudflare, apollo-server-lambda, apollo-server-koa, apollo-server-core, apollo-server-hapi, apollo-server-azure-functions, apollo-server-express, apollo-server-fastify.
- 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-w42g-7vfc-xf37 (OSV record GHSA-w42g-7vfc-xf37 lists affected ranges: npm apollo-server >=0 =0 =0 =0 =0 =0 =0 =0 =0 <2.14.2 (fixed); npm…)
- Verified: https://github.com/advisories/GHSA-w42g-7vfc-xf37 (GitHub-reviewed advisory GHSA-w42g-7vfc-xf37 lists affected ranges: npm apollo-server >=0 =0 =0 =0 =0 =0 =0 =0 =0 =0 =0…)

Commands are suggestions: review each one before running it.

Loading voting…