Home › Intelligence › Brief
VULNERABILITY BRIEF 🔴 Critical Vulnerability

Critical Unauthenticated RCE in FortiSIEM (CVE-2026-106173) with Public PoC

Researchers released a proof‑of‑concept exploit for CVE‑2026‑106173, a critical unauthenticated remote code execution flaw in Fortinet FortiSIEM. The vulnerability scores 9.4 on CVSS and can be leveraged without credentials, underscoring the need for rapid patching and auditable remediation evidence.

Verisq™ Intelligence · 📅 October 21, 2026 · 📰 thehackernews.com
🔴
Severity
Critical
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
5 recommended
📰
Source
thehackernews.com

Critical Unauthenticated RCE in FortiSIEM (CVE‑2026‑106173) – Public PoC Shows Remote Code Execution

What It Is — Fortinet disclosed a critical path‑traversal flaw (CVE‑2026‑106173) in FortiSIEM that allows an unauthenticated attacker to execute arbitrary code on the management server. The vulnerability received a CVSS 9.4 rating.

Exploitability — A proof‑of‑concept exploit has been published, demonstrating remote code execution without any credentials. No public reports of successful exploitation in the wild yet, but the PoC lowers the barrier for attackers.

Affected Products — FortiSIEM versions prior to the October 2026 security patch (all supported releases).

Why It Matters for Trust & Control Assurance

  • Patch Management Discipline – Demonstrates the need for a documented, continuously‑monitored patch‑lifecycle process that can be presented as audit evidence.
  • Evidence of Remediation – Organizations must capture verifiable proof (e.g., signed patch logs, configuration snapshots) that the fix has been applied across all SIEM instances.
  • Defensible Monitoring – Continuous telemetry that flags unpatched assets or anomalous command execution attempts provides a control‑assurance signal to auditors and customers.

Recommended Actions

  1. Deploy the FortiSIEM October 2026 security update immediately on all affected servers.
  2. Verify the patch version via inventory tools and retain signed patch‑installation logs as evidence.
  3. Enable FortiSIEM’s built‑in integrity‑checking modules to alert on any post‑patch anomalies.
  4. Update your asset‑management database and run a scan to confirm no legacy instances remain.
  5. Document the remediation workflow in your control‑mapping repository for audit readiness.

Source: The Hacker News

📰 Original Source
https://thehackernews.com/2026/10/critical-fortisiem-flaw-gets-public.html ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →