Ivanti Sentry appliances — enterprise MDM gateways that control mobile device access to internal corporate resources including email, SharePoint, and proprietary applications — are being actively backdoored following the publication of a CVSS 10.0 pre-authentication remote code execution vulnerability. CISA added CVE-2026-10520 to its Known Exploited Vulnerabilities catalog on 11 June 2026 with a remediation deadline of 14 June, one of the shortest windows the agency has issued, reflecting the severity of confirmed in-the-wild exploitation.
The Vulnerability
CVE-2026-10520 is an OS command injection flaw (CWE-78) in the Sentry management interface — the MICS (Mobility Infrastructure Configuration Service) web application. An unauthenticated attacker can send a crafted HTTP POST to /mics/api/v2/sentry/mics-config/handleMessage and achieve root-level command execution on the appliance. No credentials, no user interaction, no prior access of any kind are required.
WatchTowr, which published a full technical analysis and working proof-of-concept on 10 June — one day after Ivanti’s advisory — confirmed the exploit is straightforward to reproduce. The MICS management interface reaches the vulnerable code path before any authentication is evaluated.
A companion vulnerability, CVE-2026-10523 (CVSS 9.9), was disclosed in the same advisory and allows unauthenticated creation of administrative accounts. Both are addressed by the same patch releases: Sentry 10.5.2, 10.6.2, and 10.7.1.
Exploitation Timeline
The window between advisory and confirmed backdooring was under 48 hours. The Shadowserver Foundation, which conducts internet-wide scanning for exploitation evidence, confirmed that at least two of nineteen publicly-accessible vulnerable Sentry instances it scanned had already been compromised and backdoored by 11 June. This is active exploitation against production systems, not merely scanning or probing activity.
Ivanti’s network-connected security appliances have been a persistent target for sophisticated threat actors. CVE-2023-46805 and CVE-2024-21887 in Ivanti Connect Secure were exploited by UNC5221, a China-nexus group, to establish persistent access in government and defence networks globally. CVE-2026-10520 has not yet been attributed to a specific threat actor.
Sector Exposure
Ivanti Sentry sits at the authentication perimeter of enterprise mobile device fleets. Organisations across healthcare, financial services, telecommunications, and critical infrastructure sectors deploy it as the gateway through which clinical mobile devices, corporate smartphones, and BYOD endpoints access internal systems.
A compromised Sentry appliance gives an attacker an authenticated position inside the enterprise perimeter — able to proxy connections into internal Exchange servers, SharePoint environments, and proprietary applications that mobile devices are permitted to reach. In regulated sectors, this includes patient record systems, trading infrastructure, and operational technology management interfaces exposed through mobile workflows.
Sentry’s role as an MDM gateway also means compromise can expose the MDM management plane, potentially giving attackers insight into enrolled device inventories, configuration profiles, and certificate authorities used for device authentication.
Recommended Actions
Organisations running Ivanti Sentry should treat remediation as an emergency action, not a scheduled maintenance task:
Patch immediately. Upgrade to 10.5.2, 10.6.2, or 10.7.1 depending on installed version. The CISA deadline for federal agencies is 14 June; all organisations should treat this as the target regardless of federal affiliation.
Verify MICS interface exposure. Confirm that port 8443 (MICS) is not accessible from the internet or from network segments broader than approved management infrastructure. If external exposure exists, isolate immediately while the patch is applied.
Conduct post-patch forensics. Given the Shadowserver confirmation of active backdooring, patching alone is insufficient for organisations whose appliances were potentially exposed before remediation. Look for unexpected processes, new accounts, modified startup scripts, and unusual outbound connections from the Sentry appliance.
Rotate adjacent credentials. If the Sentry appliance had access to internal Exchange or SharePoint environments during the exposure window, assess whether those service accounts or certificates may have been observed by an attacker and rotate accordingly.
The 48-hour backdooring timeline — from public advisory to confirmed production compromise — is consistent with the rapid weaponisation pattern Ivanti’s product line has attracted over the past three years. Organisations with unpatched Sentry appliances should not assume they are uncompromised.