If your organisation runs Ivanti Sentry, stop what you're doing and read this now. A maximum-severity vulnerability disclosed just days ago is already being actively exploited in the wild — and the window between patch release and mass compromise was measured not in weeks or days, but in hours. This is exactly the kind of race-against-the-clock scenario that separates security-mature IT teams from those who end up in an incident response report.

Here's everything you need to know about CVE-2026-10520, why it matters, and — most critically — what you need to do right now.

What Is CVE-2026-10520? A Breakdown of the Vulnerability

On June 9, 2026, Ivanti published a security advisory for two critical vulnerabilities affecting Ivanti Sentry (formerly known as MobileIron Sentry), which per the vendor website is an "in-line gateway that manages, encrypts, and secures traffic between the mobile device and back-end enterprise systems."

The most severe issue, CVE-2026-10520, is an OS command injection vulnerability with a CVSS score of 10.0 that allows a remote unauthenticated attacker to achieve remote code execution (RCE) with root privileges.

A perfect 10. There is no higher rating on the scale.

Based upon the technical analysis by watchTowr, CVE-2026-10520 resides in the ConfigServiceController class within the Sentry web application, which is accessible via a POST request to the unauthenticated endpoint /mics/api/v2/sentry/mics-config/handleMessage.

The handleMessage endpoint accepts an attacker-supplied message parameter that is parsed as an internal configuration command, ultimately resulting in arbitrary OS command execution as root with attacker-controlled input.

A second vulnerability was also disclosed at the same time.

CVE-2026-10523 is an authentication bypass vulnerability with a CVSS score of 9.9 that allows a remote unauthenticated attacker to create arbitrary administrative accounts and obtain full administrative access.

The two flaws form a complete attack chain: use CVE-2026-10523 to create a privileged account, then leverage CVE-2026-10520 to execute root-level commands at will.

Why Ivanti Sentry Is Such a High-Value Target

Ivanti Sentry sits inline between an organisation's mobile device fleet and its backend corporate systems — most commonly Microsoft Exchange for ActiveSync email traffic. A root-level compromise of Sentry is equivalent, in practice, to unrestricted access to every mailbox, calendar, and enterprise application the appliance brokers.

Achieving root-level access on a Sentry instance via exploitation of CVE-2026-10520 could give a threat actor control over the appliance's configurations, stored credentials, and integrated authentication or directory connections, according to SOCRadar.

For threat actors, this isn't just a foothold — it's a masterkey.

The 24-Hour Exploitation Timeline: What Actually Happened

The speed of exploitation here is genuinely alarming and serves as a case study for why "patch when convenient" is no longer an acceptable policy.

Ivanti stated that they were not aware of any customers being exploited by either of these vulnerabilities at the time of disclosure.

That was Tuesday, June 9.

On June 10, 2026, watchTowr published a technical analysis of CVE-2026-10520 that includes a proof-of-concept exploit.

Then the floodgates opened.

The Shadowserver nonprofit security organisation reported the next day that attackers had already backdoored most of the Sentry gateways exposed online.

Defused founder and CEO Simo Kohonen told Dark Reading that attacks had been "pretty much non-stop active after the release of the watchTowr PoC," with a notable characteristic: attackers launched exploits directly against honeypots with no prior system fingerprinting, indicating fully automated, scripted exploitation at scale.

This is the terrifying detail: attackers didn't bother to manually research targets. They simply ran automated scripts against every exposed Sentry instance they could find.

Shadowserver began sharing indicators through its Vulnerable HTTP and Compromised Website reporting feeds, tagging affected systems with identifiers such as "cve-2026-10520" and "ivanti-sentry,injected-code,backdoor."

CISA cited AI-accelerated weaponisation as the central driver for the compressed timeline, noting that the speed at which adversaries can develop and deploy working exploits has made the traditional patch cadence operationally obsolete.

CISA's Response: A Historic 3-Day Patch Mandate

The U.S. government's reaction to this vulnerability was itself unprecedented.

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) ordered government agencies to patch an actively exploited Ivanti Sentry flaw within three days, as mandated by the newly issued Binding Operational Directive (BOD) 26-04.

The directive, BOD 26-04, titled "Prioritising Security Updates Based on Risk," was issued June 10, 2026. It supersedes both BOD 22-01 — the 2021 directive that established the Known Exploited Vulnerabilities catalog — and BOD 19-02, which governed remediation timelines for internet-accessible systems. The consolidation brings vulnerability remediation for all federal civilian agencies under a single, unified risk-based framework for the first time.

The addition of CVE-2026-10520 to the KEV catalog and the three-day deadline follow BOD 26-04, which sets out new requirements for federal civilian executive branch agencies to remediate security vulnerabilities based on four main factors: asset exposure, KEV status, exploit automation potential, and technical impact. The new remediation timelines shorten deadlines to three days when certain combinations of criteria are met — for example, when the flaw is both in the KEV catalog and enables total control of affected systems, while also involving publicly exposed assets.

While this mandate applies directly to federal agencies,

CISA strongly recommends that all organisations, including state and local governments, critical infrastructure, and private sector companies, apply the patch within the same timeframe.

The Broader Context: Ivanti's Troubling Track Record

It's essential to understand that this is far from an isolated incident. Ivanti products have been repeatedly and heavily targeted by threat actors for years.

CISA has now flagged 35 vulnerabilities across Ivanti's product line as actively exploited in attacks since 2020, 12 of which were leveraged in ransomware campaigns.

