How severe is CVE-2021-44077?

CVE-2021-44077 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-44077?

Affected package information for CVE-2021-44077 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2021-44077?

No fixed release is recorded for CVE-2021-44077 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2021-44077 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2021-44077 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2021-44077 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2021-44077, including 5 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-44077?

CVE-2021-44077 has an EPSS (Exploit Prediction Scoring System) score of 93.3%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2021-44077 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2021-44077 (Zoho ManageEngine ServiceDesk Plus Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-12-01. CISA required all US federal civilian agencies to remediate this vulnerability by 2021-12-15. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2021-44077?

CVE-2021-44077 is classified as Missing Authentication (CWE-306). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2021-44077?

A Nuclei detection template exists for CVE-2021-44077, meaning automated scanners can fingerprint it. A Metasploit module references CVE-2021-44077, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2021-44077 published, and has it been updated?

CVE-2021-44077 was published on November 29, 2021 and was last updated on October 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

CVE-2021-44077

CRITICAL

CVE-2021-44077 is a critical-severity (CVSS 9.8) Missing Authentication vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2021-12-01) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Zoho ManageEngine ServiceDesk Plus before 11306, ServiceDesk Plus MSP before 10530, and SupportCenter Plus before 11014 are vulnerable to unauthenticated remote code execution. This…

Published

Nov 29, 2021

Updated

Oct 21, 2025

Affected

3 products

Patched

See advisory

Exploits

6 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2021-12-01. Federal agencies were required to remediate by 2021-12-15.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2021-44077.

EPSS Exploitation Probability

via FIRST.org ↗

93.3%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-44077 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

Zoho ManageEngine ServiceDesk Plus before 11306, ServiceDesk Plus MSP before 10530, and SupportCenter Plus before 11014 are vulnerable to unauthenticated remote code execution. This is related to /RestAPI URLs in a servlet, and ImportTechnicians in the Struts configuration.

Affected Products

3 products · 73 configurations

Application

manageengine servicedesk pluszohocorp

< 11.1

3 versions

11.111.211.3

Application

manageengine servicedesk plus mspzohocorp

< 10.5

1 version

10.5

Application

manageengine supportcenter pluszohocorp

< 11.0

1 version

11.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.