Skip to main content
← Vulnerabilities

Universal sysadmin credential vulnerability in Jumis

Affects Jumis (Tildes Jumis) for Windows builds before TJ7.0.141.36, fixed in that build. No separate vendor severity rating is given.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

9.8CriticalCNA
Exploited
No known exploitation
Fix
Fixed in TJ7.0.141.36
Who is exposed
Not reported

Do first: Upgrade to a fixed version: TJ7.0.141.36.

Published
Last modified
30/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post
  • Exploitation: none
  • Automatable: yes
  • Technical impact: total

Summary

Jumis (formerly Tildes Jumis), an accounting application, uses a built-in SQL Server administrator login whose password anyone can work out from the server's publicly discoverable name, so a remote attacker can log in without credentials and gain full control of the SQL Server instance and read and write every customer's accounting database. Because the software enables xp_cmdshell, that access can also be used to run operating system commands on the database server.

Read the original description

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.

cve.now Index

30Pcve.now Index 30 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: TJ7.0.141.36.

  • Workaround: Restrict network access to the SQL Server so that only the hosts that need it can reach the instance

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  5. Record last updated

Affected versions

  • Jumis Pro SIA Jumis

    fixed in TJ7.0.141.36

Evidence 2

  1. Link
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-59105

Is CVE-2026-59105 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Jumis creates a Microsoft SQL Server login named ##Tilde_JumisAdmin## whose password can be computed by anyone able to reach a Jumis SQL Server. Logging in with it gives sysadmin rights over the SQL Server instance and read/write access to every customer accounting database on it. On the on-premise server installation, which enables xp_cmdshell, this can extend to operating-system command execution.Source: offseq.com

Which versions are affected by CVE-2026-59105?

Jumis: before TJ7.0.141.36.Source: cve.now feed data

Am I affected, and how do I check?

Jumis / Tildes Jumis for Windows builds before TJ7.0.141.36 are affected. Check the build number in the Jumis version information against TJ7.0.141.36. The operating-system command execution part applies to the on-premise server installation.Source: offseq.com

How do I fix CVE-2026-59105?

Update to TJ7.0.141.36 or later. The vendor advisory says customers should update to that version.Source: offseq.com