Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

Signal K resources API path traversal can disclose the JWT signing secret and enable remote code execution

GHSA-4xm8-rg9h-jhq2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (signalk-server 2.34.0; @signalk/resources-provider 1.5.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary Path traversal in the Signal K resources and applicationData APIs lets an unauthenticated or low-privileged user read, write and delete files outside the storage root. Reading /security.json discloses the JWT signing secret, enabling admin token forgery and remote code execution.

Details

Description The v2 REST resources API `GET /signalk/v2/api/resources/:resourceType/:resourceId` passes `resourceId` to `FileStore.getResource()` without validation. `getResource()` builds the file path with `path.join(this.resources[type].path, itemUuid)` followed by `readFile` + `JSON.parse`, so a `%2F`-encoded multi-level traversal (`..%2F..%2F..%2F..%2F`) escapes the resource storage directory and returns any JSON file on the server (source: `src/api/resources/index.ts:559-600`, `packages/resources-provider-plugin/src/filestorage.ts:115-125`). Because the JWT signing secret is stored in plaintext in ` /security.json` (generated at `src/tokensecurity.ts:271`, persisted via…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-4xm8-rg9h-jhq2

  2. Revision 1 · created ·

    Published from ghsa record GHSA-4xm8-rg9h-jhq2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-4xm8-rg9h-jhq2

Advisory: Signal K resources API path traversal can disclose the JWT signing secret and enable remote code execution
IDs: GHSA-4xm8-rg9h-jhq2
Record: https://patchnext.com/advisories/ghsa-4xm8-rg9h-jhq2 (revision 2, source checked 31 Oct 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: signalk-server 2.34.0; @signalk/resources-provider 1.5.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm signalk-server: affected >= 2.0.0, < 2.34.0; fixed in 2.34.0
- npm @signalk/resources-provider: affected >= 1.0.0, < 1.5.3; fixed in 1.5.3

## Suggested inspection (read-only)
- `npm ls signalk-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @signalk/resources-provider --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on signalk-server, @signalk/resources-provider.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4xm8-rg9h-jhq2 (GitHub-reviewed advisory GHSA-4xm8-rg9h-jhq2 lists affected ranges: npm signalk-server >=2.0.0 =1.0.0 <1.5.3)
- Verified: https://osv.dev/vulnerability/GHSA-4xm8-rg9h-jhq2 (OSV record GHSA-4xm8-rg9h-jhq2 lists affected ranges: npm signalk-server >=2.0.0 =1.0.0 <1.5.3 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…