CVE-2026-92197

waiting for further signalsZero needs more public information before it can validate it.

GHSA-j4pm-v9cx-f945 ↗EUVD-2026-116639 ↗

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
ETK-2026-3436Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 38msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h48m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Quest Foglight for Databases contains a path traversal flaw in its unzipFile functionality; affected release versions are not specified in the available evidence. An authenticated attacker may use the flaw to cause code to run with SYSTEM-level privileges.

mitigation

Restrict Foglight access to trusted administrators and limit network exposure to the service. Apply a Quest-provided security update when a fixed release is identified.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
14m
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
    ghsa: trigger signal, started the run
  2. 2026-11-03 23:51Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3436",
  "cve_id": "CVE-2026-92197",
  "display_id": "CVE-2026-92197",
  "ghsa_id": "GHSA-j4pm-v9cx-f945",
  "euvd_id": "EUVD-2026-116639",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authenticated path traversal in Quest Foglight for Databases",
  "summary": "Quest Foglight for Databases contains a path traversal flaw in its unzipFile functionality; affected release versions are not specified in the available evidence. An authenticated attacker may use the flaw to cause code to run with SYSTEM-level privileges.",
  "mitigation": "Restrict Foglight access to trusted administrators and limit network exposure to the service. Apply a Quest-provided security update when a fixed release is identified.",
  "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": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.0/AV:N/AC:L/PR:L/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": 14.076274216666667,
  "t0_at": "2026-11-03T23:51:23.789000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T23:51:23.789000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T23:51:23.789000+00:00",
      "url": "https://github.com/advisories/GHSA-j4pm-v9cx-f945"
    }
  }
}

published 2026-11-04 02:24Z
last change 2026-11-04 06:57Z

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.