Signal K Server is a server application that runs on a central hub in a boat. From 2.0.0 until 2.34.0 for Signal K Server and from 1.0.0 until 1.5.3 for @signalk/resources-provider, the v2 REST route GET /signalk/v2/api/resources/:resourceType/:resourceId accepts an unsafe resourceId that can escape the intended resource directory. The route passes the attacker-controlled resourceId through src/api/resources/index.ts to FileStore.getResource() in packages/resources-provider-plugin/src/filestorage.ts without adequate path containment, allowing arbitrary JSON files reachable by the server to be read. Related PUT and DELETE resource operations can write or delete files outside the storage root. Deployments with allow_readonly enabled permit anonymous reads, while other deployments require a readonly user token. Reading security.json exposes the HS256 JWT signing secret and password hashes, allowing an attacker to forge an administrator token. Administrative access to POST /skServer/providers can then create an Execute provider that runs commands with the server process privileges and persists its configuration across restarts. This issue is fixed in Signal K Server 2.34.0 and @signalk/resources-provider 1.5.3.
CVE-2026-123807
“—” beside the score: it is equal to the CVSS score beside it.
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-30. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
Also known asEUVD-2026-120438 (ENISA EUVD) · GHSA-4xm8-rg9h-jhq2 (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8CRITICALhigh confidence
- EG Risk
- 75EG Risk 75/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)Severity98% × 45%Impact severity (EG Severity): CVSS 9.8 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, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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
- 45th
- 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.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.5% 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 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, 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 yes (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)3 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 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
November 9, 2026
Last Modified
November 12, 2026
Advisory Details (3)
Auto-updated Nov 9, 2026v2.34.0
Patch available: SignalK/signalk-server v2.34.0
https://github.com/SignalK/signalk-server/releases/tag/v2.34.0commit 83689f040d7e (SignalK/signalk-server)
Patch available: SignalK/signalk-server v2.34.0 (contains commit 83689f040d7e)
https://github.com/SignalK/signalk-server/commit/83689f040d7e90280dddc643f44f3e4ce348fbb1Unauthenticated path traversal in resources and applicationData APIs leads to JWT secret disclosure, admin impersonation and remote code execution · Advisory · SignalK/signalk-server · GitHub
https://github.com/SignalK/signalk-server/security/advisories/GHSA-4xm8-rg9h-jhq2Vendor Advisories for CVE-2026-123807(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | @signalk/resources-provider @ 1.5.3 (fixes >= 1.0.0, < 1.5.3) | — | ghsa |
| npm | signalk-server @ 2.34.0 (fixes >= 2.0.0, < 2.34.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 1 ecosystem)
npm(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| @signalk/resources-provider | — |
| — |
| signalk-server | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× 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.
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.5% · 45th percentile
- 2026-11-12 22:28 UTCGHSA enrichmentGHSA-4xm8-rg9h-jhq2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-12 17:56 UTCEchelonGraph re-scored
- 2026-11-12 17:56 UTCGHSA enrichmentGHSA-4xm8-rg9h-jhq2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
- 2026-11-11 17:42 UTCEchelonGraph re-scored
- 2026-11-11 17:42 UTCGHSA enrichmentGHSA-4xm8-rg9h-jhq2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
- 2026-11-10 17:27 UTCEchelonGraph re-scored
- 2026-11-10 17:27 UTCGHSA enrichmentGHSA-4xm8-rg9h-jhq2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-10 16:46 UTCEchelonGraph re-scored
- 2026-11-10 16:46 UTCGHSA enrichmentGHSA-4xm8-rg9h-jhq2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.5% · 45th percentile
- 2026-11-10 16:22 UTCEchelonGraph re-scored
- 2026-11-10 16:22 UTCGHSA enrichmentGHSA-4xm8-rg9h-jhq2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-09 22:00 UTCENISA EUVD ID recordedEUVD-2026-120438 · Source: ENISA EUVD
- 2026-11-09 20:45 UTCEchelonGraph re-scoredFirst assessed: 9.8 CRITICAL
- 2026-11-09 20:45 UTCGHSA enrichmentGHSA-4xm8-rg9h-jhq2 · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-11-09 20:44 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownnpm:signalk-server
Frequently asked(5)
What is CVE-2026-123807?
When was the CVE record for CVE-2026-123807 published?
Is CVE-2026-123807 actively exploited?
What is the CVSS score of CVE-2026-123807?
How do I remediate CVE-2026-123807?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-123807
Is Your Infrastructure Affected by CVE-2026-123807?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.