Skip to content

v2.5.8

Choose a tag to compare

@github-actions github-actions released this 18 Nov 23:49
· 37 commits to main since this release

HexDB 2.5.8 fixes what a second re-review (of 2.5.7) found: a protected field inside an array that a row move could reveal, a one-time code that could sign in once per hex, and five smaller issues. Upgrade every hex.

Security

  • Moving a row can't reveal protected fields inside arrays. 2.5.7 refused a write that would uncover a hidden field, but checked contacts.secret only where contacts is an object. Where it's an array of objects (as reads hide it), changing only tenant from A to B could still reveal it. The check now looks through arrays, as reads do.
  • A one-time code signs in once across the lattice. A replica recorded the code's time step only for itself, so the same TOTP code could also sign in on the Overseer or another replica within its 30 seconds. A replica now signs in with a code only once the Overseer has recorded its step; if no Overseer answers, the sign-in fails (try again in a moment).

Fixed

  • Unique values of expired documents. A document past its ttl that hadn't been swept yet still held its unique value, refusing a new document with that value for up to a sweep interval. The expired document is now deleted in the same commit as the new one.
  • Dead letters, again. A message being moved to a dead-letter queue whose commit took longer than 60 seconds (a slow disk, a lattice waiting for acknowledgements) could be dropped from that queue's ready set. It's now kept until the move commits, however long it takes.
  • SQL memory, joins and results. limits.sql_max_mb bounded the documents a statement reads, but not the rows it builds from them: a cross join or wide projection over a small read could grow without bound. Joined rows, groups and results now have a budget of the same size, and a statement over it is refused.
  • API keys after a lattice-secret rotation. A replica that couldn't reach an Overseer (one restarting) waited 10 seconds before asking again to re-hash a key, so a key used once in that window stayed on the old hash. It now asks again on the key's next use. The hex that stores a new hash logs Re-hashed API key '<name>' with the current lattice secret.
  • Script timeouts (documentation). The MANUAL now says that stopping a script's process group is cleanup, not containment: on Linux and macOS a process that leaves the group can outlive the timeout. Scripts aren't sandboxed; only administrators can register them, and functions.scripts = false refuses them.

Dependencies

  • lettre 0.11.24 (email): fixes six advisories published 2026-11-18 (RUSTSEC-2026-0560 to 0565), among them SMTP command injection through a bare line feed and STARTTLS reply injection. They affect sending email over SMTP: password recovery, invitations and alerts.

Upgrading

Restart the hexes one at a time, as usual: replicas first, the Overseer last. Until the Overseer runs 2.5.8, TOTP sign-ins on 2.5.8 replicas fail closed (the Overseer doesn't know /lattice/mfa-step yet): sign in on the Overseer, or upgrade it soon after the replicas.

Full Changelog: v2.5.7...v2.5.8