# CVE-2026-74849: Remote code execution vulnerability

> Attackers can execute arbitrary code remotely via the GINA client in ManageEngine ADSelfService Plus.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-vwcx-qwxm-ffwg

## What is CVE-2026-74849?

CVE-2026-74849 is a critical command injection vulnerability in Zohocorp ManageEngine ADSelfService Plus, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zohocorp ManageEngine ADSelfService Plus versions before build 7001 are vulnerable to a remote code execution vulnerability in the GINA client.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-74849 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74849 is a critical command injection vulnerability in Zohocorp ManageEngine ADSelfService Plus, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74849 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-74849/ (Markdown: https://insights.sbomify.com/CVE-2026-74849/index.md)
```

## Sources

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

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