# CVE-2026-2740: Remote Code Execution

> Authenticated attackers can execute arbitrary code on agent machines via a vulnerable third-party dependency in ManageEngine products.

- **Severity:** High 8.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2026
- **Updated:** 22 May 2026
- **Also known as:** GHSA-hrrx-gqw9-2hrq

## What is CVE-2026-2740?

CVE-2026-2740 is a high-severity command injection vulnerability in Zohocorp ManageEngine ADSelfService Plus, published on 21 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Zohocorp ManageEngine ADSelfService Plus version before 6525, DataSecurity Plus before 6264 and RecoveryManager Plus before 6313 are vulnerable to Authenticated Remote code execution in the agent machines due to the bug in the 3rd party dependency.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-2740 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2740 is a high-severity command injection vulnerability in Zohocorp ManageEngine ADSelfService Plus, published on 21 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2740 in the wild and no public exploit code.

Affected product: Zohocorp ManageEngine ADSelfService Plus. 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-2740/ (Markdown: https://insights.sbomify.com/CVE-2026-2740/index.md)
```

## Sources

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

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