/

CVE-2026-80348

Severity:

HIGH RISK

(8.8)

Missing Authorization (CWE-862) in TarsWeb Patch API

CVE-2026-80348

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Cross-Application Deployment, Data Exposure, and Integrity Loss

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

TarsWeb contains missing authorization checks in several patch-management controller methods. An authenticated account, including one limited to an unrelated application, may upload and deploy packages to managed servers, access or delete other applications' packages, and change an application's default deployment package.

Affected context

The issue occurs in TarsWeb's patch-management API when controller methods rely on application-scoped roles but omit calls to the authorization service. The affected operations include package upload and deployment, package download and deletion, and selection of the default package. Risk is present when an authenticated user can reach these endpoints and the console manages registered application servers.

Exploit preconditions

  • Attack surface: Authenticated TarsWeb patch-management endpoints
  • Required access: Any authenticated account; an application-specific role may be sufficient
  • Trigger point: Invoking an affected upload, deployment, package retrieval, deletion, or default-selection operation
  • Why exploitation is possible: Several controller methods do not enforce application-scoped authorization, and some package lookups use an identifier spanning all applications rather than an application boundary

Why this happens

The vulnerability is caused by inconsistent authorization enforcement across controller methods. Sensitive operations call the authorization service individually, but the affected methods proceed after only basic checks such as confirming that a server is registered. This maps to CWE-862: Missing Authorization, because the application fails to verify whether the authenticated principal is permitted to perform the requested action on the target application, server, or package. Global sequential identifiers and insufficient resource scoping further allow objects belonging to other applications to be selected.

Potential impact

  • An authenticated user may deploy an unauthorized package to managed servers
  • An attacker could alter application behavior or introduce malicious application code
  • Other applications' packages may be disclosed or deleted
  • The package selected for an application's default deployment may be changed
  • Service availability and deployment integrity could be disrupted
  • The scope of compromise may extend across applications and managed servers

General mitigation guidance

Mitigation generally focuses on enforcing authorization consistently at every sensitive controller operation and binding each resource lookup to the authorized application context.

Common defensive patterns include:

  • Applying centralized, deny-by-default authorization checks before upload, deployment, download, deletion, and default-selection actions
  • Deriving resource scope from the authenticated principal rather than trusting caller-supplied application or module values
  • Using tenant- or application-scoped identifiers and queries for package access
  • Separating permission checks for package management from permission to deploy to servers
  • Enforcing least privilege for accounts, service identities, and managed servers
  • Requiring explicit approval or policy evaluation for cross-application deployment operations

How teams detect issues like this

Organizations can look for missing authorization through:

  • Static analysis rules identifying controller methods that access or mutate resources without an authorization-service call
  • Code review checks requiring every state-changing or data-access endpoint to establish object ownership and application scope
  • Integration tests that repeat each operation with users authorized for another application, unauthorized applications, and no relevant role
  • Runtime policy enforcement and audit logging for package uploads, deployments, downloads, deletions, and default-package changes
  • Queries for authenticated users performing operations outside their assigned application scope

Automated application-security testing and policy-aware code review tools may help identify inconsistent authorization paths.

Sources

SourceLink
github.comgithub.com/TarsCloud/TarsWeb
github.comgithub.com/TarsCloud/TarsWeb/blob/v3.0.16/app/controller/patch/PatchController.js
github.comgithub.com/TarsCloud/TarsWeb/issues/213
vulncheck.comvulncheck.com/advisories/tarsweb-through-3.0.16-missing-authorization-on-patch-deploy-download-and-delete-endpoints

Frequently asked

questions

Any authenticated account may be able to exploit the affected operations, including an account whose role is limited to an unrelated application.

No direct server login is necessarily required. The key requirement is authenticated access to the vulnerable TarsWeb patch-management endpoints and the presence of a registered target server.

Enforce centralized, deny-by-default authorization at every affected operation, and ensure package and server lookups are scoped to the caller's authorized application context.

Treat authorization as a mandatory endpoint contract, test every resource operation across application boundaries, use least privilege, and audit cross-application deployment activity.

Find out what's already
exploitable in your codebase.