Ivanti has issued an urgent warning to customers regarding two critical vulnerabilities in its Ivanti Sentry product, a key component for mobile device management security. The most critical of these, CVE-2026-10520, is an OS command injection flaw that can be exploited by a remote, unauthenticated attacker to gain root-level control over the appliance. A second vulnerability, CVE-2026-10523, allows an attacker to bypass authentication and create new administrator accounts. Although Ivanti reports no active exploitation, security firm WatchTowr has publicly released technical details and a vulnerability scanner for CVE-2026-10520. This disclosure dramatically shortens the window for defenders to act before exploits are developed and deployed. A compromised Sentry appliance provides a gateway to backend corporate resources, including email and internal applications, making these vulnerabilities an immediate and critical threat.
CVE-2026-10520: This is a critical OS command injection vulnerability. Researchers at WatchTowr discovered that a specific API endpoint intended for internal configuration was exposed to the internet without requiring authentication. An attacker can send specially crafted commands to this endpoint, which are then executed on the underlying operating system with root privileges. This provides a direct path to full system compromise.CVE-2026-10523: This is an authentication bypass vulnerability. While fewer technical details are available, it reportedly allows an attacker to create new administrative accounts on the Sentry device. This could be used to establish persistence or as a stepping stone to further exploit the system.Chaining these two vulnerabilities could allow an attacker to gain full control, create persistent access, and then use the Sentry appliance's trusted position to pivot into the internal network.
The vulnerabilities affect the following versions of Ivanti Sentry (formerly MobileIron Sentry):
Ivanti has released patched versions 10.5.2, 10.6.2, and 10.7.1 to address these issues.
As of June 10, 2026, Ivanti has stated there is no evidence of these vulnerabilities being exploited in the wild. However, the public release of technical analysis and a scanning tool by WatchTowr makes exploitation highly likely in the near future. Threat actors are known to actively target vulnerabilities in edge devices like Ivanti products, often within hours or days of public disclosure.
The impact of exploiting these vulnerabilities is severe. The Ivanti Sentry appliance functions as a critical security gateway, mediating access between mobile devices (smartphones, tablets) and a company's backend resources like Microsoft Exchange Server and other internal applications. A successful attacker could:
Given its role as a trusted intermediary, a compromised Sentry device is a catastrophic security failure.
The following patterns may help identify vulnerable or compromised systems:
/mifs/services/config/CVE-2026-10520.CVE-2026-10523.bash, sh, nc, curl/mifs/services/config/ path from external IP addresses. This leverages D3FEND's Web Session Activity Analysis (D3-WSAA).Applying the security updates provided by Ivanti is the primary and most effective mitigation.
Mapped D3FEND Techniques:
Restrict network access to the Sentry appliance's management interface from the internet. It should only be accessible from trusted internal networks.
Mapped D3FEND Techniques:
The highest priority action is to immediately upgrade all Ivanti Sentry appliances to the patched versions (10.5.2, 10.6.2, or 10.7.1). Due to the critical nature of CVE-2026-10520 (unauthenticated root RCE) and the public availability of technical details, the window for exploitation is extremely small. Standard patch testing cycles should be accelerated or bypassed for these internet-facing, critical security appliances. After patching, use a vulnerability scanner to verify that the patch has been successfully applied and the vulnerability is no longer exposed.
As an immediate compensating control while patching is underway, use a firewall or WAF to block all external access to the Sentry appliance's management interface and specifically the /mifs/services/config/ API endpoint. This interface should never be exposed to the public internet. Create an explicit deny rule for this path on your WAF. For long-term hardening, configure firewall rules to ensure the management interface is only accessible from a dedicated, secured management subnet within your internal network. This directly prevents remote, unauthenticated attackers from reaching the vulnerable code path.
Even after patching, assume the appliance may have been compromised. Enable process execution logging on the Sentry appliance itself (if possible via the underlying OS) or use an EDR agent in monitoring mode. Hunt for any anomalous process creation originating from the main Sentry application process (likely a Java process). Specifically, look for the execution of shell interpreters (sh, bash), networking tools (curl, wget, nc), or any other binaries not part of the appliance's normal operation. A baseline of normal process activity should be established, and any deviation should be investigated as a potential sign of compromise.
Ivanti releases patches and an advisory for critical vulnerabilities CVE-2026-10520 and CVE-2026-10523.
Security firm WatchTowr publishes technical details and a scanner for CVE-2026-10520.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.