CVE-2026-106173

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-13. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-98968 (ENISA EUVD) · GHSA-5cx2-chqq-627m (GitHub Security Advisories)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).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

Upgrade to FortiSIEM version 7.6.0 or above (from the CVE record's solution, Fortinet, Inc.) — apply it.

A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiSIEM 7.5.0, FortiSIEM 7.4 all versions, FortiSIEM 7.3 all versions, FortiSIEM 7.2 all versions, FortiSIEM 7.1 all versions, FortiSIEM 7.0 all versions may allow attacker to execute unauthorized code or commands via specially crafted packets.

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: Upgrade to FortiSIEM version 7.6.0 or above (from the CVE record's solution, Fortinet, Inc.). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.0%
EPSS %ILE
63rd
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.GitHub Security Advisory CVSS
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-13). 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.

Upgrade to FortiSIEM version 7.6.0 or above (from the CVE record's solution, Fortinet, Inc.). 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

October 13, 2026

Last Modified

November 10, 2026

Advisory Details (2)

Auto-updated Nov 7, 2026
🔬 Proof of concept available. Fix named in the CVE record's solution (Fortinet, Inc.).
Web page🟡 PoC Available

GitHub - horizon3ai/CVE-2026-106173: Proof of concept exploit for CVE-2026-106173, a path traversal file write leading to RCE for Fortinet FortiSIEM · GitHub

https://github.com/horizon3ai/CVE-2026-106173

Vendor Advisories for CVE-2026-106173(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 76× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 132 rows 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 32 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 17:36 UTCEchelonGraph re-scored
  2. 2026-11-13 17:36 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-13 16:50 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  4. 2026-11-12 18:33 UTCEchelonGraph re-scored
  5. 2026-11-12 18:33 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-12 17:11 UTCEchelonGraph re-scored
  7. 2026-11-12 17:11 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-12 16:32 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  9. 2026-11-11 18:49 UTCEchelonGraph re-scored
  10. 2026-11-11 18:49 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-11 16:37 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  12. 2026-11-10 20:28 UTCEchelonGraph re-scored
  13. 2026-11-10 20:27 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-10 20:27 UTCNVD updateCVSS v3 → 9.8
  15. 2026-11-10 20:15 UTCEchelonGraph re-scored
  16. 2026-11-10 20:15 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-11-10 20:15 UTCMITRE cvelistV5CVSS → 9.4
  18. 2026-11-10 16:41 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  19. 2026-11-10 13:11 UTCEchelonGraph re-scored
  20. 2026-11-10 13:11 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-11-09 16:34 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  22. 2026-11-09 14:47 UTCEchelonGraph re-scored
  23. 2026-11-09 14:47 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-08 16:38 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  25. 2026-11-08 16:26 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-11-07 23:59 UTCEchelonGraph re-scored
  2. 2026-11-07 23:59 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-07 16:38 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  4. 2026-11-07 01:38 UTCEchelonGraph re-scored
  5. 2026-11-07 01:38 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-06 16:35 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  7. 2026-11-06 03:17 UTCEchelonGraph re-scored
  8. 2026-11-06 03:17 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-05 16:36 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  10. 2026-11-05 04:56 UTCEchelonGraph re-scored
  11. 2026-11-05 04:56 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  13. 2026-11-04 06:35 UTCEchelonGraph re-scored
  14. 2026-11-04 06:35 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-03 16:46 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  16. 2026-11-03 08:13 UTCEchelonGraph re-scored
  17. 2026-11-03 08:13 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-11-02 16:43 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  19. 2026-11-02 09:52 UTCEchelonGraph re-scored
  20. 2026-11-02 09:52 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-11-01 11:31 UTCEchelonGraph re-scored
  22. 2026-11-01 11:30 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-31 16:31 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  24. 2026-10-31 13:09 UTCEchelonGraph re-scored
  25. 2026-10-31 13:09 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-30 16:33 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  27. 2026-10-30 14:45 UTCEchelonGraph re-scored
  28. 2026-10-30 14:45 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-29 16:32 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  30. 2026-10-29 16:25 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-29 09:18 UTCEchelonGraph re-scored
  32. 2026-10-29 09:17 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-28 16:31 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  34. 2026-10-28 10:57 UTCEchelonGraph re-scored
  35. 2026-10-28 10:57 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-27 16:31 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  37. 2026-10-27 11:41 UTCEchelonGraph re-scored
  38. 2026-10-27 11:41 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-26 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  40. 2026-10-26 13:21 UTCEchelonGraph re-scored
  41. 2026-10-26 13:21 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-25 16:32 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  43. 2026-10-25 14:48 UTCEchelonGraph re-scored
  44. 2026-10-25 14:48 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  46. 2026-10-24 16:26 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-24 14:46 UTCEchelonGraph re-scored
  48. 2026-10-24 14:46 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  50. 2026-10-23 16:25 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-23 13:33 UTCEchelonGraph re-scored
  52. 2026-10-23 13:33 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  54. 2026-10-22 15:07 UTCEchelonGraph re-scored
  55. 2026-10-22 15:06 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  57. 2026-10-21 16:25 UTCEchelonGraph re-scored
  58. 2026-10-21 16:25 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-21 04:27 UTCEchelonGraph re-scored
  60. 2026-10-21 04:27 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-21 04:26 UTCNVD updateCVSS v3 → 9.8
  62. 2026-10-21 04:05 UTCEchelonGraph re-scored
  63. 2026-10-21 04:05 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-10-21 04:02 UTCMITRE cvelistV5CVSS → 9.4
  65. 2026-10-20 18:27 UTCEchelonGraph re-scored
  66. 2026-10-20 18:26 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-10-20 18:25 UTCNVD updateCVSS v3 → 9.8
  68. 2026-10-20 17:32 UTCEchelonGraph re-scored
  69. 2026-10-20 17:31 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-10-20 17:22 UTCEchelonGraph re-scored
  71. 2026-10-20 17:22 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-10-20 17:21 UTCMITRE cvelistV5CVSS → 9.4
  73. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  74. 2026-10-19 22:22 UTCEchelonGraph re-scored
  75. 2026-10-19 22:22 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8

Publicly available exploits

(6 references)

Public exploit code is referenced for this CVE (6 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • GitHub PoCMRdark-ops/rce-FortiSIEM
    Published Oct 23, 2026

    Proof of concept exploit for CVE-2026-106173, a path traversal file write leading to RCE for Fortinet FortiSIEM

    Open source ↗
  • GitHub PoCtc4dy/CVE-2026-106173-PoC-Exploit
    Published Oct 22, 2026

    CVE-2026-106173 – FortiSIEM phQueryMaster RCE (CVSS 9.8) | Red/Blue Team suite for unpatched FortiSIEM 7.5.0. 2 tools: Full Exploit (multi-primitive RCE, reverse shell, persistence, creds, readback, mass scan, Tor), Blue Team Checker (exposure detection, HTTP/2 fingerprint, reporting, audit). Only Use Ethically, Stay Legal <3

    Open source ↗
  • GitHub PoC0xBlackash/CVE-2026-106173
    Published Oct 20, 2026

    CVE-2026-106173

    Open source ↗
  • GitHub PoC0xredash/CVE-2026-106173
    Published Oct 20, 2026

    CVE-2026-106173

    Open source ↗
  • GitHub PoCashrafzaryouh/CVE-2026-106173
    Published Oct 20, 2026

    CVE-2026-106173

    Open source ↗
  • GitHub PoChorizon3ai/CVE-2026-106173
    Published Oct 20, 2026

    Proof of concept exploit for CVE-2026-106173, a path traversal file write leading to RCE for Fortinet FortiSIEM

    Open source ↗

Frequently asked(5)

What is CVE-2026-106173?
CVE-2026-106173 is a critical-severity vulnerability; its CVE record was published on October 13, 2026. A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiSIEM 7.5.0, FortiSIEM 7.4 all versions, FortiSIEM 7.3 all versions, FortiSIEM 7.2 all versions, FortiSIEM 7.1 all versions, FortiSIEM 7.0 all versions may allow attacker to execute…
When was the CVE record for CVE-2026-106173 published?
The CVE record for CVE-2026-106173 was published on October 13, 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 November 10, 2026; the record at its source may have been updated since.
Is CVE-2026-106173 actively exploited?
CVE-2026-106173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (63rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-106173?
CVE-2026-106173 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-106173?
The CVE record's solution for CVE-2026-106173, written by its CNA Fortinet, Inc., names the fix: "Upgrade to FortiSIEM version 7.6.0 or above". The vendor advisories EchelonGraph has for CVE-2026-106173 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-106173?

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