CVE-2026-77933

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

GHSA-rq79-8cw2-45h7 ↗EUVD-2026-104689 ↗

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.
eosphoros-ai DB-GPT <= 0.8.2
ETK-2026-2118Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 06h 41msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h32m
0
+2h
+6h
+8h
+10h
+12h

description

DB-GPT through version 0.8.2 ships a default Docker Compose configuration with a static MySQL root credential. An attacker who can reach the MySQL service over the exposed port or shared container network can obtain administrative database access.

mitigation

Replace the default MySQL root password with a unique secret and restrict MySQL access to trusted hosts or an isolated private network. Do not publish the database port externally unless it is required and protected.

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.
0.35%27th percentile
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-20 00:46Z
Δ 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-20 00:46Z
    ghsa: trigger signal, started the run
  2. 2026-10-20 00:46Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2118",
  "cve_id": "CVE-2026-77933",
  "display_id": "CVE-2026-77933",
  "ghsa_id": "GHSA-rq79-8cw2-45h7",
  "euvd_id": "EUVD-2026-104689",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Hardcoded database credentials in DB-GPT Docker Compose",
  "summary": "DB-GPT through version 0.8.2 ships a default Docker Compose configuration with a static MySQL root credential. An attacker who can reach the MySQL service over the exposed port or shared container network can obtain administrative database access.",
  "mitigation": "Replace the default MySQL root password with a unique secret and restrict MySQL access to trusted hosts or an isolated private network. Do not publish the database port externally unless it is required and protected.",
  "vendor": "eosphoros-ai",
  "product": "DB-GPT",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 0.8.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "DB-GPT",
      "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.0035,
  "epss_percentile": 0.2709,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.790118133333333,
  "t0_at": "2026-10-20T00:46:12.076000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-20T00:46:12.076000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-20T00:46:12.076000+00:00",
      "url": "https://github.com/advisories/GHSA-rq79-8cw2-45h7"
    }
  }
}

published 2026-10-20 04:04Z
last change 2026-10-21 04:45Z

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.