- Keep the Console at version 8.7.37 for compatibility with the 1.9 server APIs.
- Validate presence messages in realtime like the HTTP endpoint and keep the caller's identity across GraphQL fields.
- Never fall back to the platform database for a missing project.
- Upgrade the Brotli runtime to brotli-libs 1.2.1 via appwrite/base 1.4.6 to fix an out-of-bounds write in the Brotli decoder (CVE-2026-111497).
- Authenticate API keys before skipping Origin checks, and allow admin mode only from console origins.
- Hold API keys and JWTs to their original grant, and refuse invalid keys instead of running them as a guest.
- Keep write-only secrets on their endpoint and bind ephemeral keys to their project and purpose. behavior changed · inferred, marked in the notes below
- Stop returning secret messaging provider credentials, webhook passwords and key secrets to callers without the right grant.
- Clear email-bound tokens and invites when the email or phone changes, and revoke prior credentials when OAuth links an unverified account.
- Rate limit token sign-ins per account and compare MFA codes in constant time.
- Require users.write to read MFA recovery codes and gate development-only routes on _APP_ENV=development. behavior changed · inferred, marked in the notes below
- Enforce permissions when staging transaction operations and rate limit guest transaction writes.
- Gate increment/decrement operations and scope the list cache to collection permissions.
- Require project access for admin mode realtime connections and apply HTTP session rules to realtime connections.
- Validate file names and build Content-Disposition per RFC 6266, and refuse reads of incomplete uploads.
- Keep the platform default storage bucket private and cap avatar remote fetches with rate limiting on image and favicon requests.
- Verify the GitHub webhook signature before fan-out, verify installation access, and sign and expire installation state.
- Verify GitHub API certificates and confine repository root directories.
- Keep migration, certificate check and SMTP connections on public addresses, with the new _APP_ALLOWED_INTERNAL_ADDRESSES option to allow an internal relay. behavior changed · inferred, marked in the notes below
- Keep session cookies and the fallback session header out of function and site requests.
- Escape the redirect in email templates and require files.read to attach files to emails. behavior changed · inferred, marked in the notes below
7 changes to check, marked in the notes below
From Appwrite
Appwrite 1.9.10 is a security release for self-hosted deployments on the 1.9 line. It backports the hardening shipped in 2.6.2 across auth, API keys, databases, realtime, GraphQL, storage, VCS, functions, migrations and messaging, and moves the runtime to a patched Brotli. It keeps Console 8.7.37 for compatibility with the 1.9 server APIs. Upgrading from 1.9.9 reuses migration V25 and introduces no schema changes, but a few fixes tighten defaults, so read Upgrade first.
Highlights
- Brotli CVE-2026-111497.
appwrite/base1.4.6 requiresbrotli-libs1.2.1, which fixes an out-of-bounds write in the Brotli decoder (appwrite/docker-base#128, #14912). libcurl and the Swoole client decodebrresponses from URLs users control, such as avatar and favicon fetches, webhooks and migration sources. - API keys and JWTs stay within their grant, invalid keys are refused instead of running as a guest, and secrets stay write-only (#14910).
- Realtime and GraphQL follow the HTTP session and permission rules (#14913).
- Outbound connections stay on public addresses for SMTP, migration sources and certificate checks, with the new
_APP_ALLOWED_INTERNAL_ADDRESSESto allow an internal relay (#14911).
Fixes
- Auth and accounts: authenticate API keys before skipping Origin checks (#14910, backports #14352), allow admin mode only from console origins (#14813), clear email-bound tokens and invites when the email or phone changes (#14347, #14819), revoke prior credentials when OAuth links an unverified account (#14801), rate limit token sign-ins per account (#14880), compare MFA codes in constant time (#14762).
- Keys and users: hold keys and JWTs to their original grant (#14888), keep write-only secrets on their endpoint and bind ephemeral keys to their project and purpose (#14795, #14825), keep key and webhook secrets out of the 1.9.4 response format (#14815), hide credentials from impersonators (#14818), require
users.writeto read MFA recovery codes (#14872), bound imported password hash costs (#14825), gate development-only routes on_APP_ENV=development(#14824). behavior changed · inferred - Databases: enforce permissions when staging transaction operations, and rate limit guest transaction writes (#14913, backports #14754, #14762), gate increment/decrement and fix upsert permissions (#14755), scope the list cache to collection permissions and gate inline encryption (#14791).
- Organizations and projects: accept only keys and console sessions on organization routes (#14779), evaluate project roles against the project in the path (#14787), require owner on both organizations to transfer a project (#14780).
- Realtime and GraphQL: require project access for admin mode connections (#14790), apply the HTTP session rules to realtime connections (#14803), send migration events only to project readers (#14805), validate presence messages like the HTTP endpoint (#14829), keep the caller's identity across GraphQL fields (#14820), cost invalid list limits at the complexity cap (#14821).
- Storage and platform: validate file names and build
Content-Dispositionper RFC 6266 (#14789), refuse reads of incomplete uploads (#14876), keep the platform default bucket private (#14814), cap avatar remote fetches and rate limit image and favicon requests (#14788), key rate limits on the route path and keep them on out-of-rangeContent-Range(#14785, #14816), drop client-named Swoole uploads and never call request values as code (#14909, backports #14897, #14792), strip control characters from webhook headers (#14806). - VCS, functions and sites: verify the GitHub webhook signature before fan-out, verify installation access, and sign and expire installation state (#14911, backports #14771, #14783, #14793), verify GitHub API certificates (#14802), confine repository root directories (#14808), bind branch preview rules to their project (#14786), validate reserved execution headers case-insensitively (#14185), keep session cookies and the fallback session header out of function and site requests (#14874, #14823).
- Migrations and messaging: keep migration, certificate check and SMTP connections on public addresses (#14794, #14870, #14811), validate NHost source hosts (#14798), check DocumentsDB and VectorsDB source key scopes (#14868), stop returning secret messaging provider credentials (#14875), require
files.readto attach files to emails (#14827), escape the redirect in email templates (#14822), never fall back to the platform database for a missing project (#14812). behavior changed · inferred
Under the hood
- Fixes in vendored libraries that 1.9's dependency set can't update are applied in Appwrite's own code: the Swoole upload guard, request values never being called as code, and GitHub API certificate verification (#14909).
- Not backported, because the feature doesn't exist on 1.9: ID-token email policies (#14633), console realtime tails (#14797), the jobs callback secret (#14116), the onboarding hook (#14807) and multi-provider VCS events (#14800). #14778 was already the behaviour on 1.9.
- 1.9.10 maps to migration V25, the same class as 1.9.9.
Removed
No environment variables, collections or public APIs are removed. Secrets that were previously readable (messaging provider credentials, webhook passwords and key secrets for callers without the right grant) are no longer returned.
Install
docker run -it --rm \
--publish 20080:20080 \
--volume /var/run/docker.sock:/var/run/docker.sock \
--volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \
--entrypoint="install" \
appwrite/appwrite:1.9.10
Upgrade
Back up your database and persistent storage first. From the parent directory of an existing 1.9.9 installation:
docker run -it --rm \
--publish 20080:20080 \
--volume /var/run/docker.sock:/var/run/docker.sock \
--volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \
--entrypoint="upgrade" \
appwrite/appwrite:1.9.10
cd appwrite
docker compose exec appwrite migrate
Check these before upgrading:
-
Run the upgrade interactively as shown, or pass your current ports with
--http-portand--https-port: a non-interactive upgrade resets custom ports to 80/443 (also true of 1.9.9). -
New optional variable
_APP_ALLOWED_INTERNAL_ADDRESSES: project SMTP, messaging SMTP providers and migration sources on a private or reserved address must be listed here. behavior changed · inferred -
Ephemeral keys minted before the upgrade are refused until reissued, and an invalid
X-Appwrite-Keynow returns401instead of running the request as a guest. behavior changed · inferred -
Changing an SMTP host, port or
secureflag, or an OAuth provider endpoint, requires sending the secret again. behavior changed · inferred -
Sites and functions whose stored root directory contains
..fail to build until the directory is changed to a path inside the repository. behavior changed · inferred -
Mock routes and the time-travel task require
_APP_ENV=development. behavior changed · inferred
Contributors
Thank you to everyone who contributed to 1.9.10:
@ChiragAgg5k @abnegate @Meldiron @ArnabChatterjee20k
Full Changelog: https://github.com/appwrite/appwrite/compare/1.9.9...1.9.10