CVE-2026-123018

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

GHSA-5h42-cm7h-7vh6 ↗EUVD-2026-117405 ↗

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.0; 0.8.1; 0.8.2
ETK-2026-3622Zero's internal tracking ID, independent of the CVE number., permanent identifier
9h 31msince last run
35mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h35m
0
+4h
+6h
+8h
+10h
+12h

description

DB-GPT through version 0.8.2 is affected by code injection in the CodeAction component's execute_code function. An unauthenticated remote attacker may be able to run code when they can reach the affected CodeAction functionality.

mitigation

Restrict network access to CodeAction, disable it if it is not required, and run the service with least privilege. No fixed release is identified in the evidence; monitor for a vendor update and upgrade 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.
–
agent run time
35m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-05 11:45Z
Δ 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-11-05 11:45Z
    ghsa: trigger signal, started the run
  2. 2026-11-05 11:45Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3622",
  "cve_id": "CVE-2026-123018",
  "display_id": "CVE-2026-123018",
  "ghsa_id": "GHSA-5h42-cm7h-7vh6",
  "euvd_id": "EUVD-2026-117405",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Remote code injection in DB-GPT CodeAction",
  "summary": "DB-GPT through version 0.8.2 is affected by code injection in the CodeAction component's execute_code function. An unauthenticated remote attacker may be able to run code when they can reach the affected CodeAction functionality.",
  "mitigation": "Restrict network access to CodeAction, disable it if it is not required, and run the service with least privilege. No fixed release is identified in the evidence; monitor for a vendor update and upgrade when one is available.",
  "vendor": "eosphoros-ai",
  "product": "DB-GPT",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "0.8.0",
        "0.8.1",
        "0.8.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "DB-GPT",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 34.710407483333334,
  "t0_at": "2026-11-05T11:45:20.056000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T11:45:20.056000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T11:45:20.056000+00:00",
      "url": "https://github.com/advisories/GHSA-5h42-cm7h-7vh6"
    }
  }
}

published 2026-11-05 12:45Z
last change 2026-11-05 22:29Z

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.