{"answers":{"affected":"2 open source packages ship an affected version, including signalk-server. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33951 in the wild and no public exploit code.","fix":"Upgrade signalk-server to 2.24.0-beta.1 or later.","what":"CVE-2026-33951 is a medium-severity missing authorization vulnerability in signalk-server, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33951 and fix it if it is affected.\n\nWhat it is: CVE-2026-33951 is a medium-severity missing authorization vulnerability in signalk-server, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33951 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- signalk-server (npm): affected all versions; fixed in 2.24.0-beta.1\n- signalk-server (npm): affected all versions; fixed in 2.24.0-beta.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33951/ (Markdown: https://insights.sbomify.com/CVE-2026-33951/index.md)","id":"CVE-2026-33951","markdown":"https://insights.sbomify.com/CVE-2026-33951/index.md","name":"CVE-2026-33951","record":{"aliases":["GHSA-gfmv-vh34-h2x5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Marine navigation server","requires_auth":"none","summary":"Remote attackers can modify trusted navigation data source priorities via an unauthenticated API endpoint, compromising marine navigation integrity.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"signal_k_server","vendor":"signalk"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"Signal K Server is a server application that runs on a central hub in a boat. Prior to version 2.24.0-beta.1, the SignalK Server exposes an unauthenticated HTTP endpoint that allows remote attackers to modify navigation data source priorities. This endpoint, accessible via PUT /signalk/v1/api/sourcePriorities, does not enforce authentication or authorization checks and directly assigns user-controlled input to the server configuration. As a result, attackers can influence which GPS, AIS, or other sensor data sources are trusted by the system. The changes are immediately applied and persisted to disk, allowing the manipulation to survive server restarts. This issue has been patched in version 2.24.0-beta.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"signalk-server: Unauthenticated Source Priorities Manipulation","id":"CVE-2026-33951","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"FreeRDP: DoS via WINPR_ASSERT in rts_read_auth_verifier_no_checks","id":"CVE-2026-33952"},"packages":[{"ecosystem":"npm","fixed":["2.24.0-beta.1"],"introduced":["0"],"last_affected":[],"package":"signalk-server","purl":null,"source":"GHSA-gfmv-vh34-h2x5"},{"ecosystem":"npm","fixed":["2.24.0-beta.1"],"introduced":["0"],"last_affected":[],"package":"signalk-server","purl":"pkg:npm/signalk-server","source":"GHSA-gfmv-vh34-h2x5"}],"prev":{"headline":"signalk-server: Privilege Escalation by Admin Role Injection via /enableSecurity","id":"CVE-2026-33950"},"products":["signalk-server"],"published":"2026-04-02","related":[{"cvss_score":10,"headline":"RCE - Command Injection in Signal K set-system-time plugin","id":"CVE-2026-23515","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":9.7,"headline":"Signal K Server has Unauthenticated State Pollution leading to Remote Code Execution (RCE)","id":"CVE-2025-66398","kev_date_added":null,"published":"2026-01-01"},{"cvss_score":9.4,"headline":"signalk-server: Privilege Escalation by Admin Role Injection via /enableSecurity","id":"CVE-2026-33950","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":9.1,"headline":"Signal K Server vulnerable to JWT Token Theft via WebSocket Enumeration and Unauthenticated Polling","id":"CVE-2025-68620","kev_date_added":null,"published":"2026-01-01"},{"cvss_score":8.7,"headline":"Signal K Server's WebSocket Login Endpoint Lacks Rate Limiting (Credential Brute-Force)","id":"CVE-2026-41893","kev_date_added":null,"published":"2026-05-09"},{"cvss_score":7.5,"headline":"Signal K Server has an Unauthenticated Regular Expression Denial of Service (ReDoS) via WebSocket Subscription Paths","id":"CVE-2026-39320","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":7.5,"headline":"Signal K Server Vulnerable to Denial of Service via Unrestricted Access Request Flooding","id":"CVE-2025-68272","kev_date_added":null,"published":"2026-01-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-02","vendors":["SignalK"]},"summary":"Remote attackers can modify trusted navigation data source priorities via an unauthenticated API endpoint, compromising marine navigation integrity.","url":"https://insights.sbomify.com/CVE-2026-33951/"}