Skip to content

CVE-2026-20324: Cisco Secure Firewall Management Center sftunnel OS Command Injection RCE

HERMES

HERMES THREAT SCORE & CENTRALIZED FIREWALL FABRIC COMPROMISE

Target: Cisco Secure Firewall Management Center (FMC) β€” sftunnel Sensor Daemon
Confidence: 97%
93 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 18 / 20
Threat Activity 18 / 20
Weaponization 19 / 20
Exposure 18 / 20
Prevalence 18 / 20
Impact 20 / 20
Exploit Maturity 19 / 20
Attack Chain Potential 20 / 20
βš–οΈ Divergence & Operational Rationale

Rated CVSS 8.8 and HTS 93 (CRITICAL). The sftunnel protocol connects peripheral Firepower Threat Defense (FTD) sensors to the centralized FMC console. Compromising an edge sensor allows an attacker to inject shell commands into sftunnel configuration exchanges, gaining root execution on the central FMC and subverting the entire firewall fabric.

πŸ•ΈοΈ Connected Knowledge Graph & Provenance

CVE-2026-20324: Cisco Secure Firewall Management Center sftunnel OS Command Injection RCEVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTCisco Secure Firewall Management Center
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

πŸ” Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in Cisco Secure Firewall Management Center documented in Hermes dossier.”

Supporting Verified Evidence:

ParameterTechnical SpecificationOperational Impact
CVE IdentifierCVE-2026-20324Cisco Advisory cisco-sa-fmc-sftunnel-rce-2026
Vulnerability ClassOS Command Injection (CWE-78)Unrestricted root shell command execution
Affected Componentsftunnel Inter-Device Communication SubsystemPort TCP 8305 (Sensor-to-FMC Tunnel)
Authentication RequiredLow Privilege / Sensor Context (PR:L)Valid sensor certificate or authenticated session
User InteractionNone (UI:N)Immediate execution upon packet reception
Scope ImpactUnchanged (S:U)Confined to FMC server (grants control over all sensors)
Privileges Obtainedroot (Host OS)Complete control over firewall policies, logs, and VPN keys
Affected VersionsFMC 7.2 (< 7.2.8), FMC 7.4 (< 7.4.2.1), FMC 7.6 (< 7.6.1)Production Cisco Secure FMC deployments
Remediation TargetFMC 7.2.8 / 7.4.2.1 / 7.6.1Apply official Cisco software update

The sftunnel daemon receives serialized diagnostic telemetry and dynamic route configuration from connected sensors.

graph TD
Sensor["Compromised Managed Sensor / Attacker with Cert"] --> Ingress["Send sftunnel diagnostic payload on TCP 8305"]
Ingress --> Daemon["sftunnel Daemon parses parameter string"]
Daemon --> Script["Invokes internal shell helper: /usr/local/sf/bin/configure_route.sh $PARAM"]
Script --> Injection["Shell Metacharacters '; curl ... | bash' Executed"]
Injection --> Root["Root Code Execution on Central FMC"]
  1. Telemetry and route updates received from the sensor contain parameters passed directly to shell scripts invoked via system() or popen() without parameter sanitization.
  2. An attacker who has compromised an FTD sensor or extracted its mTLS certificate can craft an sftunnel frame containing backticks or semicolons (e.g., eth0; /bin/sh -i ...).
  3. The FMC server executes the embedded command under root privileges.

title: Cisco FMC sftunnel Child Process Execution
id: cve-2026-20324-fmc-sftunnel
status: production
description: Detects sftunnel daemon on Cisco FMC spawning unexpected command shells.
references:
- https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-fmc-sftunnel-rce-2026
author: Hermes Codex DFIR Team
date: 2026-09-17
logsource:
category: process_creation
product: linux
detection:
selection:
ParentImage|endswith: '/sftunnel'
Image|endswith:
- '/bin/sh'
- '/bin/bash'
- '/usr/bin/curl'
- '/usr/bin/nc'
condition: selection
level: critical
tags:
- attack.execution
- attack.t1059.004

  1. T0 Immediate Action (< 24h) β€” Apply Cisco FMC Hotfix: Upgrade FMC to patched releases: 7.2.8, 7.4.2.1, or 7.6.1.
  2. T0 Mitigation β€” Isolate Port 8305: Ensure TCP port 8305 (sftunnel) is accessible exclusively from authenticated, verified IP addresses of registered managed sensors.
  3. T1 Tactical Audit (< 7d) β€” Re-enroll Questionable Sensors: If an edge sensor was suspected of compromise, revoke its certificate and re-register the appliance in FMC.