erroneo.us
Search all guides⌘K

Security Digest · Jun 9, 2026 · Vulnerability · Network edge

Ivanti Sentry CVE-2026-10520: Pre-Auth Root RCE

Unauthenticated OS command injection gives root on Ivanti Sentry; backdoors seen after a public PoC. Fixed in R10.5.2, R10.6.2, R10.7.1. Verify and hunt.

Published By erroneo.us Security Desk · Updated 3 min read11 sources

Our verdict

Check exposure

Fixed since June 2026, and exploited within two days of a public PoC. Confirm every Sentry runs R10.5.2, R10.6.2, R10.7.1 or later and that port 8443 is not internet-facing. Treat any appliance that was exposed and unpatched as compromised.

Who must act: Organizations running Ivanti Sentry before R10.5.2, R10.6.2 or R10.7.1, above all any appliance whose management interface (port 8443) was reachable from the internet or that sat in an unmanaged state.

Who can relax: Sentry appliances managed by EPMM (APIs behind mTLS) or by Neurons for MDM, whose management port was never exposed. Ivanti says they are far harder to reach, but they still need the update.

Affected
Ivanti Sentry 10.5.1 and earlier
Ivanti Sentry 10.6.1 and earlier
Ivanti Sentry 10.7.0 and earlier
Fixed in
Ivanti Sentry R10.5.2
Ivanti Sentry R10.6.2
Ivanti Sentry R10.7.1
CVSS
10.0 (v3.1, vendor)
EPSS
99.9% (percentile 100.0)
CISA KEV
Yes, listed as known exploited
Exploitation
Exploited in the wild
Severity
Critical

What to do

  1. List every Sentry appliance, its version, and whether EPMM or Neurons for MDM manages it.
  2. Upgrade to R10.5.2, R10.6.2 or R10.7.1 (or later) on the matching release line.
  3. Block internet access to the Sentry management port 8443 and the /mics/ API; allow only admin networks and the managing EPMM or Neurons service.
  4. Before patching any appliance that was exposed, preserve logs and, where possible, a disk and memory image, following CISA's BOD 26-04 triage guidance.
  5. If exploitation is suspected, rebuild the appliance from a fixed image rather than cleaning it, and rotate its admin accounts, certificates and backend credentials.

How to check if you are affected or compromised

  • Search proxy, load balancer and firewall logs for POST requests to /mics/api/v2/sentry/mics-config/handleMessage, especially from outside the admin network.
  • Look for request bodies beginning 'execute system /configuration/system/commandexec' (the public PoC format).
  • Review Sentry administrator accounts for any nobody created; CVE-2026-10523 lets attackers add admins.
  • Check Shadowserver's free reports for your IP space, which flagged backdoored Sentry hosts in June 2026.

What happened#

On June 9, 2026, Ivanti fixed two flaws in Sentry, its in-line gateway for mobile device traffic (formerly MobileIron Sentry). CVE-2026-10520 is an OS command injection that lets a remote, unauthenticated attacker run commands as root, and Ivanti scores it CVSS 3.1 10.0. CVE-2026-10523, scored 9.9, is an authentication bypass that lets an attacker create administrator accounts. At release, Ivanti said it was "not aware of any customers being exploited," per Rapid7.

A day later, watchTowr diffed the patch and published a proof-of-concept exploit. The bug is in POST /mics/api/v2/sentry/mics-config/handleMessage, whose message parameter reached a system command. The fix swaps attacker input for a hardcoded harmless command. Help Net Security relayed Shadowserver's findings: many exploit attempts based on the public PoC, and at least two of 19 vulnerable instances it could see already backdoored. CISA added CVE-2026-10520 to KEV on June 11 with a three-day deadline. BleepingComputer reports it was the first KEV entry handled under the new BOD 26-04.

Who is affected#

Sentry 10.5.1, 10.6.1, 10.7.0 and earlier releases on each line are affected. The fixes are R10.5.2, R10.6.2 and R10.7.1. CISA's KEV entry spells out the precondition. Exploitation works when the appliance is in an unmanaged state with its endpoints reachable from outside. mTLS with EPMM, or restricted HTTPS access through Neurons for MDM, closes those interfaces to external attackers.

