How severe is GHSA-rv8p-rr2h-fgpg?

GHSA-rv8p-rr2h-fgpg has a CVSS score of 8.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-rv8p-rr2h-fgpg?

GHSA-rv8p-rr2h-fgpg affects the following packages: @apollo/experimental-nextjs-app-support (npm). Ecosystems affected: npm.

How do I fix GHSA-rv8p-rr2h-fgpg?

Update @apollo/experimental-nextjs-app-support to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rv8p-rr2h-fgpg is resolved across your whole dependency graph.

How do I detect GHSA-rv8p-rr2h-fgpg in my npm dependencies?

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

How do I mitigate GHSA-rv8p-rr2h-fgpg 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-rv8p-rr2h-fgpg actively exploited in the wild?

No public exploit code has been indexed for GHSA-rv8p-rr2h-fgpg 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.

What is the EPSS score for GHSA-rv8p-rr2h-fgpg?

GHSA-rv8p-rr2h-fgpg has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rv8p-rr2h-fgpg?

GHSA-rv8p-rr2h-fgpg is classified as CWE-80 (CWE-80). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rv8p-rr2h-fgpg published, and has it been updated?

GHSA-rv8p-rr2h-fgpg was published on January 30, 2024 and was last updated on September 10, 2026. 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

HIGH severity

@apollo/experimental-nextjs-app-support Cross-site Scripting vulnerabilityGHSA-rv8p-rr2h-fgpg

HIGHFix: apollographql/apollo-client-nextjs@b92bc42

GHSA-rv8p-rr2h-fgpg is a high-severity (CVSS 8.2) CWE-80 vulnerability in @apollo/experimental-nextjs-app-support. A fix is available for @apollo/experimental-nextjs-app-support — see the affected versions and patch details below.

Also known asCVE-2024-23841

Published

Jan 30, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rv8p-rr2h-fgpg.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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.

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

@apollo/experimental-nextjs-app-supportnpm

113Kdownloads / week

Description

Impact

The @apollo/experimental-apollo-client-nextjs NPM package is vulnerable to a cross-site scripting vulnerability. This vulnerability arises from improper handling of untrusted input when @apollo/experimental-apollo-client-nextjs performs server-side rendering of HTML pages. To fix this vulnerability, we implemented appropriate escaping to prevent javascript injection into rendered pages.

Patches

To fix this issue, please update to version 0.7.0 or later.

Workarounds

There are no known workarounds for this issue. Please update to version 0.7.0

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@apollo/experimental-nextjs-app-support`	all versions	0.7.0`npm install @apollo/experimental-nextjs-app-support@0.7.0`

Affected Products

1 product · 1 configurations

Application

apollo clientapollographql

< 0.7.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @apollo/experimental-nextjs-app-support, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @apollo/experimental-nextjs-app-support to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rv8p-rr2h-fgpg 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

### Impact The @apollo/experimental-apollo-client-nextjs NPM package is vulnerable to a cross-site scripting vulnerability. This vulnerability arises from improper handling of untrusted input when @apollo/experimental-apollo-client-nextjs performs server-side rendering of HTML pages. To fix this vulnerability, we implemented appropriate escaping to prevent javascript injection into rendered pages. ### Patches To fix this issue, please update to version 0.7.0 or later. ### Workarounds There are no known workarounds for this issue. Please update to version 0.7.0