U.S. Cybersecurity and Infrastructure Security Agency (CISA) adds Ivanti Sentry flaw to its Known Exploited Vulnerabilities catalog.
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) added Ivanti Sentry flaw, tracked as CVE-2026-10520 (CVSS score of 10.0), to its Known Exploited Vulnerabilities (KEV) catalog.
Ivanti Sentry is a secure gateway appliance that sits between an organization’s internal systems and mobile devices, helping companies manage and protect mobile access to corporate resources.
Threat actors have started exploiting the maximum-severity OS command injection flaw in Ivanti Sentry, that allows remote code execution with root privileges.
“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 root-level remote code execution ” reads the advisory.
The vulnerability affects the secure mobile gateway used to protect communications between corporate systems and mobile devices. Although Ivanti initially reported no evidence of active attacks, researchers at Shadowserver found that many internet-exposed Sentry gateways had already been backdoored shortly after the security updates were released.
“We are observing a large amount of Ivanti Sentry CVE-2026-10520 exploitation attempts based on the public PoC today. We see 19 vulnerable instances in our own scans, with at least 2 backdoored (thanks to @NCA_KSA for the tip!). However, all remaining likely compromised too.” the Shadowserver Foundation posted on X. “While our detection is on the lowish side due to multiple Ivanti Sentry instances not reachable in our scans (blocklisted?), if you have not patched you are most likely compromised. Vuln IP data shared in Vulnerable HTTP reporting tagged ‘cve-2026-10520′”
Ivanti has not yet updated its advisory to confirm active exploitation of the issue in attacks in the wild. However, attackers frequently target Ivanti flaws because they can provide direct access into enterprise networks and enable data theft.
Threat actors can specifically target Ivanti Sentry instances mainly because they sit in a very sensitive and powerful position inside enterprise environments.
Ivanti Sentry acts as a gateway between mobile devices and internal corporate systems. That means if an attacker compromises it, they are no longer “outside” the network—they are effectively inside the trusted boundary.
According to Binding Operational Directive (BOD) 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities, FCEB agencies have to address the identified vulnerabilities by the due date to protect their networks against attacks exploiting the flaws in the catalog.
Experts also recommend that private organizations review the Catalog and address the vulnerabilities in their infrastructure.
CISA orders federal agencies to fix the vulnerability by June 14, 2026.
Updated June 14, 2026
An Ivanti spokesperson told Security Affairs:
Ivanti updated the Security Advisory for Sentry on Thursday, June 11, 2026 to reflect the practical risk of CVE-2026-10520. While this CVE carries a CVSS score of 10, the risk posed to customers is decreased significantly based on deployment and configuration.
For EPMM-managed Sentry appliances, the vulnerable APIs are protected by mTLS after management. It is not possible for an unmanaged Sentry to be used in production as the management is what pushes the configuration for device connectivity and authentication.
Ivanti Neurons for MDM managed Sentry appliances should not have the vulnerable API exposed to the internet as it is the management interface. This is clearly documented for both MDM and EPMM.
This CVE was added to the CISA KEV due to reports online that there has been attempted exploitation of honeypots. Successful exploitation requires access to the management port 8443 and this port should never be exposed to the internet. Honeypots often have misconfigurations to identify and track malicious behavior.
Ivanti discovered this CVE with the use of advanced LLM which we have begun integrating into our product security processes. This project has increased the capabilities of our Engineering and Product Security Red Teams to identify and fix vulnerabilities, especially those that are difficult to identify with traditional tooling. We expect that this work will result in an uptick in proactive security disclosures. We see this as a good thing, and an important part of ensuring our products keep pace with modern security requirements in a quickly evolving threat landscape.
Follow me on Twitter: @securityaffairs and Facebook and Mastodon
(SecurityAffairs – hacking, CISA)
