CYBERSECURITYTRACKER
TRACKING7,457 stories in this site build1,583 vulnerability news stories in this site build
Vulnerabilities

CVE-2026-10520

Review this vulnerability's source-backed evidence, with unavailable values and read failures kept distinct.

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker data as of: .

Detection and validation

Mapped metadata availability only. These signals do not change priority.

  • Sigma

    Not mapped by tracked sources.

  • Atomic

    Not mapped by tracked sources.

  • Nuclei

    Ivanti Sentry - OS Command Injection. Check identifier: CVE-2026-10520.

    Open Nuclei metadata

  • Metasploit

    Not mapped by tracked sources.

What it is

Reported

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.

Source reported · Source: NVD · Source last published: · Source description excerpt; complete tracked detail loads below. · Source last updated: · Tracker data as of:

What is affected

Reported

Ivanti; Sentry. Product-level identification only; no affected-version conclusion is available from this field.

Source reported · Source: NVD · Source last published: · Source last updated: · Tracker data as of:

Urgency and basis

Reported

Act · 470.4

Tracker computed · Tracker decision tier from the evidence detailed below · Source last updated: · Tracker data as of:

Exploitation evidence

Reported

Active exploitation · CISA KEV · VulnCheck KEV · ENISA exploited-vulnerability catalog

Source reported · Active since: · CISA KEV added: · VulnCheck KEV added: · ENISA added: · Source last updated: · Tracker data as of:

What to do

Reported

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.

Source remediation ↗

Source reported · Tracked source remediation field · Source last updated: · Tracker data as of:

Evidence detail

Loading the full tracker evidence record…

Glossary

Open in glossary