Vulnerability

Quest Foglight for Databases Missing Authentication Remote Code Execution (CVE-2026-92188)

A critical missing authentication flaw in the ForgeMBeanServerSupport module of Quest Foglight for Databases.

CVE ID
CVE-2026-92188
CVSS
9.8 Critical (CVSS v3.0, ZDI as CNA; no CVSS 3.1 or 4.0 score in the record or NVD)
Affected product
Quest Foglight for Databases 8.2.0
Exploited
Unknown
Published
3 November 2026 (ZDI-26-854 and CVE record); NVD entry 4 November 2026

In short

CVE-2026-92188 is a critical missing authentication flaw in the ForgeMBeanServerSupport module of Quest Foglight for Databases. The Zero Day Initiative (ZDI) says a remote attacker needs no login to run code as SYSTEM. The CVE record lists version 8.2.0 as affected, and ZDI says the fix is in Foglight 8.3.

Profile MapVulnerability
  1. CVECVE-2026-92188
  2. ProductQuest Quest Foglight for Databases 8.2.0
  3. Fix Steps4actions listedUpgrade to Foglight 8.3 · List Who Can Connect

What it allows

ZDI says the flaw lets remote attackers execute arbitrary code on affected Quest Foglight for Databases installations, and that authentication is not required. ZDI, which is also the CVE numbering authority, rates it CVSS 3.0 9.8 Critical. The advisory is ZDI-26-854, tracked before release as ZDI-CAN-29168.

What the Missing Check Means

The record says the flaw exists within the ForgeMBeanServerSupport module and "results from the lack of authentication prior to allowing access to functionality." In plain terms, a function that should ask who is calling does not ask. An attacker has no password to guess and no session to steal.

That makes network reach the whole question. If a host can connect to the vulnerable service, the record says it can run code in the context of SYSTEM, the most privileged local account on a Windows machine.

What the Record Leaves Open

Neither the CVE record nor the ZDI advisory names a port, a protocol or a setting that turns the module on. They do not describe the steps of an attack or say what the attacker sends. The advisory also does not state the operating system, so the Windows meaning of SYSTEM is our reading.

Until Quest or ZDI says more, we treat every Foglight 8.2.0 server as reachable and ask who can connect to it. The answer, not a guess about the module, drives the order of work.

Signals for CVE-2026-92188

These are the public signals we checked on 4 November 2026. Each row names its source.

Exploit signals
  • CISA KEVNot seenNot listed in catalog version 2026.11.034 Nov
  • Brandefense BlackholeYesTwo Telegram feed posts on 3 and 4 November, one relaying advisory ZDI-26-854 and one a daily critical CVE digest4 Nov
Verdict Not in CISA KEV as of catalog version 2026.11.03

Both Blackhole posts repeat the advisory text and add no new detail. Two sibling flaws in the same product were disclosed the same day: the file path flaw CVE-2026-92189 and the deserialization flaw CVE-2026-92190. Each has its own ZDI advisory, and our remote code execution glossary entry covers the wider class.

Who is affected

The CVE record lists one product and one version. It sets the default status of all other versions to unknown, so it neither clears nor condemns them.

ZDI writes "Fixed in Foglight 8.3" under Additional Details of advisory ZDI-26-854. The fix line is the same on the advisories for CVE-2026-92189 and CVE-2026-92190. We have not seen a separate hotfix named in the record.

Because only 8.2.0 is listed, we treat earlier 8.x builds as unverified, not as safe. Our vulnerability management guide describes how to inventory versions and plan a rollout.

Timeline

  1. 30 Apr 2026

    ZDI reports the vulnerability to the vendor, according to the ZDI disclosure timeline.

  2. 15 Sep 2026

    The CVE identifier is reserved.

  3. 3 Nov 2026

    ZDI publishes advisory ZDI-26-854 in coordinated release, and the CVE record is published.

  4. 4 Nov 2026

    The entry appears in NVD with the ZDI score and no NVD analysis yet.

What to do

  1. Upgrade to Foglight 8.3

    ZDI says the issue is fixed in Foglight 8.3. Plan the upgrade of every Foglight for Databases server listed as 8.2.0, and check the vendor's upgrade notes before you start.

  2. List Who Can Connect

    Because no login is needed, start with reach. We recommend listing every host and network that can connect to each Foglight server and removing paths that have no reason to exist.

  3. Limit Access to Management Hosts

    Until the upgrade is done, we recommend allowing connections to the server only from the administration hosts that need them.

  4. Review the Server Host

    Check the Foglight host for new accounts, services and scheduled tasks. Code runs as SYSTEM per ZDI, so we recommend treating any unexplained change as a possible compromise.

Questions

Does CVE-2026-92188 need a login?

No. ZDI says authentication is not required, because the module allows access to functionality without first checking who is calling.

Which Foglight version fixes CVE-2026-92188?

ZDI says Foglight 8.3. The CVE record lists 8.2.0 as affected and does not name other versions.

Is CVE-2026-92188 exploited?

It is not listed in the CISA Known Exploited Vulnerabilities catalog as of catalog version 2026.11.03.

Is this the same bug as the other two Foglight CVEs?

No. ZDI published three separate advisories for different modules: ForgeMBeanServerSupport, writeTopologySectionToFile and baseRmiServiceExporter.

In our research

  1. Network segmentation Glossary term

Sources

  1. CVE-2026-92188 Record CVE Program / ZDI CNA
  2. CVE-2026-92188 NVD
  3. ZDI-26-854 advisory Zero Day Initiative
  4. Known Exploited Vulnerabilities Catalog CISA