Termix 26.11.1 upgrade: security fixes, hashed session tokens

released
lab run
upgraded from
26.10.0
guest
Ubuntu 26.04 VM
tested
yes, in our lab

Summary

Termix 26.11.1 is a large release. It adds an actions system for plugins, API keys limited to read-only or to running actions, and an admin setting that stops anyone saving passwords and keys on hosts and credentials. It also fixes many UI problems and a group of security and permission bugs.

Breaking changes and deprecations

The release notes have no section for breaking changes. These changes can affect an existing install (all taken from the release notes, not tested by us unless stated below):

  • Session tokens are now stored as hashes, so a copy of the database holds no working logins.
  • Plugins that a new image adds start on only when they are recommended. The rest are installed but left off, and an admin turns them on in the Plugins tab.
  • Host status, import and export, and credential tools now start on for new installs.
  • Changing your password now signs out your other sessions.
  • The Linux Flatpak now installs from flatpak.termix.site.

Tested in our lab

We tested the standard Docker Compose install from the Termix docs. We installed 26.10.0 and created an admin user and one SSH host entry. Then we stopped the container with docker compose down, changed the image tag to 26.11.1, pulled it and started it again.

  • 26.10.0 started healthy and the web UI answered.
  • After the upgrade, 26.11.1 reported healthy and the web UI returned HTTP 200.
  • We logged in again with the same admin account, and the host we had created was still listed.
  • 26.10.0 logged “Loaded 34 plugin(s)” at startup. 26.11.1 logged “Loaded 21 plugin(s)”. That fits the release note about new plugins being left off, but we did not check which plugins were off or confirm the cause.
  • 26.11.1 logs [WARN] lines saying some plugins serve routes without core authentication (docker, remote-desktop, ssh-terminal, webauthn). We did not capture the 26.10.0 warnings, so we can’t say whether these are new.

Not tested: the new actions and API key limits, the admin “no saved passwords” setting, other plugins, the desktop apps, MySQL/PostgreSQL, and real SSH sessions. We also logged in fresh after the upgrade, so we did not check what happens to a session that was open before it. With hashed tokens, you may need to sign in again.

Lab log

$ docker compose up -d
[...]
$ docker ps --format "{{.Names}} {{.Image}} {{.Status}}"
termix ghcr.io/termix-ssh/termix:26.10.0 Up 18 seconds (healthy)
$ docker logs termix 2>&1 | tail -8
[...]
[8:04:32 AM] [INFO] [🚀] Loaded 34 plugin(s) [op:plugin_init]
[8:04:32 AM] [SUCCESS] [🚀] Termix backend started successfully [op:backend_init_complete,duration:3465ms]
$ docker compose down
[...]
$ sed -i "s/termix:26.10.0/termix:26.11.1/" docker-compose.yml
$ docker compose pull
[...]
$ docker compose up -d
 Container termix Started
$ docker ps --format "{{.Names}} {{.Image}} {{.Status}}"
termix ghcr.io/termix-ssh/termix:26.11.1 Up 23 seconds (healthy)
$ curl -s -b jar localhost:8080/host/db/host | head -c 160
[{"id":1,"userId":"wjDChNQ-cuyjY5RHT4FAd","connectionType":"ssh","name":"labhost","ip":"10.99.0.10","port":22,"username":"ubuntu","folder":null,"parentHostId":n
$ curl -s -o /dev/null -w "%{http_code}\n" localhost:8080/
200
$ docker logs termix 2>&1 | grep -E "Loaded|started"
[...]
[8:05:24 AM] [INFO] [🚀] Loaded 21 plugin(s) [op:plugin_init]
[8:05:24 AM] [SUCCESS] [🚀] Termix backend started successfully [op:backend_init_complete,duration:3553ms]

Reported by others

Nothing beyond the release notes. They list 10 closed issues and, among the fixes, these security-related ones:

  • A session that still has to set up a second factor can no longer open terminals or other live connections.
  • A login waiting on its second factor can no longer be used for desktop sync.
  • Time-limited manage access can no longer be used to share a host or credential past that access.
  • Host settings that need a permission can no longer be changed through import, bulk edit, host defaults or desktop sync without it.
  • Plugin connections to a shared host are no longer reused between people.

We did not test any of these.

Verdict

Upgrade now. In our lab the standard Docker upgrade from 26.10.0 kept the data and came up healthy. The fixes for second-factor and sharing permissions are worth having. Back up the /app/data volume first, as with any upgrade. After the upgrade, check the Plugins tab to see which plugins are on, and expect to sign in again.

sources