How severe is CVE-2026-10520?

CVE-2026-10520 has a CVSS score of 10/10, rated CRITICAL. Immediate patching is strongly recommended.

Which products are affected by CVE-2026-10520?

Affected package information for CVE-2026-10520 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2026-10520?

Apply the ivanti standalone sentry security patch or hotfix for CVE-2026-10520 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2026-10520 across my infrastructure?

Inventory every ivanti standalone sentry deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2026-10520 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2026-10520?

O3 detects and blocks CVE-2026-10520 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2026-10520 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2026-10520, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

Is CVE-2026-10520 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2026-10520 (Ivanti Sentry OS Command Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-06-11. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-06-14. The required action was: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2026-10520?

CVE-2026-10520 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2026-10520?

CVE-2026-10520 affects ivanti standalone sentry (1 version, e.g. 10.7.0). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2026-10520?

A Nuclei detection template exists for CVE-2026-10520, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2026-10520 published, and has it been updated?

CVE-2026-10520 was published on June 9, 2026 and was last updated on July 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2026-06-11 — agencies required to remediate by 2026-06-14

CVE-2026-10520

CRITICAL

CVE-2026-10520 is a critical-severity (CVSS 10) OS Command Injection vulnerability in ivanti standalone sentry. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-06-11) — treat it as actively exploited and patch now. O3 Security detects and blocks CVE-2026-10520 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

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

Published

Jun 9, 2026

Updated

Jul 23, 2026

Affected

0 pkgs

Patched

None yet

Exploits

2 known

Description

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

Affected Products

1 product · 3 configurations

Application

standalone sentryivanti

≥ 10.6.0 && < 10.6.2

1 version

10.7.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

watchtowrlabs/watchTowr-vs-Ivanti-Sentry-RCE-CVE-2026-10520-CVE-2026-10523

⭐ 13🍴 4Jul 2026

0xBlackash/CVE-2026-10520

CVE-2026-10520

⭐ 4🍴 0Jun 2026

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every ivanti standalone sentry deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the ivanti standalone sentry security patch or hotfix for CVE-2026-10520 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2026-10520 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2026-10520. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Runtime Protection

Is CVE-2026-10520 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2026-10520 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2026-10520

Description

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2026-10520 being exploited in your environment?