CVE-2023-41317 is a high-severity (CVSS 7.5) CWE-755 vulnerability in apollo-router. A fix is available for apollo-router — see the affected versions and patch details below.
Unnamed "Subscription" operation results in Denial-of-Service in apollographql/router
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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 CVE-2023-41317.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2023-41317 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
apollo-routerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Impact
This is a Denial-of-Service (DoS) type vulnerability which causes the Router to panic and terminate when GraphQL Subscriptions are enabled. It can be triggered when all of the following conditions are met:
- Running Apollo Router v1.28.0, v1.28.1 or v1.29.0 ("impacted versions"); and
- The Supergraph schema provided to the Router (either via Apollo Uplink or explicitly via other configuration) has a
subscriptiontype with root-fields defined; and - The YAML configuration provided to the Router has subscriptions enabled (they are disabled by default), either by setting
enabled: trueor by setting a validmodewithin thesubscriptionsobject (as seen in subscriptions' documentation); and - An anonymous (i.e., un-named)
subscriptionoperation (e.g.,subscription { ... }) is received by the Router
If all four of these criteria are met, the impacted versions will panic and terminate. There is no data-privacy risk or sensitive-information exposure aspect to this vulnerability.
Depending on the environment in which impacted versions are running and the high-availability characteristics of that environment, a single Router's termination may result in limited or reduced availability or other knock-on effects which are deployment-specific (e.g., depending on if there are multiple instances, auto-restart policies, etc.)
Discovery
This vulnerability was discovered by an internal Apollo team. We have no reports or evidence to support that that has been exploited outside of our own testing, research and follow-up.
Our public security policy can be reviewed at https://github.com/apollographql/router/security/policy and we consider the security of our projects a top priority. Please review the linked policy for more details.
Patches
This is fixed in Apollo Router v1.29.1, which is available on:
- GitHub Releases as
v1.29.1 - GitHub Packages Container Registry as
v1.29.1 - Helm Chart Repository as
1.29.1(without thev)
We recommend all users running the impacted configuration above to update to a patched version of the Router immediately. Router v1.29.1 should be a very simple upgrade from any impacted version.
Workarounds
Updating to v1.29.1 should be a clear and simple upgrade path for those running impacted versions. However, if Subscriptions are not necessary for your Graph – but are enabled via configuration — then disabling subscriptions is another option to mitigate the risk.
For more information
If you have any questions or comments about this advisory:
- Open an issue in the
routerrepository - Email us at
security[at]apollographql[dot]com
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | apollo-router | ≥ 1.28.0&&< 1.29.1 | 1.29.1cargo update -p apollo-router --precise 1.29.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apollo-router, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update apollo-router to 1.29.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-41317 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-41317 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-41317. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2023-41317 in your dependencies?
O3 Security finds CVE-2023-41317 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.