Skip to main content

Upgrading to 1.26.0

Released 2026-11-01. Everything in the release: changelog. How to upgrade: Upgrade.

What's new​

  • Attack paths, a new check, finds the ways an account on a Linux machine could become root, such as a sudo rule that opens a shell, the docker group or a script root runs that others can change. It also finds private keys, cloud credentials and .env files that other accounts can read, and SSH keys trusted on 3 or more machines. It only reads, and never reads a secret's contents. See Attack paths.
  • Attack paths notifications, for the channels that tick them.

Before you upgrade​

Back up: database schema 31. The server keeps the SSH key fingerprints each machine trusts, so 1.25 and earlier can't open the database afterwards. Back up first.

To use it​

  1. Upgrade the agents to 1.26.0: the server refuses the check for older agents and says so, and the Agents page lists them.
  2. Add Attack paths to your hosts' schedule. SSH keys trusted on many machines are found once those machines have each been scanned with it.
  3. To be told about new findings, tick Attack paths on a notification channel.

Kubernetes (Helm and Kustomize)​

Upgrade as on Upgrade: the chart upgrades the node agents with the server. On a Kubernetes node the check looks at the node itself, not its pods.

Install script and packages​

Nothing else to do.

Docker Compose​

Nothing else to do.

Known issues​

None.