How severe is GHSA-68jh-rf6x-836f?

No CVSS score has been assigned to GHSA-68jh-rf6x-836f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-68jh-rf6x-836f?

GHSA-68jh-rf6x-836f affects the following packages: @apollo/server (npm). Ecosystems affected: npm.

How do I fix GHSA-68jh-rf6x-836f?

Update @apollo/server to 4.7.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-68jh-rf6x-836f is resolved across your whole dependency graph.

How do I detect GHSA-68jh-rf6x-836f in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @apollo/server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-68jh-rf6x-836f if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-68jh-rf6x-836f actively exploited in the wild?

No public exploit code has been indexed for GHSA-68jh-rf6x-836f yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-68jh-rf6x-836f published, and has it been updated?

GHSA-68jh-rf6x-836f was published on June 16, 2023 and was last updated on June 20, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

@apollo/server vulnerable to unsafe application of Content Security Policy via reused noncesGHSA-68jh-rf6x-836f

Fix: apollographql/apollo-server@0adaf80

GHSA-68jh-rf6x-836f is a security vulnerability in @apollo/server. A fix is available for @apollo/server — see the affected versions and patch details below.

Published

Jun 16, 2023

Updated

Jun 20, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 20, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

526other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@apollo/servernpm

4.0Mdownloads / week

Description

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 commit.

Workarounds

The landing page can be disabled completely until the patch can be upgraded to. https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/#disabling-the-landing-page

References

https://content-security-policy.com/nonce/

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@apollo/server`	≥ 4.7.1&&< 4.7.4	4.7.4`npm install @apollo/server@4.7.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @apollo/server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @apollo/server to 4.7.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-68jh-rf6x-836f is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### 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 imple

O3 Security · Impact-Aware SCA

Is GHSA-68jh-rf6x-836f in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works