CVE-2026-123807: signalk-server · Path Traversal
Affects signalk-serverSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.34.0 as a priority.
Data as of 9 Nov 2026, 20:50 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 9.8 |
|---|
- Patch
- Available – fixed in 2.34.0, 1.5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade signalk-server to 2.34.0; resources-provider to 1.5.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SignalKsignalk-server | Affected
| Fixed in
|
| @signalkresources-provider | Affected
| Fixed in
|
AI-suggested
This vulnerability is fixed in Signal K Server version 2.34.0 and @signalk/resources-provider version 1.5.3. Users should upgrade to these versions or later to remediate the issue. No additional mitigation is required once updated. Deployments should ensure they are not running affected versions.
Description
CVE-2026-123807 is a critical path traversal vulnerability in Signal K Server and its resources provider plugin. It affects versions from 2.0.0 up to but not including 2.34.0 for signalk-server and from 1.0.0 up to but not including 1.5.3 for @signalk/resources-provider. The vulnerability allows an attacker to read, write, or delete arbitrary JSON files on the server by exploiting insufficient path containment in the REST API resourceId parameter. This can lead to exposure of sensitive files such as security.json, which contains JWT signing secrets and password hashes. With this information, an attacker can forge administrator tokens and gain administrative access to execute arbitrary commands with server privileges. The issue is fixed in versions 2.34.0 and 1.5.3 respectively.