Skip to main content
Mallory
CriticalPublic exploit

Pre-auth OS Command Injection in Ivanti Sentry

IdentifiersCVE-2026-10520CWE-78· Improper Neutralization of Special…

CVE-2026-10520 is a critical OS command injection vulnerability in Ivanti Sentry affecting versions prior to R10.5.2, R10.6.2, and R10.7.1. Available reporting indicates that user-supplied parameters are not properly sanitized before being passed to internal shell layers, enabling command injection. The issue is reachable remotely without authentication and can be exploited to execute attacker-controlled commands in a root context on the appliance.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote unauthenticated attacker to achieve root-level remote code execution on the affected Ivanti Sentry appliance. Given the root execution context, compromise can result in full administrative takeover of the system, including complete loss of confidentiality, integrity, and availability, as reflected by the reported critical severity and CVSS characteristics.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of Ivanti Sentry management and reachable interfaces to trusted networks only, restrict inbound access as tightly as operationally possible, and monitor for suspicious command execution or anomalous appliance behavior. Review defensive telemetry and logs for signs of compromise and validate local access permissions. However, no mitigation is described as equivalent to installing the vendor fix.

Remediation

Patch, then assume compromise.

Upgrade Ivanti Sentry to a fixed release: R10.5.2, R10.6.2, R10.7.1, or later vendor-provided versions that include the patch. Ivanti has published a security advisory for CVE-2026-10520 and organizations should apply the official maintenance update immediately. Ivanti also made a Detection Artefact Generator available to help assess affected environments.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
watchTowr-vs-Ivanti-Sentry-RCE-CVE-2026-10520-CVE-2026-10523MaturityPoCVerified exploit

This repository is a small, single-purpose Python proof-of-concept for Ivanti Sentry authentication bypass and remote code execution associated with CVE-2026-10520 and CVE-2026-10523. The repo contains only two files: a README with usage/output examples and one Python script that performs the attack. The script is not part of a larger exploitation framework. The main capability is unauthenticated remote command execution against an Ivanti Sentry target. The operator supplies a base URL and an arbitrary command via --cmd. The script constructs a POST request to the Ivanti Sentry endpoint /mics/api/v2/sentry/mics-config/handleMessage with Content-Type application/x-www-form-urlencoded and a crafted message parameter containing an XML-like commandexec structure. It disables TLS certificate verification, optionally supports an HTTP proxy, and does not follow redirects. After sending the request, the script parses the response body and optionally JSON-decodes it. It checks for success markers ('Message handled successfully' and '<result><success>...') and extracts the command output with a regular expression. If extraction succeeds, it reports the target as vulnerable and prints the returned command output; otherwise it reports the target as not vulnerable. Repository structure is minimal and operational: README.md documents the vulnerability and demonstrates exploitation, while watchTowr-vs-Ivanti-Sentry-RCE-CVE-2026-10520-CVE-2026-10523.py is the executable entry point. Although described as a 'Detection Artifact Generator,' the code actively triggers command execution on the target, so it functions as a real exploit/verification tool rather than a passive detector.

watchtowrlabsDisclosed Jun 9, 2026pythonmarkdownnetworkweb
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity13

Community discussion across Reddit, Mastodon, and other social sources.