CVE-2023-41317

MEDIUMNVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.8% (55th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The Apollo Router is a configurable, high-performance graph router written in Rust to run a federated supergraph that uses Apollo Federation 2. Affected versions are subject to 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: 1. Running Apollo Router v1.28.0, v1.28.1 or v1.29.0 ("impacted versions"); and 2. The Supergraph schema provided to the Router (either via Apollo Uplink or explicitly via other configuration) has a subscription type with root-fields defined; and 3. The YAML configuration provided to the Router has subscriptions enabled (they are _disabled_ by default), either by setting enabled: true _or_ by setting a valid mode within the subscriptions object (as seen in subscriptions' documentation); and 4. An anonymous (i.e., un-named) subscription operation (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. This is fixed in Apollo Router v1.29.1. Users are advised to upgrade. 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.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
The EG Score, 5.9 of 10.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 5, 2023

Last Modified

June 17, 2026

References (3)

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
apollo-router—
  • 1.28.0 up to 1.29.1: fixed in 1.29.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 80 of 183 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 20 repeat rows among the latest 100 are merged into the row they repeat. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 21:46 UTCEG score recompute
  2. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  3. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  4. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  5. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  6. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  7. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  8. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  9. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  10. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  11. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  12. 2026-09-30 16:29 UTCEG score recompute
  13. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  14. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  15. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  16. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  17. 2026-09-26 15:56 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  18. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  19. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  20. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  21. 2026-09-23 00:32 UTCOSV refresh
  22. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  23. 2026-09-18 19:25 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  24. 2026-09-17 19:25 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  25. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.8% · 54th percentile
Show 55 more
  1. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  2. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  3. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  4. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  5. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  6. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  7. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  8. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  9. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  10. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  11. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  12. 2026-09-03 19:16 UTCOSV refresh
  13. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  14. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  15. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  16. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  17. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  18. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  19. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  20. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  21. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  22. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  23. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  24. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  25. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  26. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  27. 2026-08-17 08:36 UTCOSV refresh
  28. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  29. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  30. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  31. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  32. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  33. 2026-08-11 13:39 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  34. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  35. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  36. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  37. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  38. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  39. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  40. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  41. 2026-08-02 03:11 UTCOSV refresh
  42. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  43. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  44. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  45. 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  46. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  47. 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  48. 2026-07-25 14:16 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  49. 2026-07-24 14:16 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  50. 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  51. 2026-07-23 02:26 UTCEG score recompute
  52. 2026-07-22 23:12 UTCEG score recompute▼ 1.60
  53. 2026-07-22 14:06 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  54. 2026-07-21 15:23 UTCEPSS rescoreEPSS 0.7% · 47th percentile
  55. 2026-07-20 17:06 UTCEPSS rescoreEPSS 0.7% · 47th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2023-41317?
CVE-2023-41317 is a medium-severity vulnerability; its CVE record was published on September 5, 2023. The Apollo Router is a configurable, high-performance graph router written in Rust to run a federated supergraph that uses Apollo Federation 2. Affected versions are subject to a Denial-of-Service (DoS) type vulnerability which causes the Router to panic and terminate when GraphQL Subscriptions are…
When was the CVE record for CVE-2023-41317 published?
The CVE record for CVE-2023-41317 was published on September 5, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2023-41317 actively exploited?
CVE-2023-41317 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-41317?
CVE-2023-41317 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2023-41317?
A fix for CVE-2023-41317 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-41317

Explore →

Is Your Infrastructure Affected by CVE-2023-41317?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs