Most of the 8 CVEs are resource-exhaustion weaknesses in Elasticsearch. These are Uncontrolled Recursion, Uncontrolled Resource Consumption, Memory Allocation with Excessive Size Value, and Inefficient Regular Expression Complexity, found in scripted geometry runtime fields, the Connector API, and the ES|QL query engine and its CHUNK function. They let a low-privileged authenticated user crash a node or degrade it. Elasticsearch is also affected by an Authorization Bypass Through User-Controlled Key in cross-cluster search with the RCS 2.0 model, which can expose the contents of unauthorized indices. The remaining CVEs are an Incorrect Authorization in Kibana, which lets users with limited Fleet privileges get the SSL private keys of Fleet Server hosts, and an Uncaught Exception in Elastic Endpoint, which can repeatedly crash Elastic Defend on Windows hosts with CJK locales. Together, these CVEs can lead to unauthorized information disclosure, credential exposure, or denial of service.
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
Social login provider icons are displayed correctly again We fixed an issue on the NetEye login page where icons of social login providers (identity providers configured in Keycloak) were rendered at the wrong size after the update to Keycloak 26.8. Read More