~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.
Python academiaanthropicarxivbravedeep-researchencryptionhome-automationhomeserverlocallocal-deep-researchlocal-llmmistralollamaopenaipubmedresearchresearch-toolretrieval-augmented-generationsearxngself-hosted
docs(changelog): add the missing fragment for the socket subscription fix (#5838)
LearningCircuit8a2f66381ec4
diff --git a/changelog.d/5520.security.md b/changelog.d/5520.security.mdnew file mode 100644index 0000000000..6418bbafac--- /dev/null+++ b/changelog.d/5520.security.md@@ -0,0 +1,9 @@+Benchmark progress is no longer delivered to the wrong user's browser. Socket.IO+subscriptions were held in a process-global map keyed by the research id alone,+but `BenchmarkRun.id` is a **per-user** autoincrement integer — so two users who+each own a benchmark run with the same id (both have run 1) were filed under the+same subscriber set, and each user's browser received the other's+`research_progress_<id>` events: live queries, partial results, rate-limit+warnings. Subscriptions are now keyed by `(username, run id)` for numeric+benchmark ids, matching the same fix applied to the benchmark run registry.+Ordinary research is unaffected — those ids are UUIDs and cannot collide.