Medium

signalk-server has SSRF via absolute signalk.appIcon URL in the app store icon fetcher

  • Disclosed: 30.10.2026
  • Updated: 31.10.2026 01:17

Summary

The app store icon code (dist/appstore/icon-probe.js around line 200 and icon-bytes.js around line 138) resolves a plugin's declared signalk.appIcon. Relative paths are pinned to the CDN, but an absolute http(s) URL is used as-is: the server fetches it, follows redirects, and stores any image/* response as the plugin's icon, which is then served to the admin UI. Unrelated to GHSA-q59x-jc9f-gfqf.

Affected

signalk-server 2.33.0 (latest).

Reproduction

The real dist modules driven directly, Docker with --network none; a local "internal" service on 127.0.0.1 logs requests:

[CONTROL relative] declared=../../icon.png
  resolved=null
  internal-service hits: []  stored: null
[ATTACK absolute] declared=http://127.0.0.1:35013/latest/meta-data/iam
  resolved=http://127.0.0.1:35013/latest/meta-data/iam
  internal-service hits: ["GET /latest/meta-data/iam"]  stored: .../icon-bytes/evil-plugin@1.0.0.png (70 bytes)
[ATTACK redirect] declared=http://127.0.0.1:35013/redir
  internal-service hits: ["GET /redir","GET /internal-secret-via-redirect.png"]  stored: .../icon-bytes/evil-plugin@1.0.0.png (70 bytes)

The modules were tested directly rather than through a full running server.

Impact

Anyone who can get a plugin listed in the app store (publishing an npm package with the signalk keywords) can make every signalk-server that browses the app store send requests to internal addresses on the vessel network and to cloud metadata endpoints. Responses with an image content type are stored and served back to the user.

Suggested fix

Only accept relative icon paths resolved against the CDN (or an https allowlist of known hosts), do not follow redirects to other hosts, and reject private, loopback and link-local addresses after resolution.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package signalk-server >= 2.28.0-beta.2, < 2.34.0 2.34.0

References

CVSS score 4.2/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
Weakness (CWE)
CWE-918
Platform
npm
Package
signalk-server
Disclosed
30.10.2026
Updated
31.10.2026 01:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-7wpf-ch8f-5f4x - CC BY 4.0

Vulnerability history: signalk-server

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (17) in the archive
Total entries
17
First → latest
01.2026 11.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 4
  • High 4
  • Medium 8
  • Low 1

Disclosures per year

  1. 2026: 17
Severity:
  1. signalk-server has SSRF via absolute signalk.appIcon URL in the app store icon fetcher this entry
    Medium · 4.2 CVE-2026-115752 >= 2.28.0-beta.2, < 2.34.0 2.34.0
  2. Critical · 9.4 CVE-2026-33950 < 2.24.0-beta.4 2.24.0-beta.4

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.