Skip to content
Fencer Intel
critical 9.4

CVE-2026-33950 json

signalk-server: Privilege Escalation by Admin Role Injection via /enableSecurity

published 7mo ago modified 3mo ago also GHSA-x8hc-fqv3-7gwf , EUVD-2026-18372

cvss
9.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits
0
none known

Summary

Signal K Server is a server application that runs on a central hub in a boat. Prior to version 2.24.0-beta.4, there is a privilege escalation vulnerability by Admin Role Injection via /enableSecurity. An unauthenticated attacker can gain full Administrator access to the SignalK server at any time, allowing them to modify sensitive vessel routing data, alter server configurations, and access restricted endpoints. This issue has been patched in version 2.24.0-beta.4.

Patch / fix

  • npm signalk-server 2.24.0-beta.4
  • signalk signal_k_server 2.24.0

Is CVE-2026-33950 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
7mo ago

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/SignalK/signalk-server/security/advisories/GHSA-x8hc-fqv3-7gwf referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
GitHub 3.1 9.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Affected packages

ecosystem package affected fixed in
npm signalk-server
<2.24.0-beta.4
2.24.0-beta.4

Affected products

  • SignalK signalk-server

Classification

Weakness
  • CWE-285 Improper Authorization
  • CWE-288 Authentication Bypass Using an Alternate Path or Channel
  • CWE-862 Missing Authorization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.