WordPress Core versions 4.7.0 through 7.1.3 contain a remote code execution vulnerability due to predictable, web-accessible staging paths during full-package core upgrades. This flaw allows unauthenticated attackers to execute code on the server during the upgrade window. Multiple versions prior to fixed releases are affected. The issue has been addressed in versions 5.7.21, 5.8.19, 5.9.20, 6.0.18, 6.1.16, 6.2.15, 6.3.14, 6.4.14, 6.5.14, and 6.6.11.
A regression in FIPS enforcement for hash algorithms in Python's hashlib module affects only Python version 3.14.10 when used with OpenSSL in FIPS mode. This issue does not impact other Python versions. A fix is available in Python 3.14.11.
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.
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 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.
The AIOHTTP library's Application.add_domain() method had a performance issue where domain masks with two or more wildcards caused polynomial-time matching delays when processing long Host headers. This could be exploited by an attacker to stall the event loop of a server using such domain masks. A patch is available in version 5.14.0_18 that fixes this issue. Until patched, limiting domain masks to at most one wildcard serves as a workaround.
A vulnerability in OpenSSL's QUIC server implementation allows a remote client to cause unbounded memory growth by repeatedly opening and resetting streams. This occurs because the server retains stream state for rejected streams if the peer resets the stream before the rejection is signaled, preventing proper cleanup. The issue leads to a denial of service by exhausting server memory over time. The severity is rated high due to the potential for service disruption, though the memory growth is slow and requires a long-lived connection.
A use-after-free vulnerability exists in OpenSSL's PEM_X509_INFO_read_bio_ex() and related functions when an application passes an existing stack to add entries. If reading PEM data fails, the function frees all entries in the stack but leaves dangling pointers, potentially causing crashes or memory corruption if the application continues to use the stack. This affects only applications that pass a non-NULL stack, which OpenSSL itself does not do. The vulnerability is triggered by malformed PEM data causing read failure.
A vulnerability in OpenSSL occurs when a server is configured with the Suite B certificate flag via SSL_CTX_set_cert_flags() and TLS 1.3 is enabled. The server may read past the end of a fixed group list during ClientHello processing if the client's supported_groups and key_share contain no Suite B group. This out-of-bounds read does not disclose memory but can cause a denial of service on builds with sanitizers or hardened allocators.