Skip to main content
VulnerabilityPublished Updated

CVE-2025-68272: signalk-server · Uncontrolled Resource Consumption

Affects signalk-serverSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 2.19.0 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.19.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade signalk/signalk-server to 2.19.0.

Affected software

ProductAffectedFixed in
GitHubsignalk/signalk-serverpkg:github/signalk/signalk-serverOther threatsAffected
  • <2.19.0
Fixed in
  • 2.19.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

Description

Signal K Server is a server application that runs on a central hub in a boat. A Denial of Service (DoS) vulnerability in versions prior to 2.19.0 allows an unauthenticated attacker to crash the SignalK Server by flooding the access request endpoint (`/signalk/v1/access/requests`). This causes a "JavaScript heap out of memory" error due to unbounded in-memory storage of request objects. Version 2.19.0 fixes the issue.

References

Community reviews

Loading reviews…