Uptime Kuma Launches Version 1.23.3

Uptime Kuma has released version 1.23.3 , bringing several bug fixes and security enhancements. This update includes important changes that users need to be aware of.

First and foremost, due to the security fix in this version, all login sessions will be logged out after updating. This is a necessary measure to ensure the security of the system. Users will need to log in again with their credentials to access the platform.

It is worth noting that if you are using any unofficial or third-party tools with Uptime Kuma, there is a possibility of breaking changes with this update. In such cases, it may be necessary to re-generate an authentication token to ensure seamless integration with these tools.

Now let’s take a closer look at the bug fixes included in this release:

• Fixed an issue where notifications were not working if the configuration was too long. This bug has been resolved thanks to the contribution of @FJBlok .
• Enabled the status page certificate expiry badge for all HTTP(s) monitors. This improvement was made possible by the work of @marvinruder .
• Addressed Kafka producer bugs, ensuring smoother operation of this feature. This fix was made possible by the contributions of @mhkarimi1383 .
• Fixed an issue with the incorrect usage of x-forwarded-host. This bug has been resolved thanks to the efforts of @xuexb .
• Resolved a race condition issue in the status page editor, ensuring that all data is saved correctly. This fix was made possible by the contribution of @chakflying .

In addition to these bug fixes, version 1.23.3 also includes security enhancements. One of the notable security fixes is the resolution of a persistent session tokens issue. Previously, there was no way to revoke session tokens even if the password was changed. With this update, users can now revoke session tokens by changing their password. For more information on this security fix, you can refer to the advisory GHSA-g9v2-wqcj-j99g .