October 19, 2026 — Linux kernel of our servers: updated, and how we restart
The Linux kernel is the part of a server that keeps one customer's code away from another's. Its security fixes install automatically on our servers, but a new kernel runs only after the server restarts.
On October 19, 2026 we restarted our servers so that all of them run the newest kernel our operating system has published a fix for.
A restart stops the databases and apps on that server for a few minutes, so we do not restart on a fixed schedule. We restart when a kernel flaw is urgent for the way we run customer code: an escape from a virtual machine, a container or a namespace, or a remote code execution over the network. In that case we restart without waiting for a maintenance window. Other kernel updates wait for the next planned maintenance.
October 14, 2026 — static-web-server (serves static sites): 2.44.0 → 2.44.1
On October 9, 2026, the static-web-server project published two advisories, fixed in 2.44.1: unbounded growth of the metrics labels (resource exhaustion), and a symbolic-link issue in the directory-listing archive feature that could disclose files outside the web root.
Neither feature is switched on in our configuration (we serve no metrics and no directory listings), so the advisories did not apply to how KoedoDB runs it. We updated anyway: on October 14, 2026 we moved to 2.44.1, re-ran our test suite for it (path traversal, hidden files, symbolic links, memory limits under load, shutdown), and copied the image into our own registry with its digest unchanged. A site is also unpacked by us into a directory it cannot leave, and only as plain files and folders, so a link in an uploaded archive is never served.
October 7, 2026 — Harbor (container registry): v2.15.2 → v2.15.3
On October 6, 2026, the Harbor project published a set of security advisories for versions up to 2.15.2, among them the handling of robot-account permissions, request forgery in webhook delivery, and a path-traversal issue in the registry endpoints. All are fixed in Harbor 2.15.3.
We updated our registry to 2.15.3 on October 7, 2026, the day after the advisories, and confirmed that every component was running the new version and was healthy.