ModSecurity versions from 3.0.5 up to but not including 3.0.17 have a vulnerability in the PCRE2 @rxGlobal implementation where match-limit errors are incorrectly treated as no-match results. This causes rules relying on match-limit exceeded indicators to be bypassed, potentially allowing malicious requests to pass through the WAF. The issue is fixed in version 3.0.17.
CVE-2026-115292 is an authorization bypass vulnerability in Kibana Machine Learning that allows an authenticated user with Machine Learning read access in one Kibana space to access audit and error messages of data frame analytics jobs in other unauthorized spaces. This can lead to information disclosure of job details such as destination index names, analyzed field names, and failure information. The issue affects multiple Kibana versions prior to fixed releases 8.19.24, 9.4.9, and 9.5.6.
A denial of service vulnerability in Grafana allows a user with Viewer role to crash the server by submitting a crafted server-side math expression that causes uncontrolled recursion. Users with permission to provision alert rules can cause the outage to persist across server restarts. The issue affects multiple Grafana versions prior to fixed releases in 12.4.14, 13.0.12, 13.1.9, and 13.2.5.
A vulnerability in Grafana OSS and Enterprise 13.2 allows an authenticated user to bypass authorization controls and read SSO client secrets as well as modify instance-wide SSO settings. This issue occurs only when the experimental kubernetesSsoSettingsApi feature toggle is enabled, which is disabled by default. The flaw is fixed in version 13.2.5.
Grafana contains an authorization bypass vulnerability (CVE-2026-100105) where users with permission to edit contact points but not their protected fields can exploit a schema downgrade to modify protected settings. This allows changing sensitive configurations such as destination URLs, potentially exposing stored credentials and redirecting alert notifications. The issue affects multiple versions prior to fixed releases in 12.4.14, 13.0.12, 13.1.9, and 13.2.5.
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.
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. The issue arises because the WebSocket reader continues parsing frames after the receive queue pauses the transport, and empty messages are not counted towards the queue size. A fix is available in version 5.14.0_18.
CVE-2026-128131 is a vulnerability in AIOHTTP where decompressing concatenated compressed streams (gzip, deflate, or zstd) causes excessive CPU usage due to quadratic time complexity in processing. This can block the event loop of a server or client when handling specially crafted compressed request bodies or WebSocket messages. The issue is fixed in version 5.14.0_18.
A vulnerability in AIOHTTP's pure-Python HTTP parser causes the request buffer to grow uncontrollably when an upgrade request is declined, leading to excessive memory use and repeated processing of pipelined requests. This affects users relying on the Python parser instead of the default C parser. The issue is fixed in version 5.14.0_18.
AIOHTTP versions from 5.14.0_13 up to but not including 5.14.0_18 have a vulnerability where data received during an upgrade request (such as a WebSocket handshake) is buffered without any size limit or flow control until the handler completes. This can lead to unbounded memory consumption if an attacker streams data behind the upgrade request to a handler that does not promptly accept or reject the upgrade. A patch is available in version 5.14.0_18 to address this issue.
AIOHTTP's WebSocket implementation contains an integer overflow vulnerability in the max_msg_size check within its C extension. This flaw allows an attacker to bypass the maximum message size restriction by sending a crafted WebSocket message with a declared length near 2^63, causing unbounded memory consumption. The vulnerability affects versions from 5.14.0_13 up to but not including 5.14.0_18. A fix is available in version 5.14.0_18. As a workaround, disabling the C extension by setting AIOHTTP_NO_EXTENSIONS=1 forces use of the unaffected Python reader.
A vulnerability in aiohttp's multipart handling allows bypassing the client_max_size limit when processing parts with Content-Transfer-Encoding: base64. This can cause excessive memory consumption or event loop blocking due to unbounded reading of multipart data. The issue affects versions from 5.14.0_13 up to but not including 5.14.0_18 and is fixed in version 5.14.0_18.
AIOHTTP's Request.post() method lacked a limit on the number of URL-encoded form fields, causing insertion of many repeated keys into a MultiDict to take quadratic time on the event loop. This flaw allows an attacker to block the event loop by sending a form POST within the default client_max_size to any handler using Request.post(). A fix is available in version 5.14.0_18.
AIOHTTP's client CookieJar had an issue where it would parse unrecognized name=value attributes in Set-Cookie headers as additional cookies without any limit on the number stored or sent. This allowed a malicious server to cause the client to store an excessive number of cookies, leading to very large Cookie headers and excessive memory and CPU usage, especially on repeated redirects. The vulnerability affects versions from 5.14.0_13 up to but not including 5.14.0_18 and has been fixed in version 5.14.0_18.