Skip to content
major vulnerability· requires attention

ManageEngine Applications Manager is widely used in IT operations; a high-severity privilege escalation affecting many deployments merits broad attention.

Applications

CVE-2026-86683

8.1
High
EPSS n/aPatch availableSep 25, 2026

Low-privileged user can change proxy settings in ManageEngine Applications Manager

common questions

Is CVE-2026-86683 being exploited?

Not confirmed. CVE-2026-86683 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-86683?

CVE-2026-86683 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-86683?

Yes. A fix has been recorded for CVE-2026-86683. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-86683 affect?

CVE-2026-86683 affects ManageEngine Applications Manager ≤ 182000, On-premises Applications Manager deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-86683?

Install vendor update, restrict low-priv accounts, and audit proxy configurations.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
ManageEngine Applications Manager ≤ 182000On-premises Applications Manager deployments
impact

Low-privileged user can modify proxy settings, enabling traffic interception, exfiltration, monitoring bypass or lateral movement.

action required

Patch when possible

affected versions
Zohocorp ManageEngine Applications Manager
  • affected< 182100

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free