Is CVE-2026-33950 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-33950 being exploited in the wild.

How severe is CVE-2026-33950?

Critical severity, with a CVSS score of 9.4, published 2 April 2026.

Which products and versions are affected?

signalk-server (npm) SEMVER:introduced=0,fixed=2.24.0-beta.4; Signal K Server < 2.24.0-beta.4.

Is there a fix for CVE-2026-33950?

Yes. signalk-server (npm): upgrade to 2.24.0-beta.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-33950 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-33950?

Check whether you run signalk-server (npm) or Signal K Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-33950: SignalK Signal K Server privilege escalation in /enableSecurity

Q: Is there a fix for CVE-2026-33950?

Yes. signalk-server (npm): upgrade to 2.24.0-beta.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-33950 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-33950?

Check whether you run signalk-server (npm) or Signal K Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-33950 · Severity: critical · CVSS 9.4 · Published 2026-04-02

Signal K Server is a central data hub used on boats to manage navigation and vessel information. A security flaw allows unauthorized individuals to create their own administrator accounts without needing any existing credentials. This could allow an attacker to remotely take control of the boat's server, modify sensitive navigation data, or change critical system configurations.

Technologies: signalk-server (npm), Signal K Server. Vendors: npm, Signal K.

Quick answers

Is CVE-2026-33950 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-33950 being exploited in the wild.
How severe is CVE-2026-33950?: Critical severity, with a CVSS score of 9.4, published 2 April 2026.
Which products and versions are affected?: signalk-server (npm) SEMVER:introduced=0,fixed=2.24.0-beta.4; Signal K Server < 2.24.0-beta.4.
Is there a fix for CVE-2026-33950?: Yes. signalk-server (npm): upgrade to 2.24.0-beta.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-33950 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-33950?: Check whether you run signalk-server (npm) or Signal K Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

signalk-server (npm): upgrade to 2.24.0-beta.4 or later
```
npm install signalk-server@2.24.0-beta.4
```

Technical details

Signal K Server contains a privilege escalation vulnerability due to improper authorization in the /skServer/enableSecurity endpoint. While this endpoint is intended to be used only during initial setup, it remains active and accessible even after security has been enabled and an administrator has been configured. The root cause is twofold: the route is never deregistered after the first use, and the server blindly trusts the 'type' field in the JSON request body. An unauthenticated attacker can send a POST request to this endpoint to inject a new user with 'admin' privileges, gaining full control over the server's configuration and vessel data. This issue is fixed in version 2.24.0-beta.4.

Affected products

SignalK Signal K Server < 2.24.0-beta.4

Identifiers

CVE-2026-33950
GHSA-x8hc-fqv3-7gwf

Timeline

2026-03-25: patched: Version 2.24.0-beta.4 released
2026-04-01: advisory: GitHub Security Advisory published
2026-04-02: disclosed: CVE-2026-33950 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.