CVE-2026-92189

waiting for further signalsZero needs more public information before it can validate it.
no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Quest Foglight for Databases 8.2.0
CWE-73 External Control of File Name or Path
ETK-2026-3421Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 28msince last run
37mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h04m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Quest Foglight for Databases is affected by improper handling of attacker-controlled file paths in a topology-writing function. An unauthenticated remote attacker who can reach the affected service may execute code with SYSTEM-level privileges.

mitigation

Restrict network access to Foglight for Databases to trusted administrative networks and block untrusted clients at network boundaries. Monitor for and apply a vendor-provided update when Quest publishes a fixed release.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
37m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 23:51Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-03 23:51Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-92189

{
  "etk_id": "ETK-2026-3421",
  "cve_id": "CVE-2026-92189",
  "display_id": "CVE-2026-92189",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unvalidated file path handling in Quest Foglight for Databases",
  "summary": "Quest Foglight for Databases is affected by improper handling of attacker-controlled file paths in a topology-writing function. An unauthenticated remote attacker who can reach the affected service may execute code with SYSTEM-level privileges.",
  "mitigation": "Restrict network access to Foglight for Databases to trusted administrative networks and block untrusted clients at network boundaries. Monitor for and apply a vendor-provided update when Quest publishes a fixed release.",
  "vendor": "Quest",
  "product": "Foglight for Databases",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "8.2.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Foglight for Databases",
      "purl": null
    }
  ],
  "cwes": [
    73
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 37.17080551666667,
  "t0_at": "2026-11-03T23:51:27.372000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T23:51:27.372000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T23:51:27.372000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-92189"
    }
  }
}

published 2026-11-04 00:18Z
last change 2026-11-04 01:23Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.