For a detailed overview of the security issues, including the impact, CVSS score, acknowledgments, and other relevant information, please refer to the links provided in the references section.
For details on how to apply this update, which includes the changes described in this advisory, refer to the NetEye Update Section in the User Guide.
Full Stack Developer at Wuerth Phoenix. I love questioning myself, find new challenges to learn and new adventures to grow up. PHP lover trying to expand my skills studying new languages and tools to improve my professional life.
Author
Gianluca Piccolo
Full Stack Developer at Wuerth Phoenix. I love questioning myself, find new challenges to learn and new adventures to grow up. PHP lover trying to expand my skills studying new languages and tools to improve my professional life.
Important: GLPI security update Type/Severity NetEye Product Security has rated this update as having a high security impact. Topic An update for the GLPI packages is now available for NetEye 4. Security Fix for NetEye 4.46 10.0.23_neteye1.17.5-1 CVEs CVE-2026-22044CVSS:Reserved CVE-2026-23624CVSS:Reserved The CVEs include Read More
Fix unnecessary action retries in Tornado's Smart Monitoring component We fixed a bug affecting Tornado in NetEye 4.45 for a specific edge case in Tornado's Smart Monitoring component that was causing unnecessary system overhead and log bloat. Specifically, when Tornado Read More
Fix contract list option wrongly disabled in SLM reports We fixed a bug affecting the SLM reporting in NetEye 4.45. The issue occurred during the modification of a report, when one of the contracts in the list could not be Read More
Bug Fix We updated the version of GLPI in order to fix some relevant vulnerabilities. List of updated packages The following packages have been updated for NetEye 4.45: glpi, glpi-autosetup, glpi-configurator, glpi-neteye-config to version 10.0.22_neteye1.17.5-1.
Bug Fix in Tornado Module We solved an issue in Tornado's rule configuration where the action_name field in director actions was being cleared after saving and deploying. When users created a rule with a director action and filled in both Read More
