A improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiSIEM 7.5.0 may allow attacker to execute unauthorized code or commands via specially crafted packets.
CVE-2026-106173
CRITICALPre-NVD 9.49.8Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
“▲” beside the score: it is higher than the CVSS score beside it.
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-13. The CNA's CVSS baseline 9.4; sources differ by 0.4.
Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, GitHub Security Advisory
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).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 9.4Exploit: None knownExposed services: Not assessed
Upgrade to FortiSOC version 26.2.2 or above (from the CVE record's solution, Fortinet, Inc.) — apply it.
- CVSS v3
- 9.4
- EG Score
- 9.8CRITICALhigh confidence
- EG Risk
- 59EG Risk 59/100
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 (value × EchelonGraph’s weight)Severity98% × 45%The EG Score, 9.8 of 10.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.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 none (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 FortiSOC version 26.2.2 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
- —
- EPSS %ILE
- —
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
Upgrade to FortiSOC version 26.2.2 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 none (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.
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
October 14, 2026
Advisory Details (1)
Auto-updated Oct 14, 2026Fix named in the CVE record's solution (Fortinet, Inc.).
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 13× in last 7d / 13× 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.
- 2026-10-14 10:55 UTCEG score recompute
- 2026-10-14 10:55 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-14 10:54 UTCMITRE cvelistV5CVSS v3 → 9.4
- 2026-10-14 04:26 UTCEG score recompute
- 2026-10-14 04:26 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-14 04:25 UTCNVD updateCVSS v3 → 9.8
- 2026-10-14 04:06 UTCEG score recompute
- 2026-10-14 04:06 UTCGHSA enrichmentGHSA-5cx2-chqq-627m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-14 04:04 UTCMITRE cvelistV5CVSS v3 → 9.4
- 2026-10-13 18:26 UTCEG score recompute▲ 0.40
- 2026-10-13 18:25 UTCNVD updateCVSS v3 → 9.8
- 2026-10-13 17:52 UTCEG score recomputeFirst assessed: 9.4 CRITICAL
- 2026-10-13 17:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
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 may allow attacker to execute unauthorized code or commands via specially crafted packets.
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 October 14, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-106173?
CVE-2026-106173 has a CVSS base score of 9.4 (the CNA's own assessment, by fortinet; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
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 FortiSOC version 26.2.2 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
Is Your Infrastructure Affected by CVE-2026-106173?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.