{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80348 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-80348 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-80348 is a high-severity missing authorization vulnerability in TarsCloud TarsWeb, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80348 and fix it if it is affected.\n\nWhat it is: CVE-2026-80348 is a high-severity missing authorization vulnerability in TarsCloud TarsWeb, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80348 in the wild and no public exploit code.\n\nAffected product: TarsCloud TarsWeb. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-80348/ (Markdown: https://insights.sbomify.com/CVE-2026-80348/index.md)","id":"CVE-2026-80348","markdown":"https://insights.sbomify.com/CVE-2026-80348/index.md","name":"CVE-2026-80348","record":{"aliases":["GHSA-h9c2-vjpc-cf5r"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"TarsWeb management console","requires_auth":"low_privilege","summary":"Authenticated users can deploy, download, or delete arbitrary application packages on any managed server due to missing authorization checks in TarsWeb.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"TarsWeb through 3.0.16 Missing Authorization on Patch Deploy, Download and Delete Endpoints","id":"CVE-2026-80348","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"TarsWeb through 3.0.14 Authentication Bypass via Spoofed X-Forwarded-For and uid Parameter","id":"CVE-2026-80349"},"packages":[],"prev":{"headline":"mcp-fetch through 1.6.3 Server-Side Request Forgery via Unstripped IPv6 Literal Brackets","id":"CVE-2026-80347"},"products":["TarsWeb"],"published":"2026-08-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-26","vendors":["TarsCloud"]},"summary":"Authenticated users can deploy, download, or delete arbitrary application packages on any managed server due to missing authorization checks in TarsWeb.","url":"https://insights.sbomify.com/CVE-2026-80348/"}