CriticalCVE-2026-10520

    Ivanti Sentry OS Command Injection Vulnerability (CVE-2026-10520)

    Published Last modified In CISA KEV since Sources: pwn.watch, CVE.org, SingCERT, Ivanti, CERT-EU

    What is affected, what to do

    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

    The vulnerability is being actively exploited; treat it as a priority. Update Sentry to version 10.5.2, Sentry to version 10.6.2. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Sentry lt *..10.5.2
    • Sentry lt 10.6.0..10.6.2
    • Sentry eq 10.7.0..10.7.0
    Fixed in
    • Sentry 10.5.2
    • Sentry 10.6.2

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    10.0

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    10.0

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: pwn.watch, CVE.org, SingCERT, Ivanti, CERT-EU

    99.91 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.97

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    248.61 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab), CIRCL KEV How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    10.0 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    10.0
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    99.91 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.97
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 12 June 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-78

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This CVE is on KEV because it delivers unauthenticated, network-reachable, root-level RCE on an appliance that by design sits at the boundary between the internet and the internal mobile and identity stack. The CVSS vector describes the full worst case (network, no auth, no user interaction, scope change, total CIA impact), and the exploitation likelihood is among the highest observed anywhere. Typical targets are organisations running externally exposed Sentry instances in the unmanaged state; attackers routinely use MDM appliances as a pivot into the mobile fleet, AD credentials, and VPN configurations. Score your exposure strictly by "is the vulnerable port reachable from the internet?" — if yes, treat as P1 with immediate isolation; if only internal and mTLS-protected, still P2 with a patch SLA under 72 hours.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Patch now: upgrade Ivanti Sentry to R10.5.2, R10.6.2, or R10.7.1 per the Ivanti security advisory, including the required appliance reboot. All standalone Sentry builds up to and including 10.7.0 are affected.
      • Pull the appliance off the public internet: restrict the MICS admin portal (TCP/8443) and Sentry service ports (typically TCP/443, 9090) at the perimeter firewall or reverse proxy to known admin source IPs. Do not accept internet exposure until the patch is verified.
      • Compensating configuration: return Sentry to a managed state with EPMM over mTLS, or lock down access via Neurons for MDM — CISA explicitly calls these configurations non-exploitable.
      • Compromise assessment before patching: inspect /var/log/tomcat2/, /var/log/mifs/, and root/tomcat shell history for command-injection traces before rebooting. On any indication, take a forensic image, rebuild clean, and do not restore configuration from an unknown-trust backup.
      • Rotate secrets: EPMM shared secrets, API tokens, certificates, and any AD service accounts stored on the Sentry appliance should be treated as exfiltrated and replaced.
      • Open an incident ticket referencing CVE-2026-10520 and evaluate NIS2 reporting obligations — internet-reachable unauthenticated RCE infrastructure typically crosses the significant-incident threshold.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: place the Sentry appliance in a dedicated management VLAN; permit inbound only from EPMM/MDM peers over mTLS; default-deny egress with an allowlist for Ivanti update endpoints and NTP.
      • Reverse proxy / WAF in front: block requests containing shell metacharacters (;, |, `, $(, %0a) in query strings and headers, especially targeting /mics/ and /sentry/ paths. Load vendor or ET Open Snort/Suricata signatures for CVE-2026-10520 and enable them in blocking mode.
      • Admin interface hardening: expose the MICS admin portal (8443) only via VPN or bastion; enforce MFA at the jump host and keep session timeouts short.
      • Egress control: block outbound connections from Sentry to non-Ivanti destinations (pastebins, Tor, generic VPS ranges) at the firewall — RCE payloads routinely stage second-stage tooling.
      • Least privilege for integrations: trim the AD accounts Sentry uses to the minimum required rights; never domain admin.
      • Immutable offline configuration backup taken before patching, so rollback does not reinstate a compromised state.

    3. Runbook step 3

      Detection rules

      • Process ancestry on the appliance: tomcat/java spawning /bin/sh, /bin/bash, curl, wget, python, perl, or nc is a strong indicator. Sigma shape: parent_image endswith 'java' AND image in ('/bin/sh','/bin/bash','/usr/bin/curl','/usr/bin/wget').
      • Access-log patterns: HTTP requests to /mics/* or Sentry endpoints containing URL-encoded shell metacharacters (%3B, %7C, %60, %24%28) or unusually long query strings. KQL shape: WebLogs | where url_path startswith "/mics/" and (url_query matches regex "%3[bB]|%7[cC]|%60|%24%28").
      • Auditd on the appliance: execve events with arguments whoami, id, uname -a, cat /etc/shadow, chmod +x /tmp/* from UID tomcat/mifs. Alert whenever the Tomcat user launches binaries outside its baseline path.
      • Network telemetry (Zeek): new outbound connections from the Sentry IP to external hosts on ports 4444, 1337, 8080, 9001 or to known C2 infrastructure; DNS lookups against OAST services (interact.sh, oast.pro, burpcollaborator).
      • Filesystem integrity: new executable files under /tmp, /dev/shm, /var/tmp; modifications to authorized_keys, crontab, /etc/passwd. Run an EDR or osquery scheduled check against a known-good hash baseline.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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

    Source: pwn.watch, NVD (NIST), CISA KEV Catalog, CVE.org (MITRE), CSA/SingCERT, cvelistv5, ivanti_bulletin, certeu_advisory

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    ivantiSentry
    • —
    • —
    ivantistandalone_sentry
    • 10.6.0 – < 10.6.2
    • < 10.5.2
    • 10.7.0
    • 10.6.2
    • 10.5.2
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

      Base

      The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

      Entry at MITRE CWE-78

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    CIRCL KEVvulnerability.circl.lu (opens in a new tab)actively exploited
    GitHubwatchtowrlabs/watchTowr-vs-Ivanti-Sentry-RCE-CVE-2026-10520-CVE-2026-10523 (opens in a new tab)github.comPoC (publicly reported)reported, not verified—
    PoC-in-GitHub (nomi-sec)CVE-2026-10520-POC (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)patch-CVE-2026-10520 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-10520 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-10520 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-10520-10523 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-10520 (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    • hub.ivanti.comIvanti Sentry — CVE-2026-10520pwn-watch
    • github.comwatchtowrlabs/watchTowr-vs-Ivanti-Sentry-RCE-CVE-2026-10520-CVE…Exploit
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-10520government-resource
    • pwn.watchpwn.watch: Ivanti Sentry: Ivanti Sentry OS Command Injection Vulnerabilitypwn-watch
    • NVD (NIST)NVD: CVE-2026-10520pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modified3c1d8aa1…

      Show 3 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://hub.ivanti.com/s/article/Security-Advisory-Ivanti-Sentry-CVE-2026-10520-CVE-2026-10523?language=en_US
      Referenceremoved
      https://hub.ivanti.com/s/article/Security-Advisory-Ivanti-Sentry-CVE-2026-10520-CVE-2026-10523?language=en_US
      —
      Reference typeremoved
      https://hub.ivanti.com/s/article/Security-Advisory-Ivanti-Sentry-CVE-2026-10520-CVE-2026-10523?language=en_US Types: Patch, Vendor Advisory
      —

      Source identifier: 3c1d8aa1-5a33-4ea4-8992-aadd6440af75

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: yes

      Show 8 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://github.com/watchtowrlabs/watchTowr-vs-Ivanti-Sentry-RCE-CVE-2026-10520-CVE-2026-10523
      Referenceadded
      —
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-10520
      Referenceremoved
      https://github.com/watchtowrlabs/watchTowr-vs-Ivanti-Sentry-RCE-CVE-2026-10520-CVE-2026-10523
      —
      Referenceremoved
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-10520
      —
      Reference typeremoved
      https://github.com/watchtowrlabs/watchTowr-vs-Ivanti-Sentry-RCE-CVE-2026-10520-CVE-2026-10523 Types: Third Party Advisory
      —
      Reference typeremoved
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-10520 Types: US Government Resource
      —
      SSVC assessmentremoved
      {"id":"CVE-2026-10520","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-06-09T00:00:00+00:00"}
      —
      SSVC assessmentadded
      —
      {"id":"CVE-2026-10520","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-06-12T03:55:17.049044Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. Initial analysis by NVDNVD

      Newly listed as affected:
      • Ivanti Sentry (before 10.5.2; 10.6.0 – before 10.6.2; 1 individual version)
      Show 4 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Product configurationadded
      —
      OR *cpe:2.3:a:ivanti:standalone_sentry:*:*:*:*:*:*:*:* versions up to (excluding) 10.5.2 *cpe:2.3:a:ivanti:standalone_sentry:*:*:*:*:*:*:*:* versions from (including) 10.6.0 up to (excluding) 10.6.2 *cpe:2.3:a:ivanti:standalone_sentry:10.7.0:*:*:*:*:*:*:*
      Reference typeadded
      —
      CISA-ADP: https://github.com/watchtowrlabs/watchTowr-vs-Ivanti-Sentry-RCE-CVE-2026-10520-CVE-2026-10523 Types: Third Party Advisory
      Reference typeadded
      —
      ivanti: https://hub.ivanti.com/s/article/Security-Advisory-Ivanti-Sentry-CVE-2026-10520-CVE-2026-10523?language=en_US Types: Patch, Vendor Advisory
      Reference typeadded
      —
      CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-10520 Types: US Government Resource

      Source identifier: nvd@nist.gov

    One NVD translation into another language is hidden.

    Linked advisories

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-10520
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-10520"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-10520.svg?lang=en" alt="CVE-2026-10520 – NEOSEC Intel" height="20"></a>