CVE-2026-10520: Ivanti Sentry OS Command Injection Vulnerability

Quick Answer

CVE-2026-10520 can allow unauthenticated root-level command execution when an Ivanti Sentry appliance is unmanaged and its vulnerable endpoints are externally reachable, according to CISA. Check management state and actual endpoint access first. EPMM mTLS or restricted HTTPS through Neurons for MDM can prevent that external access, but do not establish that the code is patched. Preserve evidence and obtain Ivanti's release-specific remediation; no fixed build is verified here.

Evidence check: Vendor evidence and unresolved source limits are described below. CISA KEV catalog 2026.10.02 was checked on October 2. Preserve the distinction between vendor publication history, catalog dates and evidence from your deployment; no patch or exploit test is claimed.

Context

Status At A Glance

Product scope	Ivanti — Sentry
CVE	CVE-2026-10520
TechGeeks response tier	P0 — confirm an exact match and act now
CISA KEV added	2026-06-11
Vendor severity	Consult the live vendor advisory; no vendor severity is inferred from KEV status.
CVSS	Consult the live vendor advisory; no CVSS value is inferred from KEV status.
Ransomware field	Unknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage field	No in the current CISA field; organizations should still investigate when exposure or evidence warrants it.
CWE	CWE-78
Federal remediation date	2026-06-14 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

Ivanti Sentry OS Command Injection Vulnerability. Ivanti Sentry (formerly known as MobileIron Sentry) contains an OS command injection vulnerability which could allow a remote unauthenticated user to achieve root-level remote code execution. This vulnerability can be successfully exploited in cases where the Sentry appliance is in an unmanaged state with its endpoints externally reachable. The use of mTLS with EPMM or restricted HTTPS access through Neurons for MDM makes interfaces inaccessible to external actors. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.

Affected Scope

Inventory Sentry's management state, enabled endpoints and access controls. CISA names EPMM mTLS and Neurons for MDM HTTPS restrictions as controls that make the interfaces inaccessible to external actors; verify their actual configuration and retain the vendor update requirement.

Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.

Steps

What To Do Now

1. Confirm. Inventory every Sentry asset and record its exact version, patch level, role, relevant configuration, and exposure.
2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Ivanti advisory.
4. Remediate. Confirm the exact product, release, exposure, and prerequisites against the live vendor advisory, then apply the vendor-listed update or mitigation. CISA added CVE-2026-10520 to KEV on 2026-06-11.
5. Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Investigation And Recovery

CISA's KEV record does not mark this entry for forensic triage. That field is not proof of a clean system; consult the vendor advisory for indicators and recovery guidance.

When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.

Notes

Exploitation Evidence

Vendor statement: Ivanti's exact exploitation statement is not established here. CISA separately records this flaw as exploited and added it to KEV on June 11; that does not determine an individual appliance's compromise status.

CISA statement: CVE-2026-10520 was added to KEV on 2026-06-11. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

• TechGeeks Security Notice Center
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Ivanti advisory or support notice
• CISA guidance
• CISA guidance
• NVD CVE record
• CISA source

Wrap-Up

Record whether CVE-2026-10520 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.