CVE-2026-80348

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-26. A secondary CVSS source baseline 8.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
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists TarsCloud TarsWeb versions up to and including 3.0.16 as affected. No release containing a fix is confirmed on record.

TarsWeb enforces its per-application roles by calling AuthService from individual controller methods, and four methods in app/controller/patch/PatchController.js make no such call. uploadAndPublish accepts a package upload and then builds and dispatches a deployment task to every server matching the supplied application and module name, while its sibling uploadPatchPackage, which only stores the package, does check developer authorization first. The only precondition uploadAndPublish enforces is that the named server is registered, and any registered server in the installation satisfies it. downloadPackage and deletePatchPackage select a package by an unscoped sequential primary key covering every application's uploads, and setPatchPackageDefault changes which package a given application deploys by default. Any authenticated account, including one holding a role scoped to a single unrelated application, can therefore push a package to and trigger its deployment on any server the console manages, retrieve or delete any other application's package, and change which package is deployed by default.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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 26, 2026

Last Modified

September 23, 2026

Advisory Details (4)

Auto-updated Aug 26, 2026
No fix on record yet.
Web page

TarsWeb through 3.0.16 Missing Authorization on Patch Deploy, Download and Delete Endpoints | Advisories | VulnCheck

https://www.vulncheck.com/advisories/tarsweb-through-3.0.16-missing-authorization-on-patch-deploy-download-and-delete-endpoints
Web page

TarsWeb/app/controller/patch/PatchController.js at v3.0.16 · TarsCloud/TarsWeb · GitHub

https://github.com/TarsCloud/TarsWeb/blob/v3.0.16/app/controller/patch/PatchController.js
Web page

Missing authorization on tars-web patch/deploy endpoints allows any authenticated user to deploy and read arbitrary packages for applications they have no permission on · Issue #213 · TarsCloud/TarsWeb · GitHub

https://github.com/TarsCloud/TarsWeb/issues/213
Web page

GitHub - TarsCloud/TarsWeb: TARS Projects Dashboard · GitHub

https://github.com/TarsCloud/TarsWeb

Vendor Advisories for CVE-2026-80348(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 19× in last 7d / 110× 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 187 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 87 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-80348?
CVE-2026-80348 is a high-severity vulnerability; its CVE record was published on August 26, 2026. TarsWeb enforces its per-application roles by calling AuthService from individual controller methods, and four methods in app/controller/patch/PatchController.js make no such call. uploadAndPublish accepts a package upload and then builds and dispatches a deployment task to every server matching…
When was CVE-2026-80348 made public?
CVE-2026-80348 was made public on August 26, 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 26, 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-80348 actively exploited?
CVE-2026-80348 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80348?
CVE-2026-80348 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80348?
No fix for CVE-2026-80348 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists TarsCloud TarsWeb versions up to and including 3.0.16 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-80348 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-80348?

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