CVE-2026-80104

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-25. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

DB-GPT builds the destination path for an uploaded skill from the multipart filename without constraining it to the upload directory. skill_upload in packages/dbgpt-app/src/dbgpt_app/openapi/api_v1/agentic_data_api.py takes file.filename as given and writes the request body to upload_dir / filename. A path composed with that operator discards the left operand when the right one is absolute and follows parent references otherwise, so a filename such as ../../../tmp/x or /tmp/x resolves outside the intended directory; nothing canonicalises the result, checks that it remains under the upload root, or prevents a .py suffix. The route's only dependency is get_user_from_headers in dbgpt_serve/utils/auth.py, which returns a request carrying the admin role whether or not a user_id header is supplied, so the endpoint is reachable without credentials. A remote attacker holding no account can therefore write attacker-controlled bytes to any path the server process can write, place a new Python module inside the application package or replace one the application already imports, and obtain code execution in the server process when that module is next imported.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation1.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
64th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 25, 2026

Last Modified

September 23, 2026

Advisory Details (5)

Auto-updated Oct 8, 2026
Patch available. Sources: github_release.
Web page

DB-GPT 0.8.0 Path Traversal Arbitrary File Write via Skill Upload Filename | Advisories | VulnCheck

https://www.vulncheck.com/advisories/db-gpt-0.8.0-path-traversal-arbitrary-file-write-via-skill-upload-filename
Web page

Client Challenge

https://pypi.org/project/dbgpt-app/
GitHub release Patch Available

v0.8.1

Patch available: eosphoros-ai/DB-GPT v0.8.1

https://github.com/eosphoros-ai/DB-GPT/releases/tag/v0.8.1
Web page

DB-GPT/packages/dbgpt-app/src/dbgpt_app/openapi/api_v1/agentic_data_api.py at v0.8.0 · eosphoros-ai/DB-GPT · GitHub

https://github.com/eosphoros-ai/DB-GPT/blob/v0.8.0/packages/dbgpt-app/src/dbgpt_app/openapi/api_v1/agentic_data_api.py
Web page

GitHub - eosphoros-ai/DB-GPT: open-source agentic AI data assistant for the next generation of AI + Data products. · GitHub

https://github.com/eosphoros-ai/DB-GPT

Vendor Advisories for CVE-2026-80104(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 26× in last 7d / 188× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 346 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 246 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 01:37 UTCEG score recompute
  2. 2026-10-14 01:37 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-13 16:35 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  4. 2026-10-12 21:47 UTCEG score recompute
  5. 2026-10-12 21:47 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-12 16:35 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  7. 2026-10-12 14:57 UTCEG score recompute
  8. 2026-10-12 05:23 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-11 19:21 UTCEG score recompute
  10. 2026-10-11 16:37 UTCEG score recompute
  11. 2026-10-11 13:56 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  14. 2026-10-10 15:18 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-10 11:11 UTCEG score recompute
  16. 2026-10-10 11:11 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  18. 2026-10-09 07:53 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-09 03:42 UTCEG score recompute
  20. 2026-10-09 03:42 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  22. 2026-10-08 10:08 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-08 06:11 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-08 02:17 UTCEG score recompute
  25. 2026-10-08 02:17 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  2. 2026-10-07 08:58 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-07 05:03 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-07 01:09 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-06 20:45 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-06 16:02 UTCEG score recompute
  7. 2026-10-06 16:01 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  9. 2026-10-06 11:55 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-06 07:39 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-06 01:52 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-05 20:52 UTCEG score recompute
  13. 2026-10-05 20:52 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  15. 2026-10-05 16:58 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-05 11:35 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-05 07:40 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-05 03:46 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-04 23:39 UTCEG score recompute
  20. 2026-10-04 23:39 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  22. 2026-10-04 19:45 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-04 13:52 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-04 09:58 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-04 06:02 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-04 02:08 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-03 20:13 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-03 16:17 UTCEG score recompute
  29. 2026-10-03 16:17 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  31. 2026-10-03 04:29 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-03 00:34 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-02 18:53 UTCEG score recompute
  34. 2026-10-02 18:53 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-02 17:57 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  36. 2026-10-02 14:48 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-02 10:20 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-02 06:25 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-02 01:16 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-01 19:59 UTCEG score recompute
  41. 2026-10-01 19:59 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  43. 2026-10-01 13:22 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-01 09:28 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-01 05:34 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-01 01:06 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-09-30 20:09 UTCEG score recompute
  48. 2026-09-30 20:09 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-09-30 15:04 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  50. 2026-09-30 11:37 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-09-30 06:23 UTCEG score recompute
  52. 2026-09-30 06:23 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-09-29 12:40 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-09-29 05:24 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-09-29 01:31 UTCEG score recompute
  56. 2026-09-29 01:31 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-09-28 21:24 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-09-28 13:54 UTCEG score recompute
  59. 2026-09-28 13:54 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-09-28 13:52 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  61. 2026-09-28 10:00 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-09-28 06:06 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-09-28 02:12 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-09-27 22:18 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-09-27 18:24 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-09-27 14:30 UTCEG score recompute
  67. 2026-09-27 14:30 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  69. 2026-09-27 10:03 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-09-27 06:09 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-09-27 02:15 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-26 21:38 UTCEG score recompute
  73. 2026-09-26 21:38 UTCGHSA enrichmentGHSA-x75h-xjfp-qrh8 · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  75. 2026-09-26 00:28 UTCEPSS rescoreEPSS 1.1% · 64th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-80104?
CVE-2026-80104 is a critical-severity vulnerability; its CVE record was published on August 25, 2026. DB-GPT builds the destination path for an uploaded skill from the multipart filename without constraining it to the upload directory. skillupload in packages/dbgpt-app/src/dbgptapp/openapi/apiv1/agenticdataapi.py takes file.filename as given and writes the request body to uploaddir / filename. A…
When was CVE-2026-80104 made public?
CVE-2026-80104 was made public on August 25, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 25, 2026. EchelonGraph's copy of the record carries a last-modified date of September 23, 2026; the record at its source may have been updated since.
Is CVE-2026-80104 actively exploited?
CVE-2026-80104 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80104?
CVE-2026-80104 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80104?
A fix for CVE-2026-80104 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80104 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-80104

Explore →

Is Your Infrastructure Affected by CVE-2026-80104?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs