Is CVE-2025-69203 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-69203 being exploited in the wild.

How severe is CVE-2025-69203?

Medium severity, with a CVSS score of 6.3, published 1 January 2026.

Which products and versions are affected?

signalk-server (npm) SEMVER:introduced=0,fixed=2.19.0.

Is there a fix for CVE-2025-69203?

Yes. signalk-server (npm): upgrade to 2.19.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-69203 attacked?

It is attacked over the network.

Am I affected by CVE-2025-69203?

Check whether you run signalk-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-69203: Signal K Server access request spoofing via X-Forwarded-For header

CVE-2025-69203 · Severity: medium · CVSS 6.3 · Published 2026-01-01

Signal K Server is a marine data server that manages device connections and access permissions. An attacker can craft a malicious access request that appears legitimate to administrators by spoofing the source IP address, providing a misleading description while requesting elevated permissions, and impersonating known devices. This could result in an administrator inadvertently granting admin-level access to an attacker with minimal user interaction.

Technologies: signalk-server (npm). Vendors: npm.

Quick answers

Is CVE-2025-69203 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-69203 being exploited in the wild.
How severe is CVE-2025-69203?: Medium severity, with a CVSS score of 6.3, published 1 January 2026.
Which products and versions are affected?: signalk-server (npm) SEMVER:introduced=0,fixed=2.19.0.
Is there a fix for CVE-2025-69203?: Yes. signalk-server (npm): upgrade to 2.19.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-69203 attacked?: It is attacked over the network.
Am I affected by CVE-2025-69203?: Check whether you run signalk-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

signalk-server (npm): upgrade to 2.19.0 or later
```
npm install signalk-server@2.19.0
```

Technical details

The vulnerability is a combination of insufficient input validation and unvalidated trust of the X-Forwarded-For HTTP header in the access request handler (src/tokensecurity.js). An attacker can craft an access request with a misleading description that suggests limited permissions while actually requesting admin-level access, and spoof their IP address to appear as a trusted internal source. The admin UI (packages/server-admin-ui/src/views/security/AccessRequests.js) displays the description field prominently while de-emphasizing the actual permissions field, increasing the likelihood of approval. The vulnerability requires admin interaction to approve the spoofed request but is highly convincing when combined with device enumeration. Patches are available in Signal K Server 2.19.0 and later.

Affected products

Signal K Server <= 2.19.0-beta.4

Identifiers

CVE-2025-69203
GHSA-vfrf-vcj7-wvr8

Timeline

2026-01-02: disclosed
2026-01-02: patched: Fixed in version 2.19.0

References

https://github.com/SignalK/signalk-server/security/advisories/GHSA-vfrf-vcj7-wvr8

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.