Uptime Kuma 2.5.11 upgrade: admin-only RCE fix, no breaking changes

released
lab run
upgraded from
2.5.10
guest
Ubuntu 26.04 VM
tested
yes, in our lab

Summary

2.5.11 is a security release. The release notes list two items: a dependency update (#8094) and a fix for GHSA-437w-j82f-9vjh, described as an admin-only remote code execution caused by a regression in an upstream package. The notes say details will be revealed after 7 days.

Breaking changes and deprecations

None listed in the release notes. We saw none in our test.

Tested in our lab

We ran Uptime Kuma 2.5.10 in Docker (louislam/uptime-kuma:2.5.10) with a named volume, completed the first-run SQLite setup, created an admin user and one HTTP monitor. We then stopped the container with docker stop, removed it, and started louislam/uptime-kuma:2.5.11 on the same volume.

  • The container came up healthy and the web UI answered (HTTP 302 redirect on /).
  • The log reports Uptime Kuma Version: 2.5.11.
  • The admin login worked and the monitor was still there.
  • Heartbeat rows grew from 1 to 2 after the upgrade, so checks kept running.
  • No errors or warnings appeared in the startup log (filtered for “error” and “warn”).

We did not test the vulnerability itself or the fix. We only used one monitor, no notifications, and a short run. We assumed 2.5.10 was the previous version because the image tag exists. We did not check the release history.

Lab log

$ docker run -d --name kuma -p 3001:3001 -v kuma-data:/app/data louislam/uptime-kuma:2.5.10
$ docker stop kuma
kuma
$ docker rm kuma
kuma
$ docker pull louislam/uptime-kuma:2.5.11
[...]
docker.io/louislam/uptime-kuma:2.5.11
$ docker run -d --name kuma -p 3001:3001 -v kuma-data:/app/data louislam/uptime-kuma:2.5.11
$ docker ps --format "{{.Names}} {{.Image}} {{.Status}}"
kuma louislam/uptime-kuma:2.5.11 Up 45 seconds (healthy)
$ curl -s -o /dev/null -w "%{http_code}\n" http://localhost:3001/
302
$ docker logs kuma 2>&1 | grep -iE "version|error|warn"
Your Node.js version: 22.23.5
[...] [SERVER] INFO: Uptime Kuma Version: 2.5.11
monitors labmon https://example.com
login true

Reported by others

Nothing beyond the release notes. The advisory GHSA-437w-j82f-9vjh had no public details when the release was published.

Verdict

Upgrade now. The fix targets remote code execution by an admin, so it matters most if you share admin access or expose the UI. Back up your data volume, stop the container cleanly, then pull the new image and start it again.

sources

other Uptime Kuma releases