Skip to content

~95% on SimpleQA (e.g. Qwen3.6-27B on a 3090). Supports all local and cloud LLMs (llama.cpp, Ollama, Google, ...). 10+ search engines - arXiv, PubMed, your private documents. Everything Local & Encrypted.

1.5 KB
Raw Blame

🔒 Security

  • Login now verifies your password even when your encrypted database is already open. The connection cache is keyed by username alone, so a cache hit proved only that someone had already opened that user's database — and login's sole credential check is whether that open succeeds.

    This only affected an account that already existed and was currently open — the normal state while that user is signed in anywhere. It could not be used to sign in to an account that does not exist or that has never been opened, and the attacker needed no account of their own. The exposure also outlives an active browser session: the database stays open after the user closes the browser (until the idle timeout — up to 30 days with "remember me") and while a research job is running. For any account meeting that condition, knowing only the username — not the password — was enough to sign in as that user from a different session, browser, or IP and read (and write) their data. The attempt also counted as a successful login, so it never tripped the account lockout or the rate limiter and left nothing in the logs that looked like an attack.

    The cache now records which password opened the connection and re-checks it on every login, falling back to a real key-validating open when it does not match.

🐛 Bug Fixes

  • Preserve commas inside Apprise service URLs while refusing configurations that contain scheme-less URL fragments. (#5394)