Vulnerabilities
Patch Ivanti's EPM and CSA flaws before anyone uses them
Ivanti's November 2026 advisories fix a 9.8 unauthenticated SQL injection in Endpoint Manager and a 9.4 missing-auth flaw in CSA, before any attacks.
Ivanti released its November 2026 security advisories on November 10, fixing around 13 vulnerabilities across five products. Two are the ones to read first, because both sit on the management servers that push software and policy to every machine in a fleet. CVE-2026-121653, scored 9.8 on the Common Vulnerability Scoring System (CVSS), is an unauthenticated SQL injection in Ivanti Endpoint Manager (EPM) that leads to remote code execution. CVE-2026-121683, scored 9.4, is a missing-authentication flaw in the Ivanti Cloud Services Application (CSA). A CVE is a Common Vulnerabilities and Exposures identifier, the shared reference number for a specific flaw.
What makes this one worth a note is the timing. Ivanti's threat intelligence reports no known exploitation in the wild at disclosure, and neither flaw is on the United States Known Exploited Vulnerabilities (KEV) catalog. That is the good part. The awkward part is that a public proof-of-concept already exists for the EPM flaw, and the products involved are exactly the kind an attacker wants. This is a patch-before-exploitation window, and those close quickly on software this valuable to an intruder.
How it works
SQL injection (SQLi) happens when a program builds a database query by pasting attacker-supplied text straight into it, instead of keeping the data and the query separate. The input then stops being treated as a value and starts being treated as part of the command. In CVE-2026-121653 the injectable input reaches the Core server of Endpoint Manager with no login required, so an attacker who can reach the server over the network can run their own database commands. On a Microsoft SQL Server back end those commands can be turned into operating-system commands, which is how a database bug becomes remote code execution (RCE): the ability to run arbitrary code on the server. The fix is in EPM 2024 Service Update 8 (SU8); earlier builds are affected.
CVE-2026-121683 in CSA is a different shape of problem. A privileged function that should check who is calling it does not check at all, which is the class of bug catalogued as missing authentication. In this case a remote unauthenticated attacker can add and delete the trusted certificate entries that CSA holds for EPM Core. Control over which certificates a system trusts is control over which other systems it will talk to, so this is a foothold into the trust between the two components, not just a nuisance. Ivanti's advisory lists CSA 5.0.8 as affected and reports the fix in build 5.0.8.1; confirm the exact build against the advisory, since version strings on these pages change.
Management planes are the prize here. EPM and CSA do not hold one application's data; they hold the keys to every endpoint they manage. A server that can install software on thousands of machines is a faster route to a whole estate than any single workstation, which is why an unauthenticated path to code execution on one of them rates 9.8.
Why the urgency, with no attacks yet
The honest answer is that "no exploitation seen" describes today, not next week. Three things shorten the gap. The EPM flaw needs no credentials, so there is no login step to slow an attacker down. A working proof-of-concept is already public, which removes most of the research an attacker would otherwise do. And EPM and CSA are often reachable from more of the network than their owners think, because they are built to be reached by the endpoints they manage.
Exposure is not uniform, though. Ivanti reports that CVE-2026-121683 is not externally exploitable in CSA Dual NIC (network interface card) deployments, where the vulnerable function sits on the internal interface rather than the one facing the internet. A NIC is a network port; a Dual NIC setup splits internal and external traffic across two of them. If your CSA is internet-facing on a single interface, treat it as exposed and move it to the top of the list. If it is Dual NIC with the affected function internal, you have more room, but the flaw is still there and still worth patching.
Ivanti also shipped a fix for Ivanti Sentry in this batch. CVE-2026-105425 is an operating-system command injection that allows remote code execution, scored 7.2 and rated high, and it affects Ivanti Endpoint Manager Mobile (EPMM) as well. Unlike the EPM and CSA flaws it needs administrator privileges, so it is a smaller risk on its own, but it is one more reason to run this update across the Ivanti footprint rather than cherry-picking.
What to do
Patch in the order of what an unauthenticated attacker can reach from outside.
- Internet-facing Endpoint Manager Core servers go first. Install EPM 2024 SU8 to close CVE-2026-121653. If a Core server answers on the public internet, there is no safe waiting window.
- Cloud Services Application next. Update to the fixed build, reported as 5.0.8.1, to close CVE-2026-121683. If your CSA is single-interface and internet-facing, this is as urgent as the EPM Core. If it is Dual NIC with the affected function internal, patch it on your normal critical track.
- Ivanti Sentry and EPMM. Move Sentry to 10.7.4, 10.8.3 or 11.0.0, and EPMM to 12.10.0.1, 12.9.0.3 or 12.8.0.5, to close CVE-2026-105425 and the rest of the batch.
Check exposure before and after. From outside your network, confirm whether the EPM Core web service and the CSA answer at all; the list of what is actually reachable rarely matches the asset inventory. There is no vendor report of exploitation, so Ivanti has not published indicators of compromise for these flaws. Until SU8 is in place, watch the EPM Core database and web logs for unusual queries or errors against the injectable endpoints, and watch CSA for certificate entries being added or removed that no administrator made. A new or missing trusted EPM Core certificate on CSA is the clearest sign the missing-auth function was touched.
If you cannot patch an internet-facing EPM Core today, restrict network access to it so only your management subnets can reach the Core web service, and treat that as a stopgap measured in days, not a fix.
Citrix published XenServer fixes in the same early-November window, in bulletin CTX697256, covering several defects across XenServer 8.4 and 9 with no reported attacks on customers. Reports disagree on the exact count and the overall severity rating, so check the Citrix bulletin for the specifics that apply to your version rather than relying on a summary. If you run XenServer, fold it into the same patch pass.
The pattern across both vendors is the same one that keeps catching teams: the fix is out, nobody is being hit yet, and the window to patch quietly is open. Management servers earn a faster track than ordinary software precisely because an unauthenticated flaw on one reaches everything it manages. Agree that track now, while this round is still a drill and not an incident.
Finding the EPM Core or CSA that is reachable from the internet when it should not be is the kind of gap we look for in attack surface management and in a network penetration test. Open the chat and Yaali, our AI agent, will pass your question to the engineer who would do the work.
Sources: SecurityWeek on Ivanti EPM fixes, CVE-2026-121653 detail, CVE-2026-121683 detail, CVE-2026-105425 detail, Ivanti November 2026 advisories summary, Citrix XenServer bulletin CTX697256, CISA Known Exploited Vulnerabilities catalog.