CVE-2026-80348
TarsWeb enforces its per-application roles by calling AuthService …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/TarsCloud/TarsWeb
- github.com/TarsCloud/TarsWeb/blob/v3.0.16/app/controller/patch/PatchController.js
- github.com/TarsCloud/TarsWeb/issues/213
- www.vulncheck.com/advisories/tarsweb-through-3.0.16-missing-authorization-on-patch-deploy-
- nvd.nist.gov/vuln/detail/CVE-2026-80348
- cve.org/CVERecord?id=CVE-2026-80348
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.