CVE-2026-80349

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-23. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists TarsCloud TarsWeb versions up to and including 3.0.14 as affected. No release containing a fix is confirmed on record.

TarsWeb decides whether a request comes from a trusted local caller using a client-controlled header. app.js sets Koa's proxy option to true without naming which upstream proxies may be trusted and without limiting the number of forwarded hops, so the request address Koa reports is taken from the X-Forwarded-For header supplied by the caller. In midware/ssoMidware.js a single branch covers both the ignored-path list and the ignoreIps allowlist from config/loginConf.js, which contains the loopback address, and that branch assigns the effective account identity from the uid query parameter before falling through to the request without validating any ticket, cookie or password. A request carrying a forged X-Forwarded-For value naming the loopback address and a uid naming an existing account therefore reaches every route the console mounts as that account, including an administrator, with no credential of any kind. Those routes include user and role administration, service configuration, and package upload and deployment. Version 3.0.16 separates the two branches so that a match on the address allowlist assigns the configured default account rather than one named by the caller.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 26, 2026

Last Modified

September 23, 2026

Advisory Details (5)

Auto-updated Oct 8, 2026
No fix on record yet.
Web page

Unauthenticated admin impersonation via spoofed X-Forwarded-For in tars-web session middleware · Issue #212 · TarsCloud/TarsWeb · GitHub

https://github.com/TarsCloud/TarsWeb/issues/212
Web page

TarsWeb through 3.0.14 Authentication Bypass via Spoofed X-Forwarded-For and uid Parameter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/tarsweb-through-3.0.14-authentication-bypass-via-spoofed-x-forwarded-for-and-uid-parameter
Web page

TarsWeb/midware/ssoMidware.js at v3.0.14 · TarsCloud/TarsWeb · GitHub

https://github.com/TarsCloud/TarsWeb/blob/v3.0.14/midware/ssoMidware.js
Web page

TarsWeb/app.js at v3.0.14 · TarsCloud/TarsWeb · GitHub

https://github.com/TarsCloud/TarsWeb/blob/v3.0.14/app.js
Web page

GitHub - TarsCloud/TarsWeb: TARS Projects Dashboard · GitHub

https://github.com/TarsCloud/TarsWeb

Vendor Advisories for CVE-2026-80349(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 129× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 166 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 66 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 01:37 UTCEG score recompute
  2. 2026-10-14 01:37 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  4. 2026-10-12 21:47 UTCEG score recompute
  5. 2026-10-12 21:47 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  7. 2026-10-12 14:57 UTCEG score recompute
  8. 2026-10-12 05:23 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-11 19:21 UTCEG score recompute
  10. 2026-10-11 16:37 UTCEG score recompute
  11. 2026-10-11 13:56 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  14. 2026-10-10 16:01 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-10 11:13 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-10 06:49 UTCEG score recompute
  17. 2026-10-10 06:49 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  19. 2026-10-09 07:52 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-09 03:28 UTCEG score recompute
  21. 2026-10-09 03:28 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-10-08 06:25 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-08 01:59 UTCEG score recompute
  25. 2026-10-08 01:59 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  2. 2026-10-07 10:25 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-07 05:58 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-07 01:35 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-06 21:11 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-06 16:39 UTCEG score recompute
  7. 2026-10-06 16:39 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  9. 2026-10-06 11:59 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-06 07:37 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-06 01:46 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-05 18:55 UTCEG score recompute
  13. 2026-10-05 18:55 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-10-05 14:32 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-05 10:10 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-05 05:47 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-05 01:24 UTCEG score recompute
  19. 2026-10-05 01:24 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-10-04 20:35 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-04 15:35 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-04 11:02 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-04 06:24 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-04 02:01 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-03 20:46 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-03 16:13 UTCEG score recompute
  28. 2026-10-03 16:13 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  30. 2026-10-03 06:04 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-03 01:33 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-02 20:57 UTCEG score recompute
  33. 2026-10-02 20:57 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  35. 2026-10-02 15:36 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-02 11:01 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-02 06:23 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-02 01:15 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-01 19:57 UTCEG score recompute
  40. 2026-10-01 19:57 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  42. 2026-10-01 14:18 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-01 09:55 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-01 05:33 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-01 01:04 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-09-30 19:59 UTCEG score recompute
  47. 2026-09-30 19:59 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  49. 2026-09-30 11:35 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-09-30 06:11 UTCEG score recompute
  51. 2026-09-30 06:11 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-09-29 12:32 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-09-29 06:06 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-09-29 01:43 UTCEG score recompute
  55. 2026-09-29 01:43 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-09-28 21:21 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-09-28 14:15 UTCEG score recompute
  58. 2026-09-28 14:15 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  60. 2026-09-28 09:52 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-09-28 05:29 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-09-28 01:07 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-09-27 20:44 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-09-27 16:21 UTCEG score recompute
  65. 2026-09-27 16:21 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  67. 2026-09-27 11:58 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-09-27 06:46 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-09-27 02:13 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-09-26 21:12 UTCEG score recompute
  71. 2026-09-26 21:11 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  73. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  74. 2026-09-25 13:51 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-09-25 09:01 UTCGHSA enrichmentGHSA-2h2x-v86q-mgw5 · GitHub severity CRITICAL · GitHub CVSS 9.8

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-80349?
CVE-2026-80349 is a critical-severity vulnerability; its CVE record was published on August 26, 2026. TarsWeb decides whether a request comes from a trusted local caller using a client-controlled header. app.js sets Koa's proxy option to true without naming which upstream proxies may be trusted and without limiting the number of forwarded hops, so the request address Koa reports is taken from the…
When was CVE-2026-80349 made public?
CVE-2026-80349 was made public on August 26, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 26, 2026. EchelonGraph's copy of the record carries a last-modified date of September 23, 2026; the record at its source may have been updated since.
Is CVE-2026-80349 actively exploited?
CVE-2026-80349 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80349?
CVE-2026-80349 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80349?
No fix for CVE-2026-80349 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists TarsCloud TarsWeb versions up to and including 3.0.14 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-80349 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-80349

Explore →

Is Your Infrastructure Affected by CVE-2026-80349?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs