https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 01:17:41 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-280209 EUVD-2026-280209 https://cve.radiocsirt.org/vuln/euvd-2026-280209 https://cve.radiocsirt.org/vuln/fkie_cve-2026-33950 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-33950 https://cve.radiocsirt.org/vuln/ghsa-x8hc-fqv3-7gwf <p><strong>Affected:</strong> npm: signalk-server</p> <p>## Summary</p> <p>According to SignalK&#39;s security documentation, when a server is first initialized without security enabled, the **/skServer/enableSecurity** endpoint is intentionally exposed to allow the owner to set up the initial admin account. This initial open access is by design.</p> <p>However, the critical vulnerability is that this route is never deregistered or disabled after the initial successful setup. Even after the genuine administrator has created their account, restarted the server, and activated token security, the **/skServer/enableSecurity** route remains perpetually open.</p> <p>Furthermore, the endpoint explicitly trusts the **type** field provided in the request body, passing it directly into the server&#39;s security configuration without validation. Because the route remains permanently listening, any unauthenticated user can call this endpoint at any time to silently inject a new, fully privileged admin account alongside the legitimate ones.</p> <p>## Vulnerable Root Cause</p> <p>File: src/serverroutes.ts (Lines 685-754) ``` if (app.securityStrategy.getUsers(getSecurityConfig(app)).length === 0) { app.post( `${SERVERROUTESPREFIX}/enableSecurity`, (req: Request, res: Response) =&gt; { // ... function addUser(request: Request, response: Response, securityStrategy: SecurityStrategy, config?: any) { // [!VULNERABLE] Passes the entire JSON request body directly to the security strategy securityStrategy.addUser(config, request.body, (err…</p> <p><strong>Affected:</strong> npm: signalk-server</p> <p>## Summary</p> <p>According to SignalK&#39;s security documentation, when a server is first initialized without security enabled, the **/skServer/enableSecurity** endpoint is intentionally exposed to allow the owner to set up the initial admin account. This initial open access is by design.</p> <p>However, the critical vulnerability is that this route is never deregistered or disabled after the initial successful setup. Even after the genuine administrator has created their account, restarted the server, and activated token security, the **/skServer/enableSecurity** route remains perpetually open.</p> <p>Furthermore, the endpoint explicitly trusts the **type** field provided in the request body, passing it directly into the server&#39;s security configuration without validation. Because the route remains permanently listening, any unauthenticated user can call this endpoint at any time to silently inject a new, fully privileged admin account alongside the legitimate ones.</p> <p>## Vulnerable Root Cause</p> <p>File: src/serverroutes.ts (Lines 685-754) ``` if (app.securityStrategy.getUsers(getSecurityConfig(app)).length === 0) { app.post( `${SERVERROUTESPREFIX}/enableSecurity`, (req: Request, res: Response) =&gt; { // ... function addUser(request: Request, response: Response, securityStrategy: SecurityStrategy, config?: any) { // [!VULNERABLE] Passes the entire JSON request body directly to the security strategy securityStrategy.addUser(config, request.body, (err…</p> https://cve.radiocsirt.org/vuln/ghsa-x8hc-fqv3-7gwf