Signal K Server Vulnerable to Denial of Service via Unrestricted Access Request Flooding
CVE-2025-68272GHSA-7rqc-ff8m-7j23
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (signalk-server 2.19.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm signalk-server
- Affected
- < 2.19.0
- Fixed in
- 2.19.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-7rqc-ff8m-7j23 lists affected ranges: npm signalk-server >=0 <2.19.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-7rqc-ff8m-7j23 lists affected ranges: npm signalk-server >=0 <2.19.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- CVE-2025-68272: 0.56% estimated exploitation activity in the next 30 days; percentile 46.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary A Denial of Service (DoS) vulnerability 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. Details The vulnerability is caused by a lack of rate limiting and improper memory management for incoming access requests. Vulnerable Code Analysis: 1. In-Memory Storage: In src/requestResponse.js, requests are stored in a simple JavaScript object: 2. Unbounded Growth: The createRequest function adds new requests to this object without checking the current size or count of existing requests. 3. Infrequent Pruning: The pruneRequests function, which removes old requests, runs only once every 15 minutes (pruneIntervalRate). 4. No Rate Limiting: The endpoint /signalk/v1/access/requests accepts POST requests from any client without any rate limiting or authentication (by design, as it's for initial…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-7rqc-ff8m-7j23
- Revision 1 · created ·
Published from osv record GHSA-7rqc-ff8m-7j23
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-68272 Advisory: Signal K Server Vulnerable to Denial of Service via Unrestricted Access Request Flooding IDs: CVE-2025-68272, GHSA-7rqc-ff8m-7j23 Record: https://patchnext.com/advisories/cve-2025-68272 (revision 2, source checked 26 Oct 2026, 12:51 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: signalk-server 2.19.0. A vendor fix does not mean a deployment is fixed. ## Affected components - npm signalk-server: affected < 2.19.0; fixed in 2.19.0 ## Suggested inspection (read-only) - `npm ls signalk-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on signalk-server. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-7rqc-ff8m-7j23 (OSV record GHSA-7rqc-ff8m-7j23 lists affected ranges: npm signalk-server >=0 <2.19.0 (fixed)) - Verified: https://github.com/advisories/GHSA-7rqc-ff8m-7j23 (GitHub-reviewed advisory GHSA-7rqc-ff8m-7j23 lists affected ranges: npm signalk-server >=0 <2.19.0) Commands are suggestions: review each one before running it.
Loading voting…