CVE-2026-53548: Termix: IDOR — Authenticated user can fetch SSH passwords for hosts owned by other users
Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. Prior to 2.6.1, the GET /host/db/host/:id/password endpoint in src/backend/database/routes/host.ts accepts an authenticated user's numeric host ID and the field=password or field=sudoPassword query without enforcing host ownership during credential resolution. A failed requester-scoped lookup can resolve the host with the owner's context and return the owner's plaintext credential, allowing any authenticated user with a valid JWT to enumerate sequential hosts.id values and retrieve SSH or sudo passwords belonging to other users. The disclosed credentials can then be used to access and control managed systems outside the Termix instance. This issue is fixed in version 2.6.1.
Security readout for executives and security teams
Plain-English summary
An authenticated Termix user may access SSH or sudo passwords stored for another user's managed hosts. Those credentials could enable access to systems beyond Termix, creating serious confidentiality and control risks across connected infrastructure.
Executive priority
Treat this as emergency remediation for affected multi-user deployments. Credential theft could extend compromise from Termix into managed servers, including privileged access. Prioritize version verification, access restriction, credential rotation, and investigation even without confirmed active exploitation.
Technical view
The host-password API lacks an effective ownership check when resolving credentials. A valid JWT holder can reference numeric host identifiers and potentially receive another owner's plaintext SSH or sudo password. The CVSS 3.1 score is 9.6, reflecting network reachability, low complexity, limited required privileges, and cross-system impact.
Likely exposure
Exposure is highest in multi-user Termix deployments that store SSH or sudo passwords. Any authenticated account with a valid JWT may represent risk. Single-user deployments have less cross-user exposure, but compromised accounts and disclosed infrastructure credentials remain concerns.
Exploitation context
The bundle describes predictable host identifiers and low-complexity credential disclosure, but provides no evidence of exploitation in the wild. The CVE is not listed as KEV in the supplied data. Authentication is required; no user interaction is required.
Researcher notes
The supplied bundle is internally inconsistent: its description says versions before 2.6.1 are vulnerable and 2.6.1 fixes the issue, while the affected entry says versions below 2.3.2 and references a 2.3.2 release. Confirm the authoritative affected and fixed ranges with the vendor advisory before closing remediation.
Mitigation direction
Prioritize upgrade to 2.6.1 as named in the description, while verifying vendor guidance because the supplied version metadata conflicts.
Restrict Termix access and disable unnecessary user accounts until remediation is confirmed.
Rotate SSH and sudo credentials stored in potentially affected Termix deployments.
Review vendor guidance for any additional containment or credential-handling recommendations.
Validation and detection
Inventory Termix instances, deployed versions, user accounts, and hosts with stored SSH or sudo passwords.
Confirm the installed release contains the vendor's ownership-validation correction.
Review available application and reverse-proxy logs for unusual host-password requests across multiple host identifiers.
Verify rotated credentials no longer authenticate and investigate unexpected access to managed systems.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-285: 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.
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.
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.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-285 · source CWE mapping
Improper Authorization
Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.