Hackers often target Ivanti security flaws because they provide an entry point into targets' enterprise networks, enabling the theft of sensitive customer and corporate data.

One of the most impactful campaigns of 2024 leveraged two Ivanti vulnerabilities to compromise thousands of Ivanti Connect Secure VPN devices.

The problem isn't just disclosure velocity — it's organisational patching behaviour.

Swimlane research found 68% of organisations leave critical flaws unpatched for over 24 hours, and 55% don't have a comprehensive system for prioritising vulnerabilities.

The 2026 Verizon Data Breach Investigations Report notes that exploitation of vulnerabilities is now the leading initial access vector in confirmed breaches at 31%, while the rate at which organisations fully remediated KEV-catalog vulnerabilities fell from 38% to just 26% between 2024 and 2025. The median time organisations took to resolve a KEV vulnerability in 2025 was 43 days — against a three-day requirement for the highest-risk tier.

That gap between 43 days and 3 days is where breaches happen.

Which Versions Are Affected and What Is the Official Fix?

The vulnerability is classified under CWE-78 (OS Command Injection) and affects Ivanti Sentry versions 10.5.1, 10.6.1, 10.7.0, and earlier.

The maximum-severity vulnerability was patched by Ivanti on Tuesday with the release of Sentry versions R10.5.2, R10.6.2, and R10.7.1.

Check CVE-2026-10523 as well — both vulnerabilities affect the same versions and require the same patch.

Ivanti patched CVE-2026-10520 by replacing the user-controlled input in the handleMessage path with hardcoded commands and adding an authentication interceptor upstream of the vulnerable Spring controller mapping, effectively adding a credential gate in front of the endpoint that previously had none.

For additional protection configuration:

Ivanti explained that Sentry instances managed by EPMM are protected from this vulnerability by mTLS, while instances managed by Neurons for MDM should not have the management interface exposed to the internet.

Practical Tips: What IT Teams Must Do Right Now

The following steps are drawn from CISA guidance, Ivanti's own advisory, and expert recommendations from the security research community. Treat these as immediate action items, not a to-do list for next week.

1. Identify All Ivanti Sentry Instances

Query internal DNS for common Sentry naming patterns: sentry-, gateway-, mobilegateway-, mobile-security-, mobileiron-, ivanti-. Sentry appliances are often deployed alongside EPMM infrastructure, so look for related hosts like epmm- or mdm- — they may point to the same deployment.

2. Apply the Patch Immediately

Patch Ivanti Sentry to R10.5.2, R10.6.2, or R10.7.1, then review exposed gateways, administrator accounts, logs, mobile traffic, and customer access.

This is not optional. If your Sentry instance is internet-facing and unpatched, assume compromise.

3. Run the Integrity Checker Tool

Ivanti and CISA have published instructions for mitigating vulnerabilities, emphasising that network defenders should run Ivanti's built-in Integrity Checker Tool (ICT) to seek out infections, and implement patches immediately.

4. Conduct Threat Hunting on Connected Systems

Conduct threat hunt actions on any systems connected to — or recently connected to — the affected Ivanti device.

A compromised Sentry gateway should be treated as a full network intrusion, not a contained appliance issue.

5. Perform a Factory Reset If Compromise Is Suspected

If threat hunting actions determine no compromise, conduct a factory reset for the highest level of confidence. For cloud and virtual systems, conduct a factory reset using an external known-clean image of the device.

6. Restrict Management Interface Exposure

Ensure that Sentry management interfaces are not publicly accessible.

The vulnerability is trivially exploitable on internet-exposed Sentry appliances not protected by mTLS with EPMM or restricted HTTPS through Neurons for MDM.

7. Report Incidents to CISA

Report to CISA and Ivanti immediately. Organisations should report incidents and anomalous activity to CISA's 24/7 Operations Centre at Report@cisa.gov or (888) 282-0870.

8. Build a Risk-Based Patching Programme

The days of waiting for monthly patch cycles to address maximum-severity, actively exploited vulnerabilities are over.

The purpose of assigning a CVE is to provide a beacon to security teams and signal the need for urgent updates.

Ensure your team has a tiered SLA for critical CVEs that mandates same-day or next-day action when CVSS scores hit 9.0 or above and active exploitation is confirmed.

Conclusion: The Patch Window Is Now Measured in Hours

The Ivanti Sentry CVE-2026-10520 incident is a defining moment in enterprise vulnerability management. A CVSS 10.0 flaw went from disclosure to mass exploitation in under 24 hours, with automated attack scripts hammering every exposed instance before most IT teams had even read the advisory. CISA's unprecedented 3-day patch mandate under the new BOD 26-04 framework reflects a hard truth: the old norms around patch timelines are dangerously out of step with the speed of modern adversaries.

If your organisation runs Ivanti Sentry, the time to act was yesterday — but right now is still better than tomorrow. Patch to R10.5.2, R10.6.2, or R10.7.1 immediately, run the Integrity Checker Tool, restrict your management interface exposure, and assume any unpatched public-facing instance has already been compromised. Share this post with your security and IT operations teams, bookmark CISA's Known Exploited Vulnerabilities catalog, and make it a standing protocol to treat any KEV-listed, CVSS 10.0 vulnerability as an all-hands emergency. In today's threat landscape, your patch cadence is your first line of defence — make sure it's up to the task.