Do you really need to act?#

For most customers, exposure was narrow, but the cost of being wrong is high. Ivanti told Security Affairs that exploitation needs access to management port 8443, which "should never be exposed to the internet." It added that a managed Sentry protects the vulnerable APIs, and that the KEV listing followed attacks on honeypots. Shadowserver's numbers back up a small attack surface: it could see just over 50 exposed Sentry admin portals. But its finding that some were backdoored shows that real, misconfigured appliances were hit.

  • Unpatched, with 8443 exposed at any point since June 10: assume compromise.
  • Patched quickly, port 8443 internal only: verify the version and move on.

What to do now#

  1. Inventory Sentry appliances, their release line and how each is managed.
  2. Upgrade to R10.5.2, R10.6.2 or R10.7.1 or later.
  3. Close port 8443 and /mics/ to the internet, and test from outside with curl -sk --max-time 10 -o /dev/null -w '%{http_code}' https://<sentry>:8443/. A result of 000 means it is unreachable.
  4. Before patching a device that was exposed, collect logs and images. CISA's BOD 26-04 guidance sets the order: evidence first, then patch, then triage.
  5. Rebuild compromised appliances from a fixed image, and rotate admin accounts and any certificates or credentials they held.

How to tell if you were hit#

Ivanti has published no indicators of compromise. Search upstream proxy and firewall logs for POSTs to handleMessage from anywhere other than your admin network or managing service. Where request bodies are logged, look for execute system /configuration/system/commandexec, the format used in the public exploit. List Sentry administrators and remove any account nobody created, since CVE-2026-10523 creates admins without credentials. Shadowserver's free network reports flagged backdoored Sentry hosts. If your IP space appeared, treat it as confirmed compromise. Patching does not remove an implant.

Timeline#

  • — Ivanti releases fixes and an advisory for CVE-2026-10520 and CVE-2026-10523, with no known exploitation.
  • — watchTowr publishes its analysis and exploit, and CERT-EU issues an advisory. CISA issues BOD 26-04.
  • — CISA adds CVE-2026-10520 to KEV, with a federal due date of June 14. By then, Shadowserver had reported backdoored instances.
  • — Ivanti tells reporters that exploitation needs access to port 8443 and that the KEV listing followed attacks on honeypots.

Vulnerability records

  • CVE-2026-10520 · KEV 2026-06-11 · An OS Command Injection vulnerability in Ivanti Sentry before the R10.5.2, R10.6.2 and R10.7.1 versions allows a remote unauthenticated user to achieve…
  • CVE-2026-10523 · An Authentication Bypass vulnerability (CWE-288) in Ivanti Sentry before the R10.5.2, R10.6.2 and R10.7.1 versions allows a remote unauthenticated attacker to…

Sources

Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.

Original and primary sources

  1. CVE record — CVE-2026-10520 cve.org
  2. CVE record — CVE-2026-10523 cve.org
  3. NVD — CVE-2026-10520 nvd.nist.gov
  4. CISA — Known Exploited Vulnerabilities: CVE-2026-10520 cisa.gov
  5. CISA — BOD 26-04 implementation guidance: prioritizing security updates based on risk cisa.gov
  6. watchTowr Labs — Ivanti Sentry pre-auth OS command injection (CVE-2026-10520) labs.watchtowr.com
  7. Rapid7 — CVE-2026-10520, CVE-2026-10523: Multiple critical vulnerabilities affecting Ivanti Sentry rapid7.com
  8. CERT-EU — Security Advisory 2026-008: Critical vulnerabilities in Ivanti Sentry cert.europa.eu

Coverage and analysis

  1. Help Net Security — Critical Ivanti Sentry flaw allows root-level remote code execution helpnetsecurity.com
  2. BleepingComputer — CISA gives feds 3 days to patch Ivanti flaw exploited in attacks bleepingcomputer.com
  3. Security Affairs — CISA adds Ivanti Sentry flaw to its Known Exploited Vulnerabilities catalog securityaffairs.com