CVE-2026-54253

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-82393 (ENISA EUVD)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.4%CVSS: 8.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

TS3 Manager is modern web interface for maintaining Teamspeak3 servers. Prior to 2.2.6, the /api/download handler in packages/server/routes/api.js passes the attacker-controlled port query parameter to socket.connect(port, host) and returns the resulting error.message through res.status(400).send(error.message) as text/html without a Content Security Policy. When a logged-in operator follows a crafted top-level link, the reflected value executes in the manager origin. The token cookie set in packages/ui/src/store/modules/query.js lacks HttpOnly, Secure, and an explicit SameSite attribute, allowing the script to read the token and call the autofillform event in packages/server/socket.js. autofillform returns the decoded JWT, including the cleartext ServerQuery password, enabling operator-session hijacking and control of the managed TeamSpeak server when the operator uses administrative ServerQuery credentials. A valid operator session and user interaction are required. This issue is fixed in 2.2.6.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
53
EG Risk 53/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

September 17, 2026

Last Modified

September 30, 2026

Advisory Details (3)

Auto-updated Sep 17, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v2.2.6

Patch available: joni1802/ts3-manager v2.2.6

https://github.com/joni1802/ts3-manager/releases/tag/v2.2.6
GitHub commit Patch Available

commit 48df540786d2 (joni1802/ts3-manager)

Patch available: joni1802/ts3-manager v2.2.6 (contains commit 48df540786d2)

https://github.com/joni1802/ts3-manager/commit/48df540786d2784c5d7b9bd55786d63e31288d07
GitHub advisoryMentions a patch (unverified)

Reflected XSS via /api/download port parameter steals operator session · Advisory · joni1802/ts3-manager · GitHub

https://github.com/joni1802/ts3-manager/security/advisories/GHSA-3cgm-7p4g-gffj

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 47× 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.

  1. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-30 22:28 UTCEG score recompute
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-10-25 14:19 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-24 01:26 UTCEG score recompute
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-10-18 03:31 UTCEG score recompute
  21. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-17 04:23 UTCEG score recompute
  23. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
Show 55 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-10-12 15:56 UTCEG score recompute
  4. 2026-10-11 19:39 UTCEG score recompute
  5. 2026-10-11 16:55 UTCEG score recompute
  6. 2026-10-11 14:01 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-10-11 02:53 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-10-10 02:45 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-10-08 17:40 UTCEG score recompute
  13. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-10-08 05:05 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-10-06 17:27 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-05 19:23 UTCEG score recompute
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-10-05 08:22 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-03 23:18 UTCEG score recompute
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-03 01:13 UTCEG score recompute
  25. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  26. 2026-10-02 03:10 UTCEG score recompute
  27. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  28. 2026-09-30 17:49 UTCEG score recompute
  29. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  30. 2026-09-29 19:51 UTCEG score recompute
  31. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  32. 2026-09-28 21:45 UTCEG score recompute
  33. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  34. 2026-09-27 23:42 UTCEG score recompute
  35. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  36. 2026-09-27 01:39 UTCEG score recompute
  37. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  38. 2026-09-26 03:34 UTCEG score recompute
  39. 2026-09-24 18:27 UTCEG score recompute
  40. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  41. 2026-09-24 07:25 UTCEG score recompute
  42. 2026-09-23 20:24 UTCEG score recompute
  43. 2026-09-23 19:53 UTCEG score recompute
  44. 2026-09-23 19:10 UTCEG score recompute
  45. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  46. 2026-09-22 20:41 UTCEG score recompute
  47. 2026-09-21 22:38 UTCEG score recompute
  48. 2026-09-21 00:36 UTCEG score recompute
  49. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  50. 2026-09-20 02:33 UTCEG score recompute
  51. 2026-09-19 04:29 UTCEG score recompute
  52. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  53. 2026-09-17 19:26 UTCEG score recompute
  54. 2026-09-17 18:42 UTCEG score recomputeFirst assessed: 8.2 HIGH
  55. 2026-09-17 18:39 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54253?
CVE-2026-54253 is a high-severity vulnerability; its CVE record was published on September 17, 2026. TS3 Manager is modern web interface for maintaining Teamspeak3 servers. Prior to 2.2.6, the /api/download handler in packages/server/routes/api.js passes the attacker-controlled port query parameter to socket.connect(port, host) and returns the resulting error.message through…
When was the CVE record for CVE-2026-54253 published?
The CVE record for CVE-2026-54253 was published on September 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-54253 actively exploited?
CVE-2026-54253 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54253?
CVE-2026-54253 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54253?
A fix for CVE-2026-54253 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54253?

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

Book a Demo →Browse All CVEs