CVE-2026-92190

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

GHSA-3xxj-hwx3-jcvq ↗EUVD-2026-116630 ↗

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-3425Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 47msince 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+25h37m
0
+2h
+4h
+6h
+8h
+10h

description

Quest Foglight for Databases installations using the affected baseRmiServiceExporter configuration are vulnerable to unsafe deserialization. A remote attacker who can reach the exposed service can execute code as SYSTEM without authenticating.

mitigation

Restrict network access to the affected service to trusted administrators and isolate it from untrusted networks; disable the affected service if it is not required. Obtain and apply a vendor update when one is provided, as no fixed version is recorded.

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
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 23:50Z
Δ 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:50Z
    ghsa: trigger signal, started the run
  2. 2026-11-03 23:50Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3425",
  "cve_id": "CVE-2026-92190",
  "display_id": "CVE-2026-92190",
  "ghsa_id": "GHSA-3xxj-hwx3-jcvq",
  "euvd_id": "EUVD-2026-116630",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated deserialization in Foglight for Databases",
  "summary": "Quest Foglight for Databases installations using the affected baseRmiServiceExporter configuration are vulnerable to unsafe deserialization. A remote attacker who can reach the exposed service can execute code as SYSTEM without authenticating.",
  "mitigation": "Restrict network access to the affected service to trusted administrators and isolate it from untrusted networks; disable the affected service if it is not required. Obtain and apply a vendor update when one is provided, as no fixed version is recorded.",
  "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": 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": 13.795221,
  "t0_at": "2026-11-03T23:50:48.578000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T23:50:48.578000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T23:50:48.578000+00:00",
      "url": "https://github.com/advisories/GHSA-3xxj-hwx3-jcvq"
    }
  }
}

published 2026-11-04 00:55Z
last change 2026-11-05 05:05Z

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.