CVE-2026-53451

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.1% (65th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-62497 (ENISA EUVD)Source: ENISA EUVD

9.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: 1.1%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Ground Station is a browser-based suite for satellite tracking, SDR reception, hardware control, and telemetry decoding. Prior to version 0.4.13, the unauthenticated save-waterfall-snapshot Socket.IO command passes attacker-controlled snapshotName input from backend/handlers/entities/sdr.py to backend/server/snapshots.py, where os.path.join permits an absolute path or parent-directory traversal and writes attacker-controlled base64-decoded bytes outside backend/data/snapshots. An attacker can write a logging YAML file containing a logging.config.dictConfig callable factory, use the unauthenticated update-app-config operation to set log_config to that file, and invoke restart_service. During restart, backend/common/logger.py passes the YAML through resolve_log_config_path(), yaml.safe_load(), and logging.config.dictConfig(), which executes the factory with service privileges and can also cause a persistent crash loop. This issue is fixed in version 0.4.13.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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
1.1%
EPSS %ILE
65th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 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, Track* at medium and Attend at high mission impact.

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 total (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)3 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 total (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

August 19, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Oct 31, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Unauthenticated arbitrary file write (path traversal) in save-waterfall-snapshot leads to remote code execution · Advisory · sgoudelis/ground-station · GitHub

https://github.com/sgoudelis/ground-station/security/advisories/GHSA-q35x-w3h6-36w8
GitHub release Patch Available

v0.4.13

Patch available: sgoudelis/ground-station v0.4.13

https://github.com/sgoudelis/ground-station/releases/tag/v0.4.13
GitHub commit Patch Available

commit 5649905f1021 (sgoudelis/ground-station)

Patch available: sgoudelis/ground-station v0.7.14 (contains commit 5649905f1021)

https://github.com/sgoudelis/ground-station/commit/5649905f1021155933463a54a76030924adffb9d

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 60× 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 100 of 138 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. None are among the latest 100 rows. The 38 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-53451?
CVE-2026-53451 is a critical-severity vulnerability; its CVE record was published on August 19, 2026. Ground Station is a browser-based suite for satellite tracking, SDR reception, hardware control, and telemetry decoding. Prior to version 0.4.13, the unauthenticated save-waterfall-snapshot Socket.IO command passes attacker-controlled snapshotName input from backend/handlers/entities/sdr.py to…
When was the CVE record for CVE-2026-53451 published?
The CVE record for CVE-2026-53451 was published on August 19, 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 September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-53451 actively exploited?
CVE-2026-53451 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53451?
CVE-2026-53451 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53451?
A fix for CVE-2026-53451 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53451

Explore →

Is Your Infrastructure Affected by CVE-2026-53451?

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