CVE-2026-56679

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
8.7EG
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.5%CVSS: 8.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

9Router is an AI router & token saver. Prior to 0.5.4, the PATCH /api/settings endpoint writes the entire request body to persistent settings without a field whitelist, allowing an authenticated user to set security-critical fields such as requireLogin and disable authentication for the whole application, exposing protected routes such as /api/keys and /api/providers to unauthenticated access. This issue is reported as fixed in version 0.5.4.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
55
EG Risk 55/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)
Severity87% × 45%
The EG Score, 8.7 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.5%
EPSS %ILE
42nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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 no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

July 15, 2026

Last Modified

July 16, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Mass assignment in PATCH /api/settings allows authenticated authorization downgrade · Advisory · decolua/9router · GitHub

Affected: 0.3.75). This finding requires a valid authenticated session and abuses input han

https://github.com/decolua/9router/security/advisories/GHSA-vmjq-hvgq-2wv4

Vendor Advisories for CVE-2026-56679(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
9router—
  • every version up to 0.5.4: fixed in 0.5.4
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 34× 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 100 of 133 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. None are among the latest 100 rows. The 33 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56679?
CVE-2026-56679 is a high-severity vulnerability; its CVE record was published on July 15, 2026. 9Router is an AI router & token saver. Prior to 0.5.4, the PATCH /api/settings endpoint writes the entire request body to persistent settings without a field whitelist, allowing an authenticated user to set security-critical fields such as requireLogin and disable authentication for the whole…
When was the CVE record for CVE-2026-56679 published?
The CVE record for CVE-2026-56679 was published on July 15, 2026. 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 July 16, 2026; the record at its source may have been updated since.
Is CVE-2026-56679 actively exploited?
CVE-2026-56679 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56679?
CVE-2026-56679 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56679?
A fix for CVE-2026-56679 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56679 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56679

Explore →

Is Your Infrastructure Affected by CVE-2026-56679?

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

Book a Demo →Browse All CVEs