# CVE-2026-121653: SQL injection in the Core of Ivanti Endpoint Manager before version 2024 SU8 allows a remote unauthenticated attacker to achieve remote code execution.


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-7fr5-xp8p-8vqx

## What is CVE-2026-121653?

CVE-2026-121653 is a critical vulnerability in ivanti Endpoint Manager, published on 10 Nov 2026. 

### Official description

SQL injection in the Core of Ivanti Endpoint Manager before version 2024 SU8 allows a remote unauthenticated attacker to achieve remote code execution.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-121653?


## How do I fix CVE-2026-121653?

No fix has been published for CVE-2026-121653 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121653 being exploited?

There is no known exploitation of CVE-2026-121653 in the wild and no public exploit code.

Public exploit code:

- Containerised PoC for CVE-2026-121653: unauthenticated SQL injection (CWE-89) in the Ivanti Endpoint Manager Core status-event service leads to RCE through the Core database account. A model of /WSStatusEvents runs on real Microsoft SQL Server; the differential, the three mitigations and an 0day sweep are captured. (github_poc): https://github.com/googlesky/CVE-2026-121653

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121653 and fix it if it is affected.

What it is: CVE-2026-121653 is a critical vulnerability in ivanti Endpoint Manager, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121653 in the wild and no public exploit code.

Affected product: ivanti Endpoint Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121653/ (Markdown: https://insights.sbomify.com/CVE-2026-121653/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121653
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121653
- OSV: https://osv.dev/vulnerability/CVE-2026-121653

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121653/
Summaries are generated and may contain mistakes; the official description above is the record.