@apollo/server vulnerable to unsafe application of Content Security Policy via reused nonces

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.

Context Content Security Policies (CSP) are a defense-in-depth strategy against XSS attacks. Improper application of CSP isn't itself a vulnerability, but it does fail to prevent XSS in the event that there is a viable attack vector for an XSS attack. Impact There aren't any XSS attack vectors via the Apollo Server landing pages known to Apollo, so to our knowledge there is no impact. However, if there are existing XSS vectors that haven't been reported and patched, then all users of Apollo Server's landing pages have a vulnerability which won't be prevented by the current CSP implemented by the landing pages. Prior to version 4.7.1, there was no CSP implemented at all. However, the initial CSP implementation (4.7.1+) reused nonces. While this sufficiently resolved the issue w.r.t. scripts not running in Safari, it did not implement CSP in a safe or conventional way. Patches The issue is patched in the latest version of Apollo Server, v4.7.4. The changes can be reviewed in the merge…

Published by the source

16 Jun 2023, 19:40 UTC

Last modified by the source

20 Jun 2023, 19:50 UTC

Source last checked

26 Oct 2026, 12:22 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-68jh-rf6x-836f

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-68jh-rf6x-836f

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

# Patch Next advisory brief: GHSA-68jh-rf6x-836f

Advisory: @apollo/server vulnerable to unsafe application of Content Security Policy via reused nonces
IDs: GHSA-68jh-rf6x-836f
Record: https://patchnext.com/advisories/ghsa-68jh-rf6x-836f (revision 2, source checked 26 Oct 2026, 12:22 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.7.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @apollo/server: affected >= 4.7.1, < 4.7.4; fixed in 4.7.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-68jh-rf6x-836f (OSV record GHSA-68jh-rf6x-836f lists affected ranges: npm @apollo/server >=4.7.1 <4.7.4 (fixed))
- Verified: https://github.com/advisories/GHSA-68jh-rf6x-836f (GitHub-reviewed advisory GHSA-68jh-rf6x-836f lists affected ranges: npm @apollo/server >=4.7.1 <4.7.4)

Commands are suggestions: review each one before running it.