CVE Tools
Back to blog

Patch tonight: CVE-2026-10520 is a CVSS 10 pre-auth root shell on Ivanti Sentry

A max-severity command injection in Ivanti Standalone Sentry is being exploited in the wild. No workaround, one fix path — here is the status and what to do.

A network-edge server appliance in a rack with one unit glowing red, indicating a critical remote compromise, while the others stay dark.
A network-edge server appliance in a rack with one unit glowing red, indicating a critical remote compromise, while the others stay dark.

A max-severity pre-auth root shell on Ivanti Sentry — already exploited

In early June 2026, Ivanti disclosed two critical flaws in Standalone Sentry and shipped fixes the same day. The headline, CVE-2026-10520, goes to the top of the triage pile on its numbers alone: a CVSS 10.0, unauthenticated, remote command injection that yields root on the appliance — and CISA has already confirmed it is being exploited.

10.0CVSS base score — the maximumAV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
0.99EPSS — near-certain exploitation likelihood99.93rd percentile of all CVEs
rootAccess gained, with no authenticationOS command injection (CWE-78)
KEVCISA confirms in-the-wild exploitationListed in the Known Exploited Vulnerabilities catalog

What the flaw actually is

CVE-2026-10520 is an OS command injection (CWE-78) in Ivanti Standalone Sentry. Three parts of the CVSS vector matter operationally: PR:N (no authentication required), AV:N (reachable over the network), and S:C — a scope change, meaning the injected command escapes the vulnerable component and runs with the privileges of the underlying host. That combination is why the score is a flat 10.0 and why the advisory describes the result as root-level remote code execution. MITRE maps it to ATT&CK T1059 — Command and Scripting Interpreter (Execution).

FieldCVE-2026-10520 (the RCE)CVE-2026-10523 (the companion)
TypeOS command injectionAuthentication bypass
CWECWE-78CWE-288
CVSS10.0 (Critical)9.9 (Critical)
EPSS0.99 (99.93rd pct)0.47 (98.7th pct)
AuthenticationNone required (pre-auth)None required (pre-auth)
ImpactRoot-level RCECreate admin accounts / full admin
Fixed inR10.5.2 / R10.6.2 / R10.7.1R10.5.2 / R10.6.2 / R10.7.1

Where this ranks right now

EPSS is not severity, it is likelihood — and CVE-2026-10520 sits at the top of the recent batch. Among the critical, network-accessible CVEs CISA added to its KEV catalog in June 2026, the Ivanti Sentry RCE has the highest modeled exploitation probability of the group:

EPSS — selected critical CVEs added to CISA's KEV catalog, June 2026
Ivanti Sentry (CVE-… 99 (26%)PeopleSoft (CVE-202… 92 (24%)Splunk (CVE-2026-20… 88 (23%)Check Point VPN (CV… 70 (19%)ColdFusion (CVE-202… 29 (8%)
LabelValue
Ivanti Sentry (CVE-2026-10520)99
PeopleSoft (CVE-2026-35273)92
Splunk (CVE-2026-20253)88
Check Point VPN (CVE-2026-50751)70
ColdFusion (CVE-2026-48282)29
EPSS = modeled probability of exploitation in the next 30 days, as a %. Live CVE records, July 17 2026. Bars show likelihood, not severity.

Who is exposed

Affected: Ivanti Standalone Sentry below the fixed releases — per NVD, Standalone Sentry prior to 10.5.2, with the vendor's branch-specific fixes being R10.5.2, R10.6.2, and R10.7.1. The risk concentrates on any Sentry whose management interface is reachable from the internet or a wide internal zone. DR/standby units and forgotten branch boxes are the usual blind spots — inventory those too.

From disclosure to exploitation

  1. Ivanti discloses both flaws and ships fixes
    CVE-2026-10520 (CVSS 10.0) and CVE-2026-10523 published; R10.5.2 / R10.6.2 / R10.7.1 released the same day.
  2. Confirmed in-the-wild exploitation
    CISA lists CVE-2026-10520 in its Known Exploited Vulnerabilities catalog.
  3. Technical write-up and proof-of-concept published
    Research firm watchtowr releases a technical analysis and a PoC for the pre-auth RCE. No Metasploit or Nuclei module was on file as of writing.

The attack path in one diagram

CVE-2026-10520 attack chain

  1. Internet attacker
  2. Sentry management interface (no auth required)
  3. Running a version below the fixed release?
  4. OS command injection (CWE-78)
  5. Root-level RCE on the appliance (CVSS 10.0, scope C)
  6. Persistence · credential theft · lateral pivot
  7. Alt path: CVE-2026-10523 auth bypass → mint admin account
  8. Patched release — not affected

Check and fix

  1. Inventory every Ivanti Standalone Sentry instance — including DR/standby and branch units — and record each release.
  2. Confirm the running release. Anything below R10.5.2 (or R10.6.2 / R10.7.1 for its branch) is affected.
  3. Upgrade to the fixed release for your branch: R10.5.2, R10.6.2, or R10.7.1. There is no vendor workaround.
  4. If a vulnerable Sentry was internet-facing, treat it as potentially compromised: review logs and the admin-account list, hunt for unexpected outbound connections, and rotate credentials.
  5. Verify the patch against the Ivanti customer hub for your specific deployment before considering the item closed.

What to trust in this write-up

The bottom line

If you run Ivanti Standalone Sentry below R10.5.2 / R10.6.2 / R10.7.1, this is a patch-tonight problem. Pre-auth root on a network-edge appliance that CISA already sees exploited is the top of the pile — and unlike most criticals, there is no mitigation to buy time with. Find the boxes, upgrade, and assume exposure if any were reachable.

What is CVE-2026-10520?
A CVSS 10.0 OS command injection (CWE-78) in Ivanti Standalone Sentry. It is unauthenticated and remote, and gives root-level code execution on the appliance. CISA lists it in the Known Exploited Vulnerabilities catalog.
Is there a workaround?
No. Ivanti's advisory gives no mitigation short of upgrading. The only remediation is to move to a fixed release (R10.5.2, R10.6.2, or R10.7.1).
Is it being exploited?
Yes. CISA added CVE-2026-10520 to its KEV catalog, which means confirmed in-the-wild exploitation. EPSS is 0.99 — among the highest of any current CVE.
Which versions are fixed?
R10.5.2, R10.6.2, and R10.7.1 — use the release for your branch. Standalone Sentry prior to 10.5.2 is affected.
Is this the same as the Ivanti Connect Secure flaws from 2023–2024?
No. This affects Standalone Sentry, a different product line from Connect Secure / Policy Secure. Separate patch track entirely.

Risk data as of 2026-07-17