ETK-2026-3245Zero's internal tracking ID, independent of the CVE number.

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

GHSA-cr7m-37cv-h5p8 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
other:TablePro for macOS <= 0.83.0; 0.84.0-beta.1
fixed in 0.83.1, 0.84.0-beta.2
CWE-436 Interpretation Conflict
ETK-2026-3245Zero's internal tracking ID, independent of the CVE number., no cve assigned
cvss7.0ethiack provisional
3h 42msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −17h50mwaiting for further signals−3h42m
−12h
−6h
0

description

TablePro for macOS may apply request restrictions differently than certain database drivers, permitting database operations beyond intended read-only or confirmation controls. Exposure requires an enabled MCP server and a paired, authorized external client, or use through the assistant; the database account's privileges limit what can be changed.

mitigation

Upgrade macOS to 0.83.1, 0.84.0-beta.2 or later.

fixed in 0.83.1, 0.84.0-beta.2

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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-01 07:16Z

this entry in the feed

GET /api/v1/feed/ETK-2026-3245

{
  "etk_id": "ETK-2026-3245",
  "cve_id": null,
  "display_id": "ETK-2026-3245",
  "ghsa_id": "GHSA-cr7m-37cv-h5p8",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Database request validation bypass in TablePro for macOS",
  "summary": "TablePro for macOS may apply request restrictions differently than certain database drivers, permitting database operations beyond intended read-only or confirmation controls. Exposure requires an enabled MCP server and a paired, authorized external client, or use through the assistant; the database account's privileges limit what can be changed.",
  "mitigation": "Upgrade macOS to 0.83.1, 0.84.0-beta.2 or later.",
  "vendor": "other",
  "product": "other:TablePro for macOS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 0.83.0",
        "0.84.0-beta.1"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "0.83.1",
        "0.84.0-beta.2"
      ],
      "package_name": "TablePro for macOS",
      "purl": null
    }
  ],
  "cwes": [
    436
  ],
  "cvss_score": 7,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.217487483333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-01T07:16:34+00:00",
      "days": -0.743160603900463,
      "is_lower_bound": true,
      "measured_at": "2026-11-02T01:06:43.139234+00:00",
      "url": "https://github.com/TableProApp/TablePro/security/advisories/GHSA-cr7m-37cv-h5p8"
    }
  }
}

published 2026-11-01 21:10Z
last change 2026-11-02 00:53Z

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.