- Exploited
- No known exploitation
- Fix
- Fixed in 2.31.0-beta.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.31.0-beta.1.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- The share of the registry's downloads of each affected package in the window that were versions inside the affected ranges. Downloads, not users or installs: CI runs and mirrors inflate the counts.
- 41% of signalk-server downloads last week were affected versions (4K).npm, 9.8K downloads in the last 7 days, read Nov 13, 2026
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Medium (ghsa)
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Signal K Server package (signalk-server) has a flaw where an unauthenticated WebSocket client can subscribe to the log path and receive the server's buffered logs. The bug is reached over the WebSocket connection, which stays open before login, and it does not depend on a non-default setup or any listed attack data.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
An unauthenticated WebSocket client can subscribe to the log path and receive buffered server logs.
WebSocket connections are intentionally permitted before authentication because login occurs over the WebSocket connection. However, the log subscription path does not enforce an authorization check.
processSubscribe handles subscriptions to the log path separately, without applying access control:
if (
Array.isArray(msg.subscribe) &&
msg.subscribe.length > 0 &&
msg.subscribe[0].path === 'log'
) {
if (!spark.logUnsubscribe) {
spark.logUnsubscribe = startServerLog(app, spark)
}
} else {
// normal subscriptions go through subscriptionmanager, which applies
// securityStrategy.filterReadDelta
}startServerLog then replays the whole buffer to that socket:
app.logging.getLog().forEach((log) => {
spark.write({ type: 'LOG', data: log })
})The asymmetry is inside this one file. Writes are gated by securityStrategy.shouldAllowWrite (ws.ts:961), normal delta subscriptions are filtered by securityStrategy.filterReadDelta (ws.ts:1159, the else branch of this same function), and the log branch consults neither.
An unauthenticated socket, which is legitimately open for login, can subscribe to log and receive buffered server logs.
Fix: Requires an administrator principal, before startServerLog, in the same way the other branch defers to securityStrategy. The fix was released with version 2.31.0-beta.1.
The investigated code path was reviewed at commit 26ab199. No server was run and no WebSocket frames were captured. AI assistance was used during the investigation.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Affects npm packages
- Severity4/10Rated medium by ghsa
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
Impact
- Widely used
signalk-server has 10.7k weekly downloads.Source: npmjs.com
What to do
Upgrade to a fixed version: 2.31.0-beta.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by GHSA-7M8X-X364-M26J (Signal K Server: Buffered logs exposed to unauthenticated WebSocket clients), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for GHSA-7M8X-X364-M26J (entry last updated 2026-11-12):
Affected:
- npm package signalk-server: fixed in 2.31.0-beta.1
Fixed versions: 2.31.0-beta.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: GHSA-7M8X-X364-M26J is not listed as of cve.now's last read.
This KEV status is for GHSA-7M8X-X364-M26J only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/SignalK/signalk-server/security/advisories/GHSA-7m8x-x364-m26j
- https://github.com/SignalK/signalk-server/commit/1bee85114a4cb7403aba71632d9902792d6b4f0c
- https://github.com/SignalK/signalk-server
- https://github.com/SignalK/signalk-server/releases/tag/v2.31.0
- https://github.com/SignalK/signalk-server/releases/tag/v2.31.0-beta.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/GHSA-7M8X-X364-M26J
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "GHSA-7M8X-X364-M26J"}.Timeline
- Advisory published
- Record last updated
- First seen by cve.now
Affected versions
fixed in 2.31.0-beta.1
Fixed in 2.31.0-beta.1 (released Aug 10, 2026, 94 days before disclosure).
The latest release, 2.37.0, is not affected.
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
Other links · 4
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about GHSA-7M8X-X364-M26J
Is GHSA-7M8X-X364-M26J being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by GHSA-7M8X-X364-M26J?
signalk-server (npm): before 2.31.0-beta.1.Source: cve.now feed data
How do I fix GHSA-7M8X-X364-M26J?
Upgrade to a fixed version: 2.31.0-beta.1.Source: cve.now feed data