Logstash shares the two eMudhra trust-store CVEs listed under Elasticsearch (CVE-2026-91403, CVE-2026-114820) through its bundled Java runtime.
The most severe of the 12 unique CVEs is an Out-of-bounds Write in the Node.js Brotli decoder bundled with Kibana, which can lead to remote code execution when Kibana receives a crafted compressed response from an attacker-controlled upstream. Three further CVEs are Improper Certificate Validation issues caused by the compromised eMudhra (emSign) root certificates shipped in the Java runtime bundled with Elasticsearch and Logstash, and the Node.js runtime bundled with Kibana; they allow a man-in-the-middle attacker to intercept or modify TLS-protected traffic with forged certificates. Elasticsearch is also affected by an Uncontrolled Recursion in the Remote Cluster Server interface, which an unauthenticated attacker can use to crash nodes, an Allocation of Resources Without Limits or Throttling in the phonetic analysis plugin that exhausts node heap memory, an Incorrect Authorization that fails to apply field-level security to constant_keyword fields, and a Use of Cache Containing Sensitive Information that leaks query results across users with different field-level security restrictions. Kibana additionally suffers a Path Traversal in Fleet that lets a low-privileged user trigger unauthorized deletion of resources, two Authorization Bypass Through User-Controlled Key issues that expose Machine Learning job details and connector execution logs across spaces, and an Insertion of Sensitive Information Into Sent Data in Observability onboarding that can disclose the Elasticsearch credentials used by Kibana. Together, these CVEs can lead to remote code execution, TLS traffic interception, unauthorized information and credential disclosure, or denial of service.
Update: Elastic Stack v9.5.6 also includes important security fixes. You can find more details here. Update of Elastic Stack to Version 9.5.6 Elastic Stack 9.5.6 is a maintenance release that brings a large set of stability, correctness and hardening fixes 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
Disclaimer: The security issues referenced below do not yet have publicly disclosed CVE identifiers, so they are referenced by GHSA ID. This post will be updated as soon as CVEs become available. Important: Icinga 2 security update Type/Severity NetEye Product 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
Asset Management: GLPI agent inventory submissions through satellites now work with the glpiinventory plugin On NetEye satellites, nginx proxies GLPI inventory submissions from agents to the GLPI instance running on the master. Until now, the proxy covered only one endpoint, Read More