Skip to content

v0.38.0

Choose a tag to compare

@github-actions github-actions released this 03 Nov 11:33
· 74 commits to main since this release

A security release

v0.38.0 fixes every problem three security audit passes over the server found, one of them high severity. Upgrade soon. Several fixes change what non-admins see; read the upgrade notes first.

Security

  • Hidden rows could be read one guess at a time. On SQLite, a ?filter= that fails on some values answered differently depending on rows the list rule hides. The filter now runs only on rows the rule admits.
  • Password resets didn't end every session. A token issued in the same second as a reset, or by a sign-in, refresh, provider merge or impersonation racing it, could outlive it. Tokens now carry the reset stamp they were issued after and end as soon as it changes. That works across cluster nodes without relying on their clocks. Impersonation tokens end with their admin, and a reset voids pending provider merges.
  • Someone who registered your address first kept their way in. The first magic-link sign-in on an unverified account now ends the password, MFA, sessions, provider links and push devices they set up.
  • Read rules on other paths:
    • writes the caller can't view return null;
    • for non-admins, admin-only collections look missing everywhere, including batch, history, filters and the public OpenAPI;
    • singletons are read under their view rule in batch and aggregate;
    • record history decrypts only fields marked encrypted.
  • Requests that cost the server far too much:
    • long email addresses;
    • % patterns in rules;
    • animated GIF and oversized image thumbnails;
    • unbounded relation expand (now 6 levels, 20 paths);
    • batches charged one rate-limit token in all (now one per op).
  • Views can no longer publish password hashes past the private-column check.
  • MCP: stored content can't close the <user-data> marker, more outputs are marked, and a stdio session rechecks its token on every request.
  • Maintenance mode lets an API token through only when it acts as admin for that request.
  • Releases and installers:
    • signatures are accepted only from the release workflow at the version's tag;
    • installers stop when the checksum can't be fetched;
    • Docker images are built only from signed releases.

SDKs

No SDK release needed: JS SDK 0.10.0 and Dart vaultbase 0.6.0 (with vaultbase_flutter 0.1.5) work with this release. A batch that writes can't contain a list; send lists in their own batch.

See the changelog for the full list.

Upgrade notes

  • Admin-only collections answer 404 to non-admins (was 403) when their list, view and create rules are all admin-only.
  • Writes the caller can't view return {"data": null}.
  • A batch that writes can't list (422). A batch costs one rate-limit token per op.
  • Expand is limited to 6 levels and 20 paths.
  • New collections can't be named admin, auth, files, collections, health, batch, custom, realtime or mcp.
  • View queries that read vaultbase_* tables or serialize whole rows of auth or password tables are refused. Existing views keep working until you alter them.
  • MCP clients that parse write, SQL, job, seed or record/log/audit resource output as raw JSON now get it inside <user-data> tags.
  • Magic-link sign-in on an unverified account replaces its password; the user sets a new one through a reset.
  • Installers need --skip-checksum (-SkipChecksum) for releases without checksums. vaultbase update and --verify-sig accept only signatures from the release workflow at the version's tag.
  • Signing out with a password reset, email change or magic-link claim stops push notifications until the apps register again.
  • Upgrade notes for earlier releases apply if you are coming from before v0.37.0.

Full Changelog: v0.37.0...v0.38.0