Security readout for executives and security teams
Plain-English summary
A signed-in low-privileged Termix user could cause a vulnerable server to send another user’s stored SSH password or private key to an attacker-controlled SSH server. This threatens privileged infrastructure credentials and may enable follow-on system access. Termix fixed the flaw in version 2.3.2.
Executive priority
Treat this as an urgent credential-exposure issue. Prioritize internet-accessible and multi-user Termix instances, upgrade promptly, and investigate suspicious outbound SSH activity. Because leaked credentials may grant access beyond Termix, suspected exposure should trigger credential rotation and review of affected infrastructure access.
Technical view
Before 2.3.2, the terminal WebSocket accepts a user-controlled host identifier without enforcing host ownership or access. Credential resolution may fall back to the host owner’s credential, which is then combined with attacker-controlled connection details. Exploitation requires authentication and the victim user’s data key to be unlocked.
Likely exposure
Exposure is most likely in multi-user Termix deployments below 2.3.2 where low-privileged accounts can access the terminal WebSocket, stored SSH credentials exist, and another user’s data key is unlocked. The bundle provides no CPEs or deployment prevalence data, so fleet-wide exposure cannot be estimated.
Exploitation context
The attack is network-accessible, requires a low-privileged authenticated account, needs no victim interaction, and can disclose high-value SSH secrets. The source bundle reports no CISA KEV listing and provides no evidence of active exploitation. Practical success depends on the victim user’s data key being unlocked.
Researcher notes
The flaw combines missing object-level authorization with missing authorization enforcement, mapped to CWE-639 and CWE-862. Its critical 9.6 CVSS 3.1 rating reflects low-complexity remote abuse by an authenticated user, cross-user credential disclosure, and potential downstream integrity impact. Availability impact is not asserted.
Mitigation direction
- Upgrade Termix to version 2.3.2 or later.
- Restrict untrusted or low-privileged Termix access until the upgrade is complete.
- Review vendor guidance for any additional remediation or credential-handling recommendations.
- Assess and rotate stored SSH credentials if suspicious exposure is identified.
Validation and detection
- Inventory Termix instances and confirm every deployed version is 2.3.2 or later.
- Identify deployments allowing multiple users or low-privileged terminal access.
- Review logs for unexpected outbound SSH connections or unusual terminal WebSocket activity.
- Confirm host credential resolution enforces ownership or explicit access after upgrading.
- Check whether sensitive users’ data keys were unlocked during suspected activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-53546 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N3.15.8GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Termix-SSH/Termix/security/advisories/GHSA-57gp-39c7-4g9rCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/Termix-SSH/Termix/pull/874CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/Termix-SSH/Termix/commit/52f4e51ae03b5b8d2608e1383e2ccf79d290132bCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/Termix-SSH/Termix/releases/tag/release-2.3.2-tagCVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.