CVE-2026-80348

HighCVSS 8.8

Published: 26/08/2026(UTC)Updated: 23/09/2026(UTC)Translated: 31/08/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.52%

43th percentile - higher than 43% of all known CVEs

Summary

TarsWeb fails to enforce access control in four methods of PatchController, allowing any authenticated user to upload packages, trigger deployments on any server, retrieve/delete other applications' packages, and change the default package.

Risk Assessment

Unauthorized access to package management functions can lead to application integrity compromise, data leakage, or unauthorized changes to deployment configurations.

Recommendation

Update TarsWeb to a version that adds proper authorization checks in uploadAndPublish, downloadPackage, deletePatchPackage, and setPatchPackageDefault. Restrict access to accounts with least privilege.

Other vulnerabilities in TarsWeb

CVE-2026-80349Critical
TarsWeb trusts a client-controlled X-Forwarded-For header, allowing an attacker to impersonate a local caller. By forging a loopback address and providing a uid of an existing account, an attacker can access the console as any user, including administrator, without credentials. Version 3.0.16 fixes this.

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS