Checkmk 2.5.0p20: Security fix silently breaks existing notifications

Checkmk 2.5.0p20: Security fix silently breaks existing notifications

After upgrading Checkmk Community from 2.5.0p19 to 2.5.0p20 on November 16, I noticed that email notifications were no longer being sent.

The notification log showed:

Global rule 'Notify all contacts of a host/service via HTML email'...
 -> matches!
User tkuhlmann's rule 'Notify all contacts of a host/service via HTML email'...
 -> does not match: User [redacted] is not a contact of this host or service
1 rules matched, but no notification has been created.

After investigating, I discovered that this behavior is caused by Werk #22556, which changes how personal notification rules are evaluated.

Previously, my personal notification rule successfully delivered notifications for all monitored hosts and services without requiring explicit membership in the Everything contact group.

Since 2.5.0p20, this no longer works. Adding my user to Everything appears to be the appropriate solution.

I understand the security implications and the reason for restricting personal notification rules to hosts and services for which the user is an actual contact.

However, I see three problems here:

  1. Existing notification configurations can silently stop working after an update. In a monitoring system, losing notifications is particularly critical.

  2. Checkmk reports no failed notifications. The notification overview still shows zero failures, although no notification is generated.

  3. The change was not apparent to me in the Changed Werks list when preparing the update. Werk #22556 is marked as incompatible and requiring possible manual intervention. Such a change should be particularly prominent.

My suggestion would be to introduce an upgrade warning or a configuration check that identifies personal notification rules potentially affected by this change.

Security fixes are important, of course. But a security fix that silently disables alert delivery introduces a different operational risk.

Has anyone else encountered this after upgrading to 2.5.0p20?

That’s exactly what has been fixed.

That’s the intended behavior. This is also how it is covered in the User Guide.

I brought this up to the security team: In such cases, the release announcement probably should state that some users might accidentally rely on the unintended behavior and keep an eye on notifications after updating.