CVE-2026-59105
CRITICALEPSS 74th pctlDescription
Jumis (formerly Tildes Jumis) creates and uses a Microsoft SQL Server login named ##Tilde_JumisAdmin## whose password is derived deterministically from a single non-secret input - the SQL Server name (@@servername). The derivation algorithm is hard-coded in the client application and is identical across every installation; it contains a hard-coded secret key for entropy. Because the only input (the server name) is not secret - the instance suffix is hard-coded and the host name is discoverable via the SQL Server Browser service (UDP 1434), the TDS pre-login response, or DNS/NetBIOS - any party able to reach a Jumis SQL Server can compute the password offline and authenticate. The ##Tilde_JumisAdmin## login is a member of the sysadmin server role. Successful authentication therefore grants full administrative control of the SQL Server instance and read/write access to every customer's accounting database hosted on it. The on-premise server installation also programmatically enables xp_cmdshell during routine operation, so sysadmin access escalates to operating-system command execution on the database server.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Elevated risk: more likely to be exploited than 74% of all known CVEs.
References
Related Vulnerabilities
Other CWE-547 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-14837 | Critical | 9.1 | 1.7% | - | Fix |
| CVE-2024-32021 | Low | 3.9 | 1.0% | - | Fix |
| CVE-2025-30206 | Critical | 9.8 | 0.9% | - | - |
| CVE-2023-1712 | Critical | 9.8 | 0.9% | - | Fix |
| CVE-2025-49151 | Unscored | - | 0.6% | - | - |
| CVE-2025-2081 | Unscored | - | 0.4% | - | - |
Common questions
How do I fix CVE-2026-59105?
No published fix for CVE-2026-59105 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-59105 being actively exploited?
Not that we know of. CVE-2026-59105 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 1.4% is the estimated probability that it will be exploited in the next 30 days. That is higher than 74% of all scored CVEs.
How severe is CVE-2026-59105?
CVE-2026-59105 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-59105
Markdown
[](https://tridentstack.com/cve/CVE-2026-59105)HTML
<a href="https://tridentstack.com/cve/CVE-2026-59105"><img src="https://tridentstack.com/cve/badge/CVE-2026-59105.svg" alt="CVE-2026-59105"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-12.