Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-80349 – Authentication Bypass / Admin Impersonation – TarsCloud TarsWeb ≤ 3.0.14

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-80349 is a critical authentication bypass vulnerability (CWE-290: Authentication Bypass by Spoofing) affecting TarsCloud TarsWeb, the web-based management dashboard for the TARS microservices platform. The flaw allows an unauthenticated remote attacker to spoof a trusted-proxy header and impersonate any existing account — including administrators — granting full control over the management console. The issue carries a Critical severity rating (CVSS 9.3) and affects all versions of TarsWeb up to and including 3.0.14.

Technical details

  • Root cause 1 – unrestricted proxy trust: TarsWeb’s app.js sets Koa’s app.proxy = true without restricting which upstream proxies are trusted, so the application derives the client’s source IP directly from the client-supplied X-Forwarded-For header.
  • Root cause 2 – conflated allowlist and identity logic: The SSO middleware (midware/ssoMidware.js) uses a single code branch to both skip authentication for IP-allowlisted callers (config/loginConf.js lists 127.0.0.1/localhost as trusted) and to assign the effective account identity from the caller-supplied uid query parameter, without validating any ticket, cookie, or password.
  • Trigger conditions: An attacker sends a request with the header X-Forwarded-For: 127.0.0.1 and appends a uid query parameter naming an existing account (e.g., ?uid=admin) to any endpoint under /api, /pages/server/api, /k8s/api, or /pages/k8s/api.
  • Attack vector: Network-based, no authentication or user interaction required, low attack complexity.
  • Impact: Full unauthenticated impersonation of any account, including administrators — enabling user/role management, service configuration changes, and package/binary deployment across the managed TARS platform.

Affected software

  • TarsCloud TarsWeb versions 0 through 3.0.14 (inclusive)

Severity

  • CVSS Score: 9.3 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to TarsWeb 3.0.16 or later, which separates the IP-allowlist handling from identity assignment so that allowlisted callers receive only a configured default account rather than an attacker-controlled uid.
  • If immediate patching is not possible:
    • Disable or remove app.proxy = true (or restrict trusted proxies explicitly) so X-Forwarded-For cannot be spoofed by external clients.
    • Remove or tighten the ignoreIps allowlist in config/loginConf.js, and ensure any network path reaching TarsWeb passes through a proxy layer that strips/overwrites client-supplied X-Forwarded-For headers before they reach the application.
    • Restrict network access to the TarsWeb management interface to trusted internal networks/VPN only, and place it behind an authenticating reverse proxy until patched.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge