CVE-2025-69203

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 6.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-01-02) is not newer than that change (2026-10-07), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-206135 (ENISA EUVD) · GHSA-vfrf-vcj7-wvr8 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Signal K Server is a server application that runs on a central hub in a boat. Versions prior to 2.19.0 of the access request system have two related features that when combined by themselves and with an information disclosure vulnerability enable convincing social engineering attacks against administrators. When a device creates an access request, it specifies three fields: clientId, description, and permissions. The SignalK admin UI displays the description field prominently to the administrator when showing pending requests, but the actual permissions field (which determines the access level granted) is less visible or displayed separately. This allows an attacker to request admin permissions while providing a description that suggests readonly access. The access request handler trusts the X-Forwarded-For HTTP header without validation to determine the client's IP address. This header is intended to preserve the original client IP when requests pass through reverse proxies, but when trusted unconditionally, it allows attackers to spoof their IP address. The spoofed IP is displayed to administrators in the access request approval interface, potentially making malicious requests appear to originate from trusted internal network addresses. Since device/source names can be enumerated via the information disclosure vulnerability, an attacker can impersonate a legitimate device or source, craft a convincing description, spoof a trusted internal IP address, and request elevated permissions, creating a highly convincing social engineering scenario that increases the likelihood of administrator approval. Users should upgrade to version 2.19.0 to fix this issue.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
71
EG Risk 71/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 1, 2026

Last Modified

October 7, 2026

Advisory Details (2)

Auto-updated Aug 6, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Access Request Spoofing · Advisory · SignalK/signalk-server · GitHub

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

v2.19.0

Patch available: SignalK/signalk-server v2.19.0

https://github.com/SignalK/signalk-server/releases/tag/v2.19.0

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmsignalk-server @ 2.19.0 (fixes < 2.19.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
signalk-server—
  • every version up to 2.19.0: fixed in 2.19.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 101 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-11-01 08:01 UTCGHSA enrichmentGHSA-vfrf-vcj7-wvr8 · GitHub severity MODERATE · GitHub CVSS 6.3
  4. 2026-11-01 08:01 UTCEG score recompute
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-10-27 11:45 UTCEG score recompute
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-25 16:03 UTCEG score recompute
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-10-18 05:16 UTCEG score recompute
  21. 2026-10-17 22:17 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
Show 74 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-12 16:46 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-10-11 20:21 UTCEG score recompute
  5. 2026-10-11 18:33 UTCEG score recompute
  6. 2026-10-11 15:07 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-10-07 11:21 UTCEG score recompute
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-10-01 08:23 UTCEG score recompute
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  20. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  21. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  25. 2026-09-19 19:30 UTCOSV refresh
  26. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  27. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  28. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  29. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  30. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  31. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  32. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  33. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  34. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  35. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  36. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  37. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  38. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  39. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  40. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  41. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  42. 2026-08-31 22:34 UTCOSV refresh
  43. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  44. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  45. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  46. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  47. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  48. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  49. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  50. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  51. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  52. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  53. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  54. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  55. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  56. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  57. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  58. 2026-08-15 00:08 UTCEG score recompute
  59. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  60. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  61. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  62. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  63. 2026-08-09 22:06 UTCEG score recompute
  64. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  65. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  66. 2026-08-08 03:27 UTCEG score recompute
  67. 2026-08-07 16:27 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  68. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  69. 2026-08-06 06:29 UTCEG score recompute▲ 2.50
  70. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  71. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  72. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  73. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  74. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-69203?
CVE-2025-69203 is a high-severity vulnerability; its CVE record was published on January 1, 2026. Signal K Server is a server application that runs on a central hub in a boat. Versions prior to 2.19.0 of the access request system have two related features that when combined by themselves and with an information disclosure vulnerability enable convincing social engineering attacks against…
When was the CVE record for CVE-2025-69203 published?
The CVE record for CVE-2025-69203 was published on January 1, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2025-69203 actively exploited?
CVE-2025-69203 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-69203?
CVE-2025-69203 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2025-69203?
A fix for CVE-2025-69203 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-69203

Explore →

Is Your Infrastructure Affected by CVE-2025-69203?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs