kibana is an open source (Apache Licensed), browser-based analytics and search dashboard for Elasticsearch.

Affected versions of this package are vulnerable to Incorrect Authorization in the Fleet. An attacker can gain unauthorized access to manage integration policies for different integrations by updating an existing integration policy, as the restriction is evaluated against the stored policy's integration rather than the replacement integration provided during the update. This allows an authenticated user with limited privileges to escalate their access by converting an endpoint policy they control into a policy for another integration and supplying its configuration.

agno is an Agno: a lightweight library for building Multi-Agent Systems

Affected versions of this package are vulnerable to Directory Traversal through the read_file, save_to_file, and run_python_file actions. An attacker can read, write, or execute arbitrary files by supplying a file_name with parent-directory traversal sequences such as ../../../../../../etc/passwd, escaping the intended base_dir and causing the tool to operate on attacker-chosen paths. This lets a remote caller or prompt-injected agent gain access to sensitive files, overwrite files, or run arbitrary Python code under the process user's privileges.

io.netty:netty-handler is a library that provides an asynchronous event-driven network application framework and tools for rapid development of maintainable high performance and high scalability protocol servers and clients. In other words, Netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients. It greatly simplifies and streamlines network programming such as TCP and UDP socket server.

Affected versions of this package are vulnerable to Improper Check for Unusual or Exceptional Conditions through the SslClientHelloHandler.decode ClientHello parser in handler/src/main/java/io/netty/handler/ssl/SslClientHelloHandler.java. An attacker can bypass per-SNI mTLS selection by sending a fragmented TLS ClientHello whose 4-byte handshake header spans multiple records, causing parsing to fail and the connection to fall back to the default SslContext. This breaks deployments that rely on SNI-driven SslContext selection as the only client-certificate check: the request reaches the default TLS configuration instead of the intended SNI-specific context, allowing an unauthenticated client to complete a connection where mTLS was expected.