CVE-2026-48105

HIGHPre-NVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (11th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.3EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.3Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Arc is an open, SQL-native time-series database for telemetry. Prior to version 26.06.1, Arc Enterprise's Raft FSM (internal/cluster/raft/fsm.go:applyRegisterFile) accepts attacker-chosen file paths in manifest-registration proposals without validating them against the configured storage backend. The only check is that the path is non-empty. There is no parent-traversal (..) rejection, no allowlist of legitimate prefixes, no scheme restriction (s3:// vs local), and no length bound. This is fixed in 2026.06.1. Some workarounds are available. Restrict cluster network access to known-trusted peers via strict firewall rules, audit the cluster manifest for unexpected paths (any path not matching the configured storage backend root is suspect), and/or disable cluster mode until the fix is available.

CVSS v3
8.3
EG Score
8.3HIGHmedium confidence
EG Risk
37
EG Risk 37/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity83% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 21, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Aug 21, 2026
No fix on record yet. Sources: github.
githubMentions a patch (unverified)

Arc Enterprise cluster FSM applyRegisterFile accepts arbitrary file paths without validation, enabling cluster-wide path-traversal worm primitive · Advisory · Basekick-Labs/arc · GitHub

https://github.com/Basekick-Labs/arc/security/advisories/GHSA-f85q-mvg8-qf37

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-09 05:38 UTCEG score recompute
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-08 04:48 UTCEG score recompute
  5. 2026-10-07 23:48 UTCEPSS rescore
  6. 2026-10-06 16:49 UTCEG score recompute
  7. 2026-10-06 15:18 UTCEPSS rescore
  8. 2026-10-06 03:03 UTCEG score recompute
  9. 2026-10-05 17:43 UTCEPSS rescore
  10. 2026-10-05 09:25 UTCEG score recompute
  11. 2026-10-04 23:22 UTCEPSS rescore
  12. 2026-10-03 16:40 UTCEG score recompute
  13. 2026-10-03 14:25 UTCEPSS rescore
  14. 2026-10-03 01:35 UTCEG score recompute
  15. 2026-10-01 22:44 UTCEG score recompute
  16. 2026-10-01 19:50 UTCEPSS rescore
  17. 2026-09-30 20:25 UTCEG score recompute
  18. 2026-09-30 15:03 UTCEPSS rescore
  19. 2026-09-29 15:35 UTCEG score recompute
  20. 2026-09-28 21:35 UTCEG score recompute
  21. 2026-09-28 13:51 UTCEPSS rescore
  22. 2026-09-27 15:47 UTCEG score recompute
  23. 2026-09-27 13:48 UTCEPSS rescore
  24. 2026-09-27 02:22 UTCEG score recompute
  25. 2026-09-26 15:59 UTCEPSS rescore
Show 60 more
  1. 2026-09-26 00:27 UTCEPSS rescore
  2. 2026-09-24 18:59 UTCEG score recompute
  3. 2026-09-24 05:36 UTCEG score recompute
  4. 2026-09-23 17:53 UTCEPSS rescore
  5. 2026-09-22 15:44 UTCEG score recompute
  6. 2026-09-22 03:07 UTCEG score recompute
  7. 2026-09-21 01:43 UTCEG score recompute
  8. 2026-09-20 20:16 UTCEPSS rescore
  9. 2026-09-19 23:43 UTCEG score recompute
  10. 2026-09-18 22:30 UTCEG score recompute
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-17 21:16 UTCEG score recompute
  13. 2026-09-16 19:41 UTCEG score recompute
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-16 05:43 UTCEG score recompute
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-15 04:27 UTCEG score recompute
  18. 2026-09-14 03:12 UTCEG score recompute
  19. 2026-09-13 16:47 UTCEPSS rescore
  20. 2026-09-13 01:58 UTCEG score recompute
  21. 2026-09-12 00:44 UTCEG score recompute
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-11 12:05 UTCEG score recompute
  24. 2026-09-10 09:55 UTCEG score recompute
  25. 2026-09-10 09:35 UTCEPSS rescore
  26. 2026-09-09 01:44 UTCEG score recompute
  27. 2026-09-08 22:01 UTCEPSS rescore
  28. 2026-09-08 04:05 UTCEG score recompute
  29. 2026-09-07 16:01 UTCEPSS rescore
  30. 2026-09-06 13:48 UTCEG score recompute
  31. 2026-09-06 13:47 UTCEPSS rescore
  32. 2026-09-06 01:11 UTCEG score recompute
  33. 2026-09-04 23:48 UTCEG score recompute
  34. 2026-09-04 11:06 UTCEG score recompute
  35. 2026-09-04 05:06 UTCEPSS rescore
  36. 2026-09-02 21:12 UTCEG score recompute
  37. 2026-09-02 14:12 UTCEPSS rescore
  38. 2026-09-01 19:53 UTCEG score recompute
  39. 2026-09-01 13:54 UTCEPSS rescore
  40. 2026-09-01 06:35 UTCEG score recompute
  41. 2026-08-31 03:36 UTCEG score recompute
  42. 2026-08-30 19:17 UTCEPSS rescore
  43. 2026-08-30 02:21 UTCEG score recompute
  44. 2026-08-30 01:22 UTCEPSS rescore
  45. 2026-08-29 01:02 UTCEG score recompute
  46. 2026-08-28 21:41 UTCEPSS rescore
  47. 2026-08-27 23:18 UTCEG score recompute
  48. 2026-08-27 14:25 UTCEPSS rescore
  49. 2026-08-26 22:04 UTCEG score recompute
  50. 2026-08-26 14:46 UTCEPSS rescore
  51. 2026-08-25 20:43 UTCEG score recompute
  52. 2026-08-25 13:49 UTCEPSS rescore
  53. 2026-08-24 19:26 UTCEG score recompute
  54. 2026-08-24 18:51 UTCEG score recompute
  55. 2026-08-24 14:35 UTCEG score recompute
  56. 2026-08-23 00:40 UTCEG score recompute
  57. 2026-08-23 00:19 UTCEPSS rescore
  58. 2026-08-21 23:25 UTCEG score recompute
  59. 2026-08-21 22:54 UTCEG score recompute
  60. 2026-08-21 22:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48105?
CVE-2026-48105 is a high vulnerability published on August 21, 2026. Arc is an open, SQL-native time-series database for telemetry. Prior to version 26.06.1, Arc Enterprise's Raft FSM (internal/cluster/raft/fsm.go:applyRegisterFile) accepts attacker-chosen file paths in manifest-registration proposals without validating them against the configured storage backend.…
When was CVE-2026-48105 disclosed?
CVE-2026-48105 was first published on August 21, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48105 actively exploited?
CVE-2026-48105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48105?
CVE-2026-48105 has a CVSS base score of 8.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48105?
No fix for CVE-2026-48105 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48105?

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

Book a Demo →Browse All CVEs