CVE-2026-113594

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreHIGH confidence

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

Score 5.4 from GitHub Security Advisory published 2026-10-20. A secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Sharkord before 0.0.8 contains a missing authorization vulnerability that allows any authenticated member to change server-wide settings by calling the others.updateSettings tRPC mutation without the MANAGE_SETTINGS permission. Attackers can set a join password, disable registration, zero upload limits, or toggle plugin loading to deny service to other members.

CVSS v3
5.4
EG Score
5.4MEDIUMhigh confidence
EG Risk
24
EG Risk 24/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)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.3%
EPSS %ILE
26th
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 (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 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 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

October 20, 2026

Last Modified

October 20, 2026

Advisory Details (5)

Auto-updated Oct 20, 2026
Patch available. Sources: github_commit, github_release.
Web page

Sharkord before 0.0.8 Missing Authorization via updateSettings tRPC Route | Advisories | VulnCheck

https://www.vulncheck.com/advisories/sharkord-before-0.0.8-missing-authorization-via-updatesettings-trpc-route
Web page

sharkord/apps/server/src/routers/others/update-settings.ts at v0.0.7 · Sharkord/sharkord · GitHub

https://github.com/Sharkord/sharkord/blob/v0.0.7/apps/server/src/routers/others/update-settings.ts
GitHub release Patch Available

v0.0.8

Patch available: Sharkord/sharkord v0.0.8

https://github.com/Sharkord/sharkord/releases/tag/v0.0.8
GitHub commit

commit 3866cd3a352e (Sharkord/sharkord)

Fix landed in Sharkord/sharkord commit 3866cd3a352e — awaiting tagged release

https://github.com/Sharkord/sharkord/commit/3866cd3a352e99ddedbd9f809261dacaca4d2c29
Web page

Security: Missing Permission Checks on Server Settings Mutation Endpoints · Issue #387 · Sharkord/sharkord · GitHub

https://github.com/Sharkord/sharkord/issues/387

Vendor Advisories for CVE-2026-113594(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 7× 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.

  1. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-10-20 20:26 UTCEG score recompute
  3. 2026-10-20 20:26 UTCGHSA enrichmentGHSA-p2rv-36r3-pvw3 · GitHub CVSS 5.4
  4. 2026-10-20 17:31 UTCEG score recompute
  5. 2026-10-20 16:30 UTCEG score recompute
  6. 2026-10-20 15:49 UTCEG score recomputeFirst assessed: 5.4 MEDIUM
  7. 2026-10-20 15:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-113594?
CVE-2026-113594 is a medium-severity vulnerability; its CVE record was published on October 20, 2026. Sharkord before 0.0.8 contains a missing authorization vulnerability that allows any authenticated member to change server-wide settings by calling the others.updateSettings tRPC mutation without the MANAGE_SETTINGS permission. Attackers can set a join password, disable registration, zero upload…
When was CVE-2026-113594 made public?
CVE-2026-113594 was made public on February 25, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 20, 2026. EchelonGraph's copy of the record carries a last-modified date of October 20, 2026; the record at its source may have been updated since.
Is CVE-2026-113594 actively exploited?
CVE-2026-113594 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-113594?
CVE-2026-113594 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-113594?
A fix for CVE-2026-113594 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-113594 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-113594

Explore →

Is Your Infrastructure Affected by CVE-2026-113594?

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