How severe is CVE-2026-115752?

No CVSS score has been assigned to CVE-2026-115752 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-115752?

CVE-2026-115752 affects the following packages: signalk-server (npm). Ecosystems affected: npm.

How do I fix CVE-2026-115752?

Update signalk-server to 2.34.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-115752 is resolved across your whole dependency graph.

How do I detect CVE-2026-115752 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for signalk-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-115752 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2026-115752 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-115752 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-115752?

CVE-2026-115752 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 7th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-115752?

CVE-2026-115752 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-115752 published, and has it been updated?

CVE-2026-115752 was published on October 23, 2026 and was last updated on October 31, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-115752 — signalk-server

Fix: SignalK/signalk-server@535104f

CVE-2026-115752 is a Server-Side Request Forgery (SSRF) vulnerability in signalk-server. A fix is available for signalk-server — see the affected versions and patch details below.

Signal K Server 2.28.0-beta.2 before 2.34.0 SSRF via App Store appIcon

Also known asGHSA-7wpf-ch8f-5f4x

Published

Oct 23, 2026

Updated

Oct 31, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-115752.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs7th percentile — riskier than 7% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦signalk-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

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/[email protected] (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/[email protected] (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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`signalk-server`	≥ 2.28.0-beta.2&&< 2.34.0	2.34.0`npm install signalk-server@2.34.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for signalk-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update signalk-server to 2.34.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-115752 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is CVE-2026-115752 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2026-115752 — signalk-server

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Summary

Affected

Reproduction

Impact

Suggested fix

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2026-115752 in your dependencies?