CVE-2023-40171

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.9% (61st 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
Elevated

Also known asEUVD-2023-44776 (ENISA EUVD)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Dispatch is an open source security incident management tool. The server response includes the JWT Secret Key used for signing JWT tokens in error message when the Dispatch Plugin - Basic Authentication Provider plugin encounters an error when attempting to decode a JWT token. Any Dispatch users who own their instance and rely on the Dispatch Plugin - Basic Authentication Provider plugin for authentication may be impacted, allowing for any account to be taken over within their own instance. This could be done by using the secret to sign attacker crafted JWTs. If you think that you may be impacted, we strongly suggest you to rotate the secret stored in the DISPATCH_JWT_SECRET envvar in the .env file. This issue has been addressed in commit b1942a4319 which has been included in the 20230817 release. users are advised to upgrade. There are no known workarounds for this vulnerability.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (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.9%
EPSS %ILE
61st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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 public PoC (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.

The score's inputs: 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

August 17, 2023

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Aug 2, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

Server response includes the JWT Secret Key used for signing JWT tokens in error message · Advisory · Netflix/dispatch · GitHub

https://github.com/Netflix/dispatch/security/advisories/GHSA-fv3x-67q3-6pg7
GitHub release Patch Available

v20241220

Patch available: Netflix/dispatch v20241220

https://github.com/Netflix/dispatch/releases/tag/latest
GitHub pull request Patch Available

Removes error message for malformed JWT tokens

Patch available: Netflix/dispatch v20230817c (PR #3695 merged 2023-08-16)

https://github.com/Netflix/dispatch/pull/3695
GitHub commit

commit b1942a4319f0 (Netflix/dispatch)

Fix landed in Netflix/dispatch commit b1942a4319f0 — awaiting tagged release

https://github.com/Netflix/dispatch/commit/b1942a4319f0de820d86b84a58ebc85398b97c70

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 29× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 266 rows on record for this CVE, as 94 entries (6 repeats merged).

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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 166 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 14:02 UTCEchelonGraph re-scored
  2. 2026-11-12 16:30 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  3. 2026-11-12 14:38 UTCEchelonGraph re-scored
  4. 2026-11-11 16:33 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  5. 2026-11-11 15:14 UTCEchelonGraph re-scored
  6. 2026-11-10 16:37 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  7. 2026-11-10 15:50 UTCEchelonGraph re-scored
  8. 2026-11-09 16:30 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  9. 2026-11-08 17:03 UTCEchelonGraph re-scored
  10. 2026-11-08 16:35 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  11. 2026-11-07 17:39 UTCEchelonGraph re-scored
  12. 2026-11-07 16:35 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  13. 2026-11-06 18:16 UTCEchelonGraph re-scored
  14. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  15. 2026-11-05 18:53 UTCEchelonGraph re-scored
  16. 2026-11-05 16:33 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  17. 2026-11-04 19:30 UTCEchelonGraph re-scored
  18. 2026-11-04 16:31 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  19. 2026-11-04 15:25 UTCOSV refresh
  20. 2026-11-03 20:06 UTCEchelonGraph re-scored
  21. 2026-11-03 16:41 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  22. 2026-11-02 20:41 UTCEchelonGraph re-scored
  23. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  24. 2026-11-01 21:17 UTCEchelonGraph re-scored
  25. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.9% · 60th percentile
Show 69 more
  1. 2026-10-31 21:54 UTCEchelonGraph re-scored
  2. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  3. 2026-10-30 22:30 UTCEchelonGraph re-scored
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  5. 2026-10-29 23:07 UTCEchelonGraph re-scored
  6. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  7. 2026-10-28 23:44 UTCEchelonGraph re-scored
  8. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  9. 2026-10-28 00:22 UTCEchelonGraph re-scored
  10. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  11. 2026-10-27 00:57 UTCEchelonGraph re-scored
  12. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  13. 2026-10-25 17:37 UTCEchelonGraph re-scored
  14. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  15. 2026-10-24 22:19 UTCEchelonGraph re-scored
  16. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  17. 2026-10-23 22:56 UTCEchelonGraph re-scored
  18. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  19. 2026-10-22 23:12 UTCEchelonGraph re-scored
  20. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  21. 2026-10-21 23:49 UTCEchelonGraph re-scored
  22. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  23. 2026-10-21 00:26 UTCEchelonGraph re-scored
  24. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  25. 2026-10-20 00:59 UTCEchelonGraph re-scored
  26. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  27. 2026-10-18 23:56 UTCEchelonGraph re-scored
  28. 2026-10-18 07:54 UTCEchelonGraph re-scored
  29. 2026-10-18 00:31 UTCEchelonGraph re-scored
  30. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  31. 2026-10-17 01:02 UTCEchelonGraph re-scored
  32. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  33. 2026-10-16 01:06 UTCEchelonGraph re-scored
  34. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  35. 2026-10-14 20:08 UTCEchelonGraph re-scored
  36. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  37. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  38. 2026-10-12 16:51 UTCEchelonGraph re-scored
  39. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  40. 2026-10-11 21:47 UTCEchelonGraph re-scored
  41. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  42. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  43. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  44. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  45. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  46. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  47. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  48. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  49. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  50. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  51. 2026-09-30 16:28 UTCEchelonGraph re-scored
  52. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  53. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  54. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  55. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  56. 2026-09-26 15:56 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  57. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  58. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  59. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  60. 2026-09-23 02:02 UTCOSV refresh
  61. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  62. 2026-09-18 19:25 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  63. 2026-09-17 19:25 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  64. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  65. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  66. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  67. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  68. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  69. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile

Frequently asked(5)

What is CVE-2023-40171?
CVE-2023-40171 is a critical-severity vulnerability; its CVE record was published on August 17, 2023. Dispatch is an open source security incident management tool. The server response includes the JWT Secret Key used for signing JWT tokens in error message when the Dispatch Plugin - Basic Authentication Provider plugin encounters an error when attempting to decode a JWT token. Any Dispatch users…
When was the CVE record for CVE-2023-40171 published?
The CVE record for CVE-2023-40171 was published on August 17, 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-40171 actively exploited?
CVE-2023-40171 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-40171?
CVE-2023-40171 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2023-40171?
A fix for CVE-2023-40171 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-40171

Explore →

Is Your Infrastructure Affected by CVE-2023-40171?

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