Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Applications Manager installer
-
DeliveryExtract embedded GCP private key
-
ExploitAuthenticate to Google Cloud as service account
-
ExecutionAccess or modify associated cloud resources
-
ImpactCloud data theft or resource tampering
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
|
| Exploitation Conditions | No special runtime conditions on the target server - the private key is statically embedded in the Applications Manager installer for all versions 182200 and below, so any party who obtains that installer (a downloadable artifact) can extract the key without authenticating to the product. The practical prerequisite is possession of the installer and that the associated Google Cloud service account remains active with meaningful IAM permissions; exploitation then targets Google Cloud APIs directly, not the Applications Manager instance. The main limiting factor is the blast radius being bounded by whatever roles/permissions were granted to that specific service account. |
| Impact | This is a genuine top-priority issue, not a high-CVSS-but-low-real-risk case. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N, score 10.0) is internally consistent with the description: a Google Cloud service-account private key is embedded in the Applications Manager installer, making this effectively a shared/hardcoded secret (CWE-321) identical across all installations. Because anyone who obtains the widely-distributed installer can extract the key without authenticating, PR:N is justified, and the scope change (S:C) correctly reflects that impact lands on Google Cloud resources - a system separate from the vulnerable component. No EPSS score, no CISA KEV listing, and no public POC were provided, so despite the maximal CVSS this is 'no public exploit identified at time of analysis' rather than confirmed active exploitation - the score reflects potential severity, not observed weaponization. One caveat: A:N is arguably understated, since the description explicitly says an attacker can 'modify associated cloud resources,' which could include deletion (availability loss). Advisory is vendor-self-reported (Zoho), so exploitation-in-the-wild signals are absent, suggesting theoretical/targeted risk rather than mass exploitation today. |
| Exploit ScenarioDerived | An attacker downloads or otherwise obtains the ManageEngine Applications Manager installer (version 182200 or below), extracts the embedded Google Cloud service-account private key, and uses it to authenticate to Google Cloud APIs as that service account. With no further credentials required, they read or modify the cloud resources the service account can reach. No public proof-of-concept was identified, but the low attack complexity and unauthenticated nature make exploitation straightforward once the key is located. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
ManageEngine Applications Manager builds 182200 and below embed a static Google Cloud service-account private key inside the shipped installer, so anyone who downloads that installer artifact can extract the credential without authenticating to the product and then impersonate the service account directly against Google Cloud APIs. The vendor scores this CVSS 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) because the leaked key grants high confidentiality and integrity impact on associated cloud resources and the scope changes beyond the Applications Manager instance itself, with no authentication or user interaction required. Exploitation depends on the installer being obtainable and the referenced service account remaining active with meaningful IAM permissions; no public exploit code has been identified at time of analysis and there is no CISA KEV listing, but the credential is static rather than runtime-dependent, which makes the exposure durable rather than conditional.
RemediationAI
Patch available per vendor advisory: upgrade ManageEngine Applications Manager to a release later than build 182200 as documented at https://www.manageengine.com/products/applications_manager/security-updates/security-updates-cve-2026-86708.html; the supplied intelligence does not include an exact fix build number, so confirm the specific patched version on that page before upgrading. Upgrading alone is not sufficient remediation, because the private key is a leaked static credential and replacing the installer does not invalidate it - the Google Cloud service-account key must be revoked and rotated immediately, and any new key must be stored outside the product artifact in a managed secret store or workload identity federation rather than re-embedded. While the key remains valid, audit the service account's IAM bindings and remove any permissions beyond the minimum required, since the achievable impact is bounded solely by those roles, and review Google Cloud Audit Logs for suspicious token issuance or API calls from unexpected source addresses to determine whether the key was already used. If immediate rotation is not possible, the only durable compensating control is disabling or tightly scoping the service account, accepting that this breaks any Applications Manager functionality that depends on it until the upgrade, key rotation, and IAM review are complete.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-321, Use of Hard-coded Cryptographic Key: a Google Cloud service-account private key (the JSON key material used to sign OAuth 2.0 JWT bearer assertions for the service-account flow) was packaged as static content within the ManageEngine Applications Manager installer rather than being generated per-deployment or provisioned as a secret outside the artifact. Because the key is embedded in a distributable binary, anyone who obtains the installer for builds 182200 and below effectively holds a long-lived credential; there is no need to reach or exploit the Applications Manager server itself. The changed-scope (S:C) rating reflects that the resulting impact lands on Google Cloud resources governed by that service account's IAM bindings rather than on the ManageEngine host, so the practical blast radius is defined entirely by the roles and permissions granted to the specific service account. Affected software is captured by the CPE cpe:2.3:a:zohocorp:manageengine_applications_manager:*:*:*:*:*:*:*:*, with the version ceiling given as 182200 and below in the description. The PR:N and UI:N components of the assessed vector confirm the attack is unauthenticated against the product and requires no victim interaction; no KEV or POC signal is present in the supplied intelligence, so this should be treated as a serious latent credential-exposure defect rather than a confirmed exploited one.
Know when Manageengine Applications Manager gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Shared hardcoded key extractable from a distributed installer means PR:N/AC:L; impersonation reaches a separate cloud system (S:C) allowing read and modify (C:H/I:H); A:N per vendor, though deletion could arguably raise availability.
Primary rating from Vendor (Zohocorp).
CVSS VectorVendor: Zohocorp
Lifecycle Timeline
2DescriptionCVE.org
ZohoCorp ManageEngine Applications Manager versions 182200 and below were vulnerable to exposure of a Google Cloud service-account private key in the Applications Manager installer, which could allow an unauthenticated attacker to impersonate the service account and access or modify associated cloud resources.
Articles & Coverage 1
Executive ViewAI
ManageEngine Applications Manager builds 182200 and below ship with a static Google Cloud service-account private key embedded in the installer, allowing unauthenticated attackers who obtain the installer to impersonate that service account and access associated cloud resources. This vulnerability, rated CVSS 10.0, directly threatens the confidentiality and integrity of cloud data and services for affected organizations. Leadership should treat this as a high-priority risk requiring immediate credential rotation and access controls, despite no public exploit identified at time of analysis.
Revoke and rotate the exposed Google Cloud service-account key, restrict access to the installer artifact, apply least privilege to the service account, and monitor for unauthorized API calls.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
A remote code execution issue was discovered in Zoho ManageEngine Applications Manager before 13.6 (build 13640). Rated
Zoho ManageEngine Applications Manager 13 before build 13500 allows SQL injection via GraphicalView.do, as demonstrated
Zoho ManageEngine Applications Manager 12 through 14 allows FaultTemplateOptions.jsp resourceid SQL injection. Rated cri
An issue was discovered in Zoho ManageEngine Applications Manager 11.0 through 14.0. Rated critical severity (CVSS 9.8),
A SQL Injection vulnerability exists in the Zoho ManageEngine Applications Manager 13 before build 13820 via the resids
A SQL Injection vulnerability exists in Zoho ManageEngine Applications Manager 13.x before build 13800 via the j_usernam
Zoho ManageEngine Applications Manager 13 before build 13500 allows Post-authentication SQL injection via the name param
An issue was discovered in Zoho ManageEngine Application Manager through 14.2. Rated high severity (CVSS 8.8), this vuln
An issue was discovered in Zoho ManageEngine OpManager through 12.4x. Rated high severity (CVSS 8.8), this vulnerability
Zoho ManageEngine Applications Manager 13 before build 13530 allows SQL injection via the /MyPage.do widgetid parameter.
Zoho ManageEngine Applications Manager 13 before build 13530 allows SQL injection via the /showresource.do resourceid pa
Zoho ManageEngine Applications Manager 13 before build 13530 allows SQL injection via the /MyPage.do?method=viewDashBoar
EUVD-2026-85288
GHSA-pwgq-mrvp-r2v7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB