We fixed a bug in Tornado that caused Smart Monitoring Actions to fail to correctly set statuses on Icinga 2 objects during a restart of Icinga 2 and during Icinga Director deployments, due to a race condition in Icinga 2.
We also fixed a bug in the Tornado Smart Monitoring Actions that could cause to process the check results in Icinga 2 in the wrong order. I.e., older Events could overwrite the status set by newer Events.
For NetEye 4.22 we updated the following packages:
tornado, tornado-autosetup, tornado-common, tornado-dto, tornado-neteye-config to version 1.18.6-1
icingaweb2-module-director, icingaweb2-module-director-autosetup to version 1.8.1_neteye1.26.1-1
icinga2, icinga2-autosetup, icinga2-bin, icinga2-ido-mysql, icinga2-neteye-config, icinga2-resources, icinga2-common, icinga2-selinux to version 2.11.9_neteye1.48.2-1
icingaweb2-module-tornadocarbon, icingaweb2-module-tornadocarbon-autosetup to version 1.25.1-1
Important: Keycloak security update Type/Severity NetEye Product Security has rated this update as having a CRITICAL security impact. Topic An update for the keycloak packages is now available for NetEye 4. Security Fix for NetEye 4.50: 26.8.2_neteye1.47.5 Security Fixes CVE-2026-114938 A memory Read More
Alyvix Server-side Error We fixed an issue in Alyvix Service caused by a critical typo on the server side. Updating will prevent future communication problems between Alyvix Service and NetEye. List of updated packages To solve the issue mentioned above, Read More
Disclaimer: The security issues below do not yet have publicly disclosed CVE identifiers, so details regarding their severity, impact, and potential attack vectors are not fully available at this time. This post will be updated as soon as additional information Read More
Bug fix: Elasticsearch nodes can crash On Elasticsearch 9.5.6, Elasticsearch nodes could crash at random times. The cause was a kernel setting that was too low: vm.max_map_count. Elasticsearch memory-maps many files. When the number of memory maps reached the limit, Read More
Disclaimer: The CVEs referenced below have not yet been publicly disclosed, so details regarding their severity, impact, and potential attack vectors are not available at this time. This post will be updated as soon as additional information becomes publicly available. Read More