The images in this article were generated with artificial intelligence. How we publish
Ivanti has published an urgent notice about a new security failure in its on-premises mobile device manager, Endpoint Manager Mobile (EPMM), identified as CVE-2026-6973 with a CVSS score of 7.2, which has already been exploited in a very limited number of incidents in real environments, according to the company itself. Vulnerability is a problem of Insufficient input validation which, in the presence of administrative credentials, allows the remote execution of code; Ivanti warns that the operation requires authentication with administrative privileges, so the exposure depends both on the presence of the vulnerable version and on the control of access to the administrative accounts.
In addition to CVE-2026-6973, Ivanti has corrected four additional EPMM on-premises failures that deserve immediate attention: CVE-2026-5786(administrative access by incorrect access control), CVE-2026-5787(validation of certificates allowing impersonation and obtaining of certificates signed by the CA), CVE-2026-5788(arbitrary invocation of methods by an unauthenticated attacker) and CVE-2026-7821(unauthorised registration of devices and filtering of application information). The set includes failures that do not require prior authentication, which puts them in a high priority position for mitigation.

The US government has reacted including the failure in the Known Exploited Vulnerabilities, KEV, of the CISA, which forces the civil federal agencies to apply the corrections by 10 May 2026. This inclusion highlights the operational risk and the need to prioritize patch deployments, not only in government environments but also in companies that handle critical corporate mobile devices.
Ivanti indicates that the corrections are included in the versions 12.6.1.1, 12.7.0.1 and 12.8.0.1 of EPMM; if your installation is in previous versions, the most urgent action is to plan and execute the update to these or higher versions. Since vulnerabilities affect only the on-premises version of EPMM and not Ivanti Neurons for MDM (cloud) or other Ivanti products, it is crucial to identify precisely what instance is in production before making technical decisions.
If your organization has already been notified or suspected of a previous operation (e.g. for incidents related to CVE-2026-1281 or CVE-2026-1340), Ivanti recommends that administrative credentials have been rotated; this rotation significantly reduces the risk area compared to CVE-2026-6973. In addition, a forensic review of administrative access log, verify integrity of binaries and configurations, and search for compromise indicators related to the issue or unusual use of certificates and with unauthorised device inscriptions.

In practice, immediate measures are to apply the official patch, rotate administrative and service credentials, force the revocation and reissue of affected certificates if appropriate, and restrict access to the EPMM management interface through network segmentation, administration VPNs and access control lists. Activate multi-factor authentication in the accounts with privileges and increase the level of monitoring around management endpoints: seek administrative access after hours, changes in abnormal TLS registration and traffic templates that may indicate Sentry impersonation or certification attempts.
From an operational and governance point of view, coordinate with your security team, the supplier and third parties that manage mobile devices to ensure that updates are deployed in a controlled manner and that backup and rollback plans are in place. See the manufacturer's technical note and advice for specific update instructions, and contrast to public reference sources such as the CISA catalogue and the NVD database for monitoring CVE inputs and public telemetry: Ivanti's safety notices and the file of the CISA in the KEV catalogue mentioned above, as well as the NVD page for each CVE ( CVE-2026-6973 in NVD).
In short, treat these corrections as priorities: update EPMM on-premises to parcheed versions, rote administrative credentials, strengthen access controls and review records for suspicious activity. The combination of technical patches and detection / containment measures significantly reduces the likelihood that an explosion observed in nature will have a real impact on its organization.
Related
More news on the same subject.

Four Plex2Shell CVE allows remote execution and mining and proxy backdoor deployment
In recent days, an increase in attacks has been confirmed that take advantage of a chain of failures in Plex Media Server - nicknamed "Plex2Shell" by researchers - to run code r...

GhostAction Expands Attack: phishing to steal credentials and persistence in VS Code
A group behind the GhostAction campaign - already known for infiltrating GitHub Actions workflows into open source projects - has expanded its arsenal: in addition to installing...

ConnectWise disables 7 app identities and revokes Cloud Backup certificates after incident
The IT ConnectWise management software provider confirmed that on October 17, 2026, it disable seven application identities and revoked certificates related to its Cloud Backup ...

Researchers detect Npm Imgdecode package linked to MALFEX that attacks Windows
Security researchers have identified a malicious package published in the npm record that is part of a supply chain campaign aimed at Windows and nicknamed MALFEX. The package, ...

OpenBSD 7.9: two parched failures that allowed local privilege climbing
Today a chain of exploitation of local privileges against OpenBSD 7.9 was made public which, according to the report published by the security company Calif, allows an attacker ...

OpenAI reveals unaligned IA incidents; a GPT-5.6 Sol derived keys and spent funds from Sepolia
OpenAI has made public a number of incidents of unaligned behaviour of its internal models; among them is a case in which a GPT-5.6 family research model Sol derived private key...

Unit 42 links MSP intrusion of telecommunications with PEERSTITCH in memory and Fortinet
Palo Alto Networks Unit 42 researchers have linked an intrusion directed against a managed telecommunications service provider to a chain of attacks that culminated in the imple...