Ivanti EPM's 9.8 flaw: patch the server that patches everything

By DataForge team17 November 20265 min read

Ivanti fixed a CVSS 9.8 remote code flaw in Endpoint Manager on 10 November. Here's what NZ IT teams running EPM should check this week.

What Ivanti released

Ivanti published its monthly security update on 10 November 2026. Ivanti releases on the second Tuesday of each month, which put the advisories in New Zealand inboxes on Wednesday 11 November. SecurityWeek counted 13 vulnerabilities across five products: Endpoint Manager (EPM), Endpoint Manager Mobile, Sentry, Cloud Services Application (CSA) and User Workspace Manager.

The most serious fix is for CVE-2026-121653, an SQL injection flaw in the EPM Core server. The CVE record, as shown on OpenCVE, describes a remote attacker with no credentials getting code execution on the Core. The flaw scores 9.8 under CVSS 3.1 and affects every EPM release before 2024 SU8. GBHackers' breakdown of the advisories shows that SU8 also fixes CVE-2026-18128, a medium-severity flaw (CVSS 6.8). That second flaw sends sensitive agent information in cleartext, so an attacker sitting on the network path could read and change agent traffic.

The second critical flaw is CVE-2026-121683 (CVSS 9.4) in CSA, the gateway that lets EPM manage devices outside the corporate network. An unauthenticated attacker could add or delete trusted EPM Core certificate entries. Only CSA 5.0.8 is affected, and 5.0.8.1 fixes the problem, according to SecurityOnline's summary. SecurityWeek reports that CSA deployments using a dual NIC configuration can't be exploited from outside the network.

Ivanti says it has "no evidence of these vulnerabilities being exploited in the wild." OpenCVE's listing, last refreshed on 15 November, shows the EPM flaw isn't in CISA's Known Exploited Vulnerabilities catalogue. The same listing gives an EPSS score of about 2% and rates the flaw "automatable" with "total" technical impact. Low current exploitation and easy automation is a combination that can change quickly once someone publishes a working exploit.

Why an endpoint manager flaw belongs in your ITSM queue

Most security bulletins describe a single vulnerable system. An EPM Core is the system that pushes software, patches and scripts to every Windows device it manages. If an attacker controls the Core, the organisation's own deployment tool becomes the attacker's way of reaching every laptop and server on the estate. That's why we'd treat CVE-2026-121653 as an emergency change with a named owner and a deadline. Leaving it in next month's patch cycle invites the problem the tool exists to prevent.

Ivanti products also have a track record that should shape how quickly you move. In March 2024, NCSC New Zealand and CERT NZ joined CISA and agencies from Australia, the UK and Canada in warning of active exploitation of Ivanti Connect Secure and Policy Secure gateways. Those gateways are different products from EPM. Still, the 2024 advisory showed attackers persistently targeting Ivanti flaws and told organisations to assume a capable attacker could stay dormant inside a compromised network. A business that waited then paid for the delay with incident response and forensic work.

Version drift is the other problem. EPM 2022 is a separate release branch from EPM 2024, and SU8 is a 2024 update. The lifecycle tracker endoflife.ai lists EPM 2022 as end of life since 31 October 2025, with no security fixes after that date. A New Zealand business still running EPM 2022 can't simply apply SU8. Its team has to plan a version upgrade before the November fix can go on, and the upgrade is a larger change that needs testing time.

What NZ businesses should take from the release

In our experience, mid-sized NZ organisations often install an endpoint manager once and then leave the Core server alone. An MSP or a contractor sets the server up, the console works, and nobody tracks the version. When a critical advisory lands, the first hour goes on finding out who has admin access and which build is running. Good change and configuration practice saves that hour. A configuration record for the EPM Core should show its version, its owner, whether its web services face the internet and which CSA appliance sits in front of it.

Ivanti's blog post also says it now uses large language models in its own security testing and expects that work to increase the number of disclosures. If Ivanti finds more flaws each month, monthly releases will get bigger. Teams that rate each Ivanti advisory by hand will fall behind unless they have a standing rule for vendor criticals on management infrastructure. Our ITIL 4 framework guidance covers how to set up an emergency change path that's fast and still leaves an audit trail.

MSP contracts deserve a look too. Many NZ firms get endpoint management as part of a managed service, and the contract may promise "patching" without saying whether that covers the provider's own tooling. If your MSP runs EPM on your behalf, ask for the Core version and the date SU8 went on, in writing.

Practical next steps

  • Confirm the version today. Check the EPM Core build. Anything at 2024 SU7 or earlier needs SU8. Raise the work as an emergency change with a named owner and a completion date this week.
  • Check CSA separately. If you run Cloud Services Application, confirm whether it's on 5.0.8. If it is, upgrade to 5.0.8.1 and check that the dual NIC configuration is in place.
  • Plan the EPM 2022 upgrade now. If the Core is still on EPM 2022, schedule the move to EPM 2024 as a project with testing. In the meantime, cut network access to the Core down to admin workstations and the subnets that need it.
  • Limit access to the Core. The Core server shouldn't be reachable from the internet. Review firewall rules so that only managed devices and admin networks can reach its services.
  • Review Core activity since 10 November. Look for new admin accounts, unexpected packages or scripts in the distribution queue, and unusual scheduled tasks. Exploitation hasn't been reported, but a check now is cheap.
  • Update the CMDB record. Record the Core and CSA versions, owners and exposure so the next advisory takes minutes to assess.
  • Ask your MSP directly. Get written confirmation of the patch date for any Ivanti tooling the provider manages for you.
  • Set a standing rule. Agree in advance that critical vendor fixes for management servers such as EPM, RMM tools and backup consoles go through the emergency change path automatically.

Ivanti hasn't published any exploitation indicators for these flaws, and it's unknown how soon a public exploit will appear. Patching the EPM Core is a small job if the version is current and the owner is known, so this week is the time to do it.

If you'd like help building that emergency change path or reviewing how your service desk handles vendor security advisories, our ITSM team can help.

Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.

Get my free assessment How we help
Get new articles by RSS