CVE-2026-80348

Received Received - Intake

Unauthorized Package Deployment in TarsWeb

Publication date: 2026-08-26

Last updated on: 2026-09-03

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-26

Last Modified

2026-09-03

Generated

2026-09-15

AI Q&A

2026-08-26

EPSS Evaluated

2026-09-14

NVD

CVE-2026-80348

EUVD

EUVD-2026-66387

Affected Vendors & Products

Vendor	Product	Version / Range
tarscloud	tarsweb	3.0.16
tarscloud	tarsweb	to 3.0.16 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-862	The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

Executive Summary

CVE-2026-80348 is a missing authorization vulnerability in TarsWeb through version 3.0.16. Four methods in PatchController.js (uploadAndPublish, downloadPackage, deletePatchPackage, setPatchPackageDefault) fail to enforce role-based access controls. This allows any authenticated user, even with limited permissions, to perform unauthorized actions like uploading and deploying packages to any server, downloading or deleting packages from other applications, and changing default deployment packages.

Detection Guidance

Check if TarsWeb version 3.0.16 or earlier is installed by examining package managers or file versions. Inspect PatchController.js for missing AuthService calls in uploadAndPublish, downloadPackage, deletePatchPackage, and setPatchPackageDefault methods. Monitor network traffic for unauthorized patch deployment or package downloads.

Impact Analysis

An attacker could exploit this to push malicious code to production servers, disrupt services by deleting critical packages, or steal sensitive application data by downloading packages. Even low-privilege users can perform high-impact operations like triggering deployments across all managed servers in the Tars installation.

Compliance Impact

This vulnerability could lead to violations of GDPR (data exposure), HIPAA (unauthorized access to health data), or other regulations by enabling unauthorized access to sensitive data, disruption of services, or tampering with critical application packages. Compliance failures may result from breaches of confidentiality, integrity, or availability requirements.

Mitigation Strategies

Upgrade TarsWeb to the latest version beyond 3.0.16. Implement strict role-based access controls and ensure all patch-related endpoints enforce authorization checks. Restrict network access to TarsWeb management interfaces and audit logs for suspicious activities.

Hi! I’m here to help you understand CVE-2026-80348. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70