CVE-2026-80348

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

Published Aug 26, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

TarsWeb lacks proper authorization checks in key patch‑management endpoints: upload-and-apply, download, delete, and setting the default package. As a result, any authenticated user, even one with a role scoped to an unrelated application, can upload a patch, trigger its deployment on any server managed by the console, retrieve or delete other applications’ packages, and change which patch a given application deploys by default. This lack of access control allows attackers to execute arbitrary code on target servers, delete critical data, and disrupt application operation, constituting a severe privilege escalation flaw.

Affected Systems

This vulnerability affects all installations of TarsWeb up to and including version 3.0.16. The issue exists in the application’s PatchController module for TarsCloud’s TarsWeb product.

Risk and Exploitability

With a CVSS score of 8.7 the flaw is considered high severity. The EPSS score is unavailable, but the vulnerability is listed as not in the CISA KEV catalog. The attack likely proceeds from an authenticated user session on the web console; explicit attack vectors are not documented, but inference indicates that any authenticated user can exploit the missing authorizations. The propagation can affect all servers managed by the TarsWeb instance, making the risk landscape broad for deployments using this product.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor patch or upgrade to TarsWeb version 3.0.17 or later to enforce authorization checks on all patch endpoints.
  • Reconfigure role‑based access control so that only users with explicit patch‑management roles can access upload, download, delete, and set‑default endpoints.
  • Enable detailed audit logging for all patch‑management actions and regularly review logs for anomalous activity.

Generated by OpenCVE AI on August 26, 2026 at 11:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Tarscloud
Tarscloud tarsweb
Vendors & Products Tarscloud
Tarscloud tarsweb
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title TarsWeb through 3.0.16 Missing Authorization on Patch Deploy, Download and Delete Endpoints
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 26, 2026, 4:10 PM
Reserved
Aug 26, 2026, 9:56 AM
Status
Deferred
Published
Aug 26, 2026, 10:16 AM
Modified
Sep 23, 2026, 5:17 PM