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.
Update: The CVEs referenced below have now been publicly disclosed, and additional details have been added to this post.
Important: Grafana security update
Type/Severity
NetEye Product Security has rated this update as having a High security impact.
Topic
Updates for the grafana packages are now available for NetEye 4.
Two of the three CVEs affect low-privileged authenticated users. The first vulnerability allows a user who can edit alert notification contact points (but not their protected fields) to bypass authorization by switching an integration to a legacy schema version, changing protected settings such as the destination URL. The second CVE allows a Viewer to crash the Grafana server with a crafted server-side math expression (uncontrolled recursion), with users permitted to provision alert rules able to make the outage persist across restarts. The third CVE is a server-side request forgery in the Azure Monitor data source: a user with query access can make Grafana send requests to an attacker-controlled endpoint that discloses the data source’s Azure access token. Together these vulnerabilities can lead to credential exposure, alert hijacking, a persistent Grafana outage, or Azure token disclosure where Azure Monitor data sources are used.
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