PatchSiren

PatchSiren cyber security CVE debrief

CVE-2025-68272 SignalK CVE debrief

A Denial of Service (DoS) vulnerability in Signal K Server versions prior to 2.19.0 allows an unauthenticated attacker to crash the server by flooding the access request endpoint, causing a 'JavaScript heap out of memory' error due to unbounded in-memory storage of request objects. This issue affects Signal K Server installations in marine environments, potentially disrupting operations. Defenders should assess exposure and prioritize upgrading to version 2.19.0 or later to mitigate this vulnerability.

Vendor
SignalK
Product
signalk-server
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-01-01
Original CVE updated
2026-10-01
Advisory published
2026-01-01
Advisory updated
2026-10-01

Who should care

Defenders responsible for Signal K Server installations, particularly those in marine environments, should assess exposure and prioritize upgrading to version 2.19.0 or later to mitigate this DoS vulnerability.

Why it matters

CVE-2025-68272 is a Denial of Service vulnerability in Signal K Server that allows an unauthenticated attacker to crash the server. Defenders in marine environments should verify exposure and prioritize upgrading to version 2.19.0 or later.

  • Potential disruption of marine operations due to server crashes
  • Need for verification of Signal K Server installations for exposure
  • Priority on upgrading to version 2.19.0 or later to prevent exploitation
  • Potential impact on navigation and communication systems reliant on Signal K Server

Technical summary

The Signal K Server application, running on a central hub in a boat, is vulnerable to a Denial of Service (DoS) attack in versions prior to 2.19.0. An unauthenticated attacker can flood the access request endpoint (/signalk/v1/access/requests), causing a 'JavaScript heap out of memory' error due to unbounded in-memory storage of request objects. This results in the server crashing, potentially disrupting marine operations that rely on Signal K Server for navigation and communication. Defenders should prioritize verifying exposure of Signal K Server installations and upgrading to version 2.19.0 or later to mitigate this DoS vulnerability.

Defensive priority

Defenders should prioritize verifying exposure of Signal K Server installations and upgrading to version 2.19.0 or later to mitigate this DoS vulnerability.

Recommended defensive actions

  • Verify Signal K Server installations for exposure
  • Upgrade to version 2.19.0 or later
  • Monitor access request endpoint for potential abuse
  • Review compensating controls for exposed systems
  • Check relevant monitoring, detection, and logs for exposed assets
  • Track exceptions and retest remediated assets
  • Plan vendor-supported updates through normal change control

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impact, and the fixed version. However, additional information on potential exploitation or affected deployments is limited. Defenders should verify Signal K Server installations for exposure and review official advisories for further guidance. The lack of detailed information on affected deployments requires a cautious approach to verifying exposure and implementing mitigations.

Sources and references

Verified primary and authoritative sources

  • CVE-2025-68272 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2025-68272

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2025-68272 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2025-68272

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.