CVE-2025-68272 is a Denial of Service vulnerability classified under CWE-400 (Uncontrolled Resource Consumption) and CWE-770 (Allocation of Resources Without Limits or Throttling) affecting the SignalK Server, a server application deployed on central hubs in boats to manage maritime data. The vulnerability exists in versions prior to 2.19.0, where the server's /signalk/v1/access/requests endpoint accepts access requests without authentication or rate limiting. An attacker can send a high volume of requests to this endpoint, causing the server to store each request object in memory without bounds. This leads to excessive JavaScript heap memory usage, culminating in a crash with an 'out of memory' error. The vulnerability has a CVSS 3.1 base score of 7.5, reflecting its high severity due to network attack vector, no required privileges or user interaction, and a significant impact on availability. The flaw does not affect confidentiality or integrity, as it only causes service disruption. The issue was publicly disclosed on January 1, 2026, and fixed in SignalK Server version 2.19.0. No known exploits have been reported in the wild, but the vulnerability poses a risk to maritime systems relying on SignalK for real-time data exchange and control. The root cause is the lack of input validation and resource management on the access request endpoint, allowing resource exhaustion through unbounded in-memory data accumulation.

For European organizations, particularly those in the maritime and shipping sectors using SignalK Server on vessels or maritime infrastructure, this vulnerability can cause critical service disruptions. The DoS attack can incapacitate the central hub managing navigation, sensor data, and communication, potentially affecting vessel operations and safety. Although it does not compromise data confidentiality or integrity, the loss of availability can delay critical decision-making and operational commands. This is especially impactful for commercial shipping companies, port authorities, and maritime research institutions in Europe that rely on real-time data aggregation and distribution. The disruption could also affect interconnected systems dependent on SignalK data streams, amplifying operational risks. Given the increasing digitalization of maritime operations in Europe, the vulnerability could have cascading effects on logistics, safety, and regulatory compliance.

The primary mitigation is to upgrade all SignalK Server instances to version 2.19.0 or later, where the vulnerability is patched. For environments where immediate upgrade is not feasible, implement strict rate limiting and throttling on the /signalk/v1/access/requests endpoint to prevent flooding attacks. Deploy Web Application Firewalls (WAFs) or API gateways capable of detecting and blocking abnormal request patterns targeting this endpoint. Monitor server memory usage and set alerts for unusual spikes indicative of potential exploitation attempts. Network segmentation can isolate SignalK servers from untrusted networks, reducing exposure. Additionally, implement logging and anomaly detection to identify repeated access request floods. Maritime organizations should also review their incident response plans to include scenarios involving SignalK server DoS events. Finally, coordinate with vendors and maritime cybersecurity bodies to stay updated on patches and threat intelligence.