CVE-2026-92207

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

GHSA-wc4f-6wjm-cqwf ↗EUVD-2026-107405 ↗

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

description

MindsDB installations using the OpenBBtable functionality may permit code injection; the affected release range is not specified. An authenticated attacker with access to the vulnerable functionality could execute code with the MindsDB service account's privileges.

mitigation

Restrict MindsDB access and OpenBBtable use to trusted accounts, and apply least-privilege permissions to the service account. Isolate or disable OpenBBtable where feasible until an upstream 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
40m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 17:17Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-21 17:17Z
    ghsa: trigger signal, started the run
  2. 2026-10-21 17:17Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2361",
  "cve_id": "CVE-2026-92207",
  "display_id": "CVE-2026-92207",
  "ghsa_id": "GHSA-wc4f-6wjm-cqwf",
  "euvd_id": "EUVD-2026-107405",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authenticated code injection in MindsDB OpenBBtable",
  "summary": "MindsDB installations using the OpenBBtable functionality may permit code injection; the affected release range is not specified. An authenticated attacker with access to the vulnerable functionality could execute code with the MindsDB service account's privileges.",
  "mitigation": "Restrict MindsDB access and OpenBBtable use to trusted accounts, and apply least-privilege permissions to the service account. Isolate or disable OpenBBtable where feasible until an upstream fixed release is identified.",
  "vendor": "MindsDB",
  "product": "MindsDB",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "25.10.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "MindsDB",
      "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": 39.57260566666667,
  "t0_at": "2026-10-21T17:17:42.063000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T17:17:42.063000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T17:17:42.063000+00:00",
      "url": "https://github.com/advisories/GHSA-wc4f-6wjm-cqwf"
    }
  }
}

published 2026-10-21 21:19Z
last change 2026-10-21 22:34Z

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.