A vulnerability in Kibana Observability onboarding allows an authenticated user with onboarding privileges to obtain credentials embedded in Elasticsearch host URLs. These credentials belong to the Kibana service account and can be used to access Elasticsearch with elevated privileges beyond those granted to the user. This issue affects certain versions of the ELK stack and has been fixed in later releases.
A resource allocation vulnerability in Elasticsearch's analysis-phonetic plugin can cause denial of service by exhausting heap memory. Authenticated users with write or search permissions on affected indexes can trigger this by submitting crafted input values. The issue affects multiple Elasticsearch versions prior to fixed releases 8.19.24, 9.4.9, and 9.5.6.
CVE-2026-115292 is an authorization bypass vulnerability in Kibana Machine Learning that allows an authenticated user with read access in one Kibana space to access audit and error messages of data frame analytics jobs in other unauthorized spaces. These messages may reveal sensitive job details such as destination index names, analyzed field names, and failure information. The issue is fixed in versions 8.19.24, 9.4.9, and 9.5.6.
A vulnerability in Elasticsearch allows information disclosure due to the use of cache containing sensitive information. Specifically, cached query results can be shared between users with different field-level security restrictions, enabling restricted users to infer data they should not access and causing incomplete search results for users with full access. This issue affects certain versions of Elasticsearch and has been fixed in later releases.
A vulnerability in Elasticsearch allows authenticated users with field-level security restrictions to access constant_keyword fields that their roles exclude. This occurs because some search and query features do not enforce field-level security on this field type, leading to potential information disclosure.
CVE-2026-115290 is a vulnerability in Elasticsearch involving uncontrolled recursion that can cause denial of service. An unauthenticated attacker with network access to a node's cluster server interface can send a crafted request with nested serialized data payloads, causing the node to terminate. This attack can be repeated against each reachable node in the cluster. The issue affects multiple Elasticsearch versions prior to fixed releases. A patch is available to address this vulnerability.
A thread-safety vulnerability in the mod_http2 module of Apache HTTP Server versions 2.4.55 through 2.4.70 allows remote attackers to execute arbitrary code without authentication. The flaw arises from improper synchronization when handling concurrent HTTP/2 requests, leading to heap corruption. Only servers with HTTP/2 enabled are affected. A fix is available in version 2.4.71.
HashiCorp Consul and Consul Enterprise contain an authorization bypass vulnerability in health check registration. This flaw allows an authenticated user to modify health checks of another service on the same node. The issue affects versions from 0.7.2 up to but not including 2.1.0. The vulnerability is fixed in Consul Community Edition 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19. No public exploit or in-the-wild exploitation has been reported. The severity is assessed as medium based on the impact described.
HashiCorp Consul and Consul Enterprise versions 1.17.0 up to but not including 2.1.0 contain an authorization bypass vulnerability in the agent's service mesh leaf certificate API. This flaw may allow an attacker without a valid ACL token to retrieve a cached service leaf certificate and its private key. The vulnerability is fixed in Consul Community Edition 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19.
HashiCorp Consul and Consul Enterprise have a denial of service vulnerability in their HTTP API that allows an unauthenticated attacker to exhaust memory on a Consul agent. This issue is fixed in Consul Community Edition 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19.
HashiCorp Consul and Consul Enterprise have an authorization bypass vulnerability in service mesh proxy registration that allows a user with service write permission to apply Envoy escape-hatch configuration without needing mesh write permission. This flaw is fixed in Consul Community Edition 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19.
Cybercriminals are exploiting a recent Microsoft 365 global outage by sending phishing emails to corporate users. These emails claim that Outlook and other Microsoft services are disconnected and urge recipients to reconnect their accounts via a link leading to a phishing site. The phishing site mimics the Microsoft login page and attempts to steal credentials or connect unauthorized devices to victims' accounts using a device code phishing technique.
Apache ActiveMQ and Apache ActiveMQ Runtime Config contain a vulnerability where cached authorizations are not properly invalidated. This allows an authenticated connection established before a revocation of write permissions to continue sending messages to a destination, even after the write grant is removed. New connections and explicit producers are correctly denied access. The issue affects versions from 6.0.0 before 6.3.3 and before 5.19.12. Upgrading to versions 6.3.3, 6.4.0, or 5.19.12 resolves the issue.
Apache ActiveMQ and its KahaDB persistence store have a vulnerability where creating a durable subscription with a combined clientId and subscription name length exceeding 65,535 characters can cause the broker to shut down and become unrecoverable. This improper input validation affects versions before 6.3.3 and 5.19.12. Upgrading to versions 6.3.3, 6.4.0, or 5.19.12 resolves the issue.
Apache ActiveMQ Broker contains a denial of service vulnerability due to a memory leak caused by repeated rejected temporary destination consumer requests. An authenticated OpenWire client sending ConsumerInfo for a temporary queue/topic owned by another connection triggers an InvalidDestinationException, but the broker fails to clean up the rejected subscription, leading to heap exhaustion and potential out-of-memory conditions. This affects ActiveMQ versions from 6.0.0 before 6.3.3 and versions before 5.19.12. The issue is fixed in versions 6.3.3 and 5.19.12.
Apache ActiveMQ versions from 6.0.0 before 6.3.3 and before 5.19.12 contain an improper input validation vulnerability. The broker does not verify that user-provided connection IDs match the authenticated user, allowing authenticated clients to spoof other users' connection, session, and consumer IDs. This enables unauthorized consumption from another user's temporary queues or topics, disruption of live subscriptions by tearing them down, and permanent deletion of unacknowledged messages via forged acknowledgments. The issue is fixed in versions 6.3.3 and 5.19.12.
Apache ActiveMQ contains an input validation vulnerability in the LDAPAuthorizationMapPlugin that allows an authenticated attacker to bypass authorization by injecting LDAP DN special characters into destination names. This manipulation affects the LDAP search base used for access control list lookups. The issue affects versions 5.19.0 through 5.19.11 and 6.3.0 through 6.3.2. Fixed versions are 5.19.12 and 6.3.3 or later.
A vulnerability in aiohttp's WebSocket implementation allows attackers to bypass receive queue limits by sending many small or compressed messages. This can cause excessive memory consumption on the server or client side when messages are processed faster than the application consumes them. The issue arises because empty messages are not counted towards the queue size and compressed frames can decompress into large amounts of data. A patch is available to address this issue.
AIOHTTP suffers from a vulnerability where decompressing payloads with many concatenated compressed members causes excessive CPU usage due to quadratic time complexity. This can block the event loop of a server or client when processing specially crafted compressed request bodies or WebSocket messages. The issue affects versions 1.2.1 and later. A patch is available to address this problem.
AIOHTTP versions 1.2.1 and later have a vulnerability where data received during an HTTP upgrade request (such as a WebSocket handshake) is buffered without any size limit or flow control until the upgrade handler completes. This can lead to unbounded memory consumption if an attacker streams large amounts of data behind the upgrade request to a handler that does not promptly accept or reject the upgrade.