CVE-2026-111692

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

GHSA-8xhf-8q7j-9q7q ↗EUVD-2026-102983 ↗

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.
databufflabs databuff <= 0.1.10
ETK-2026-1809Zero's internal tracking ID, independent of the CVE number., permanent identifier
3d 17h 27msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+28h32m
0
+2h
+4h
+6h
+8h
+10h

description

DataBuff ai-apm-web through version 0.1.10 contains an embedded JWT signing key in its token service. An unauthenticated attacker able to reach the affected web endpoints could obtain administrator-level access to protected APIs, including query functionality.

mitigation

Immediately restrict access to the affected web and API routes to trusted networks and users, and revoke active administrative sessions where supported. No fixed release is recorded; deploy a vendor release that removes the embedded key when one is available.

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.
–
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.
0.61%48th percentile
agent run time
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 17:39Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-1809",
  "cve_id": "CVE-2026-111692",
  "display_id": "CVE-2026-111692",
  "ghsa_id": "GHSA-8xhf-8q7j-9q7q",
  "euvd_id": "EUVD-2026-102983",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Hardcoded JWT signing key in DataBuff ai-apm-web",
  "summary": "DataBuff ai-apm-web through version 0.1.10 contains an embedded JWT signing key in its token service. An unauthenticated attacker able to reach the affected web endpoints could obtain administrator-level access to protected APIs, including query functionality.",
  "mitigation": "Immediately restrict access to the affected web and API routes to trusted networks and users, and revoke active administrative sessions where supported. No fixed release is recorded; deploy a vendor release that removes the embedded key when one is available.",
  "vendor": "databufflabs",
  "product": "databuff",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 0.1.10"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "databuff",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0061,
  "epss_percentile": 0.4808,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 35.794937366666666,
  "t0_at": "2026-10-16T17:39:48.239000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T17:39:48.239000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T17:39:48.239000+00:00",
      "url": "https://github.com/advisories/GHSA-8xhf-8q7j-9q7q"
    }
  }
}

published 2026-10-16 20:56Z
last change 2026-10-21 05:31Z

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.