CVE-2026-123807: Signal K Server Path Traversal Exposes JWT Secret and Enables RCE
What's the vulnerability
CVE-2026-123807 is a path traversal flaw (CWE-22) in the Signal K server resources API, specifically the @signalk/resources-provider component. The v2 REST endpoint GET /signalk/v2/api/resources/:resourceType/:resourceId passes the user-supplied resource id directly to the file store without sanitizing it. A URL-encoded traversal sequence (e.g. ../ variants) in the resourceId escapes the intended resources directory, letting a requester retrieve arbitrary JSON files from the host filesystem.
The critical impact comes from which file is reachable this way: security.json, which stores the server's JWT signing secret. On deployments with allow_readonly enabled, this file can be read with no authentication at all; on default configurations, any valid readonly-scoped token is sufficient. Once an attacker has the signing secret, they can forge a JWT with admin privileges and use it to register a malicious Execute provider via POST /skServer/providers, achieving remote code execution on the server.
Affected software
- signalk-server: versions >= 2.0.0, < 2.34.0
- @signalk/resources-provider: versions >= 1.0.0, < 1.5.3
Both packages are distributed via npm.
Exploitation status
This vulnerability has a CVSS score of 9.8 (Critical) and a public proof of concept is available. There is no confirmed patch date on record at this time. Given the public PoC and the low complexity of the exploit chain (a single traversal request followed by token forgery), defenders should treat any internet-facing or multi-tenant Signal K deployment in the affected version ranges as at immediate risk and prioritize mitigation.
How our detection catches it
Our detection logic targets the full exploit chain rather than a single indicator, improving coverage against variant encodings of the traversal payload:
- Traversal request detection — flags HTTP requests to the
/signalk/v2/api/resources/path whoseresourceIdsegment contains encoded or literal directory-traversal sequences. - Sensitive file access — surfaces successful responses that indicate
security.jsonor other sensitive configuration files were served through the resources endpoint instead of a legitimate resource object. - Post-theft anomaly correlation — watches for authentication events and administrative actions (such as provider creation) occurring shortly after a suspected secret-theft request, which is consistent with JWT forgery and the RCE follow-on.
This logic ships across Microsoft Sentinel (KQL), Splunk (SPL), Elastic (EQL), IBM QRadar (AQL), Sumo Logic, Google Chronicle (YARA-L), and CrowdStrike (CQL), so teams can deploy the same detection coverage regardless of their SIEM.
Full detection content, including the ready-to-use queries, investigation guide, and atomic tests for each platform, is available on the CVE-2026-123807 detection page.