Uptime Kuma 2.5.9: RSS cache poisoning fix, clean upgrade
Summary
Uptime Kuma 2.5.9 is a small maintenance release. It fixes an RSS cache poisoning problem (advisory GHSA-86ch-2247-gr56) and replaces the old apicache library with http-cache-semantics. It also updates dependencies and fixes four bugs: a timeout fallback that used milliseconds for a seconds field, push monitor retries, a duplicated refresh timer on status pages, and the time zone shown for recurring maintenance.
Breaking changes and deprecations
None listed in the release notes. We did not see any in our test.
Tested in our lab
We installed 2.5.8 with Docker, created an admin user and one HTTP monitor, then stopped the container cleanly and started 2.5.9 on the same data volume.
- 2.5.9 started and reported healthy after about 45 seconds.
- The login still worked with the same credentials.
- The monitor created on 2.5.8 was still there, and its heartbeat history was kept.
- The container logs showed no errors or warnings (we searched for “error” and “warn”).
We did not test the individual bug fixes or the RSS fix itself (push monitors, status page timers, recurring maintenance, RSS feeds). This only covers a basic upgrade.
Lab log
$ docker run -d --name uptime-kuma --restart=unless-stopped -p 3001:3001 -v uptime-kuma:/app/data -e UPTIME_KUMA_DB_TYPE=sqlite louislam/uptime-kuma:2.5.8
$ docker exec uptime-kuma grep "\"version\"" package.json
"version": "2.5.8",
[... created admin user and monitor "example" (https://example.com) through the socket API ...]
{"ok":true,"msg":"successAdded","msgi18n":true,"monitorID":1}
$ docker stop uptime-kuma && docker rm uptime-kuma && docker run -d --name uptime-kuma --restart=unless-stopped -p 3001:3001 -v uptime-kuma:/app/data -e UPTIME_KUMA_DB_TYPE=sqlite louislam/uptime-kuma:2.5.9
[...]
Status: Downloaded newer image for louislam/uptime-kuma:2.5.9
$ docker ps --format "{{.Image}} {{.Status}}"
louislam/uptime-kuma:2.5.9 Up 44 seconds (healthy)
$ docker exec uptime-kuma grep "\"version\"" package.json
"version": "2.5.9",
[... logged in again through the socket API and listed monitors ...]
monitor 1 example https://example.com
heartbeats 1 3 1
login true
$ docker logs uptime-kuma 2>&1 | grep -iE "error|warn" | head
The last command printed nothing.
Reported by others
The release notes list the changes above and credit the RSS fix to @the-arma-of-owl: 2.5.9 release notes. We did not read the advisory itself, so we can’t say how severe it is.
Verdict
Upgrade when convenient. It includes a security fix, the upgrade from 2.5.8 was uneventful in our test, and we found no reason to wait. Back up your data volume first, as always.