Karakeep 0.35.0 upgrade: security fixes, redesign, no manual steps
Summary
Karakeep 0.35.0 is a big release focused on security and a redesign. The web app, mobile app and browser extension all get a new look. The reader view now uses Defuddle for article extraction. Smart lists can be built from tags, favourites, archive state and age, and are evaluated as a single SQL query. The release also fixes a long list of security issues and hardens the Docker images.
Breaking changes and deprecations
No breaking changes are listed in the release notes. One thing to know, as reported by the project:
- The web server and workers in the Docker image now drop privileges and capabilities. The release notes say no compose changes are needed. If you see permission errors on your data directory, look for a
WARNING: couldn't ...line in the logs and setKARAKEEP_DISABLE_PRIVILEGE_DROP=trueto return to the old behaviour. - Running fully as a non-root user is not backward compatible. You would need to migrate the data directory yourself.
- New accounts open the bookmark preview on click. Existing accounts keep their setting.
- Mobile app and browser extension updates depend on store reviews, so they may arrive a few days later.
Tested in our lab
Tested in our lab: an upgrade from 0.34.0 to 0.35.0 with the official Docker Compose setup (web, Chrome and Meilisearch containers).
- 0.34.0 installed and started healthy. We created an account, an API key, a text note and a link bookmark (example.com), which was crawled successfully.
- We stopped the stack with
docker compose stop, setKARAKEEP_VERSION=0.35.0, then randocker compose pullanddocker compose up -d. - After the upgrade the web container reported healthy on 0.35.0. Both bookmarks were still there, sign-in still worked, and a new link bookmark was created and crawled successfully.
- The logs showed no errors. They only had Better Auth warnings about our deliberately weak lab secret; the same warning type is not new to this release.
- We did not see the privilege-drop
WARNING: couldn't ...message. The web container’s main command still ran as root when we checked withdocker compose exec web id, and/datawas owned by root. That check only shows the user of a new exec session, so we can’t say what the server process ran as.
Not tested: the redesigned UI (we only used the API), the mobile app, the browser extension, the remote sandbox option, AI features, and the security fixes themselves.
Lab log
$ docker compose ps --format "{{.Name}} {{.Image}} {{.Status}}"
karakeep-app-chrome-1 ghcr.io/karakeep-app/karakeep-chrome:release Up 23 seconds
karakeep-app-meilisearch-1 getmeili/meilisearch:v1.55.0 Up 23 seconds
karakeep-app-web-1 ghcr.io/karakeep-app/karakeep:0.34.0 Up 23 seconds (healthy)
$ docker compose stop
[...]
Container karakeep-app-web-1 Stopped
$ sed -i "s/^KARAKEEP_VERSION=.*/KARAKEEP_VERSION=0.35.0/" .env
$ docker compose pull
[...]
Image ghcr.io/karakeep-app/karakeep:0.35.0 Pulled
$ docker compose up -d
[...]
Container karakeep-app-web-1 Started
$ docker compose ps --format "{{.Name}} {{.Image}} {{.Status}}"
karakeep-app-chrome-1 ghcr.io/karakeep-app/karakeep-chrome:release Up 34 seconds
karakeep-app-meilisearch-1 getmeili/meilisearch:v1.55.0 Up 33 seconds
karakeep-app-web-1 ghcr.io/karakeep-app/karakeep:0.35.0 Up 34 seconds (healthy)
$ curl -s localhost:3000/api/v1/bookmarks -H "Authorization: Bearer [redacted]" | grep -oE "\"(title|type|url)\":\"[^\"]*\"" | head
"type":"link"
"url":"https://example.com/"
"title":"Example Domain"
"title":"Lab note"
"type":"text"
Reported by others
Reported in the release notes, not tested by us:
- Security fixes include a path traversal in avatar cleanup (rated High, GHSA-qh82-x2c9-f2x7), webhook tokens leaking on cross-origin redirects, rate limits that trusted client-supplied IPs, an open redirect on
/signup, an SSRF guard gap for NAT64 addresses, and several shared-list privacy leaks. - The Docker images include Node.js 24.22.3 with the November 2026 security release.
- Smaller fixes: search (
android-style words,before:,-age:), large PDFs freezing workers, OCR and Ollama timeouts, lighter exports. - An experimental remote sandbox for untrusted content handling is included but not documented yet.
Verdict
Upgrade now. The upgrade path was uneventful in our test and the security fixes are worth having, especially if your instance is exposed to the internet or shared with other users. Back up your data directory first, and keep KARAKEEP_DISABLE_PRIVILEGE_DROP=true in mind if you hit permission errors.
sources
other Karakeep releases
- 0.34.1 upgrade now