Foglight for Databases CVE-2026-92199
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged code execution on host
-
DeliveryLocate EncryptionUtil hard-coded key
-
ExploitAbuse symmetricDecrypt with recovered key
-
ExecutionExecute arbitrary code as SYSTEM
-
ImpactFull host compromise
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 | Exploitation requires that the attacker can already run low-privileged code on the system hosting Quest Foglight for Databases (per CVSS PR:L and the advisory's explicit statement that the attacker 'must first obtain the ability to execute low-privileged code on the target system'). The specific weakness is a hard-coded cryptographic key used by the EncryptionUtil component's symmetricDecrypt method, so the condition is the presence of that fixed key in the shipped product rather than any opt-in feature or non-default setting. Limiting factors: the attack vector is local only (no network exploitation), it is authenticated to the extent that an existing low-privilege foothold is needed, and it affects installations of this specific Quest product; no remote or unauthenticated path is described in the available sources. |
| Impact | This is a credible but conditional priority, not an internet-facing emergency. The CVSS 3.0 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) describes a locally-exploitable flaw that requires the attacker to already hold low-privileged code execution on the host, so it is a post-compromise privilege-escalation primitive rather than an initial-access vulnerability. The impact ceiling is severe - full confidentiality, integrity and availability impact via arbitrary code execution as SYSTEM - which makes it a valuable second-stage step for an attacker who already has a foothold. No EPSS score, no CISA KEV listing, and no SSVC machine triage were supplied in the input, so widespread or automatable exploitation cannot be asserted; the only decision signal present is the vuln.today priority 'this_week', which indicates prompt but not emergency remediation. The sole reference is the ZDI advisory (ZDI-26-863), a coordinated-disclosure write-up reported by Trend Micro ZDI, not a published working exploit. Net: the low-complexity, no-interaction local escalation to SYSTEM warrants timely patching on any host running this product, but the local-only attack vector and the authenticated prerequisite bound the real-world risk below that of a remote unauthenticated flaw. |
| Exploit ScenarioDerived | An attacker who has already obtained a low-privileged account or code-execution foothold on a server running Quest Foglight for Databases extracts the hard-coded cryptographic key embedded in the EncryptionUtil component and uses it against the symmetricDecrypt method to recover or forge protected data, escalating to arbitrary code execution in the SYSTEM context. Exploitation is local only and low-complexity (AV:L/AC:L) with no user interaction required. No public exploit code was identified in the provided data; the only reference is the ZDI advisory. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 04, 2026
Local privilege escalation in Quest Foglight for Databases lets an attacker who already holds low-privileged code execution on the host escalate to SYSTEM by abusing a hard-coded cryptographic key in the EncryptionUtil symmetricDecrypt routine. The attack is local-only and requires an existing authenticated foothold (CVSS PR:L), and no public exploit code or CISA KEV entry was identified at time of analysis. With a CVSS base score of 7.8 and high confidentiality, integrity, and availability impact, the flaw is best treated as a post-compromise escalation path on Foglight hosts rather than an internet-facing emergency.
RemediationAI
No fixed version is listed in the supplied intelligence; consult ZDI-26-863 for vendor patch status, and treat a vendor update as the only complete fix because a hard-coded key cannot be rotated through configuration alone. Until a patched build is confirmed, reduce exposure by tightening the prerequisite the exploit depends on: restrict who can execute code or log on interactively to Foglight for Databases hosts, and consider running Foglight services under a least-privileged service account rather than SYSTEM, accepting that some functionality may require elevated rights. Monitor Foglight hosts for unexpected child processes or credential-decryption activity originating from the service, since the flaw is only reachable after a low-privileged foothold has already been obtained.
Affected ProductsAI
Quest Foglight for Databases installations are affected; the supplied intelligence does not specify a version range or CPE identifier, so the exact affected builds are not confirmed from the available data. The primary reference is the ZDI advisory ZDI-26-863 at https://www.zerodayinitiative.com/advisories/ZDI-26-863/, which should be consulted to map the flaw to specific Foglight for Databases releases.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The weakness is CWE-321, Use of a Hard-coded Cryptographic Key, in the EncryptionUtil component's symmetricDecrypt method. Because the symmetric key is embedded in the shipped product rather than generated per installation or stored in a protected keystore, every deployment carries the same static secret, and anyone who can read the relevant binary or configuration can recover it and decrypt data protected by that routine. The supplied CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) describes a local, low-complexity attack that requires low privileges and no user interaction, with scope unchanged and high impact across confidentiality, integrity, and availability; the trigger beyond the hard-coded key itself is not described in the available sources. The advisory is ZDI-CAN-29967, published as ZDI-26-863, and the assessed vector matches the vendor-disclosure vector.
Know when the next one hits your stack
- 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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Advisory requires a pre-existing low-privilege local foothold (AV:L, PR:L) with no user interaction, and the hard-coded key yields reliable SYSTEM code execution (AC:L, C/I/A:H).
Primary rating from Vendor (trendmicro).
CVSS VectorVendor: trendmicro
DescriptionCVE.org
Quest Foglight for Databases EncryptionUtil Hardcoded Encyption Key Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Quest Foglight for Databases. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.
The specific flaw exists within the symmetricDecrypt method. The issue results from the use of a hard-coded cryptographic key. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-29967.
Executive ViewAI
A high-severity local privilege escalation flaw in Quest Foglight for Databases allows anyone who already has a low-privileged foothold on a monitoring host to elevate to SYSTEM-level control, exposing the confidentiality, integrity, and availability of data and systems managed through the platform. The exposure is not remotely exploitable and no public exploit exists at time of analysis, so leadership should treat it as a post-compromise risk multiplier that raises the stakes on endpoint hygiene and detection around any existing host intrusion. Organizations relying on Foglight to monitor sensitive databases should prioritize hardening and containment of the monitoring tier while a vendor fix is pending.
No vendor-released patch identified at time of analysis. Limit local code execution and administrative access on Foglight hosts, enforce least privilege for service and user accounts, deploy application allowlisting and EDR behavioral monitoring for privilege escalation, segment monitoring infrastructure from sensitive database networks, and maintain enhanced logging and alerting for suspicious local activity until a patch is available.
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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
NVD
CVE.org
GitHub PoC
Exploit-DB