Self-hosters spent the weekend talking about a bookmark manager's security release. The verified substance: Karakeep 0.35.0 shipped November 15 with fixes for seven security advisories, a Docker image rebuilt on the patched Node.js 24.22.3, and a 30,000-star milestone for the project.
Key facts
- A high-severity path traversal in avatar cleanup let a logged-in user delete files outside their asset directory, including other users' assets and the SQLite database (fixed in 0.35.0).
- Rate limits no longer trust client-supplied IPs: authenticated requests are keyed by user, and sign-in and password reset are limited per email (GHSA-cv6g-rxx2-rxhr).
- The Docker images include the November 2026 Node.js security release, which carried seven high-severity fixes.
- The release crossed 30,000 GitHub stars, and drew sustained discussion on r/selfhosted.
What's driving the conversation
The traction is on Reddit and Hacker News rather than X this time. The maintainer, MohamedBassem, titled the release "security and polish" and wrote plainly that the team runs Karakeep in production themselves, so its security is a personal priority. That framing, a maintainer treating his own tool as attack surface, is what r/selfhosted readers latched onto.
The substance
Karakeep ingests untrusted web content by design: it fetches, archives, and AI-tags arbitrary pages, which makes it a realistic target in the self-hosted stack. The release notes walk through the October incidents in detail, and every fix links its advisory: the path traversal (GHSA-qh82-x2c9-f2x7), webhook bearer tokens leaking on redirect (GHSA-chpj-828m-9wj6), IP-trusting rate limits, highlight-note exposure to list collaborators, and an open redirect on the signup route.
One process detail worth noting: the fixes are credited to named external reporters with advisories published per issue, which is the disclosure pattern security teams ask for and small projects rarely execute this cleanly. We make no judgment on the project's overall security posture beyond what the advisories document.
Why builders are watching
Self-hosted AI tooling keeps generating incident reports: an exposed-endpoint sweep in Mysterium Node 36.7.69, the LiteLLM 1.10.70 supply-chain compromise, and the Poellm botnet targeting self-hosted AI stacks. Anything in that stack that fetches untrusted content and hands it to a model is attack surface. Karakeep's response, patch fast, publish advisories with reporter credit, ship the patched runtime in the same image, is the pattern to compare other projects against the next time one goes quiet.
Questions
- What is Karakeep?
- An open-source, self-hosted bookmark manager that archives links, notes, and files, and applies AI-generated tagging and summaries to saved content. It runs as a Docker container that users host themselves.
- What security issues did Karakeep 0.35 fix?
- Seven GitHub security advisories, including a high-severity path traversal in avatar cleanup that let a logged-in user delete files outside their asset directory, plus webhook token leakage, client-IP-trusting rate limits, and shared-list information exposure.
Sources
About DeAI
DeAI is an independent publication covering open-weight AI models, private inference, and decentralized infrastructure — the tools for running AI you actually control. We test providers on price, privacy, and refusal behavior and publish the numbers, not the vibes. DeAI is powered by Morpheus (mor.org), a decentralized inference marketplace, and covers it on the same terms as every other provider.
Powered by Morpheus and StrandCMS
Morpheus is a decentralized inference marketplace, covered on the same terms as every other provider — we rank it wherever the data lands. StrandCMS is the open-source, agent-first framework this site is built on.
