CVE-2026-28273 is a critical vulnerability in ZoneMinder, an open source closed-circuit television software. The vulnerability has a CVSS score of 9.9, indicating a high severity with network attack vector, low attack complexity, and no user interaction required. It impacts multiple specific versions of ZoneMinder as listed. No public exploit or vendor patch information is provided in the data.
CVE-2024-43361 is a medium severity vulnerability in ZoneMinder, an open source closed-circuit television software. The vulnerability has a CVSS 3.1 base score of 6.5, indicating it can be exploited remotely without privileges or user interaction, resulting in limited confidentiality loss and low impact on availability. Multiple specific versions of ZoneMinder are affected. No public exploits or vendor patch information are provided.
Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary.
Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack. Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this. CWE: CWE-416: Use After Free Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged. If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack. An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory. Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack. The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions. FIPS impact: no The affected code is outside the FIPS module boundary.
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.
A high severity security vulnerability (CVE-2026-129246) affecting multiple versions of LightDM has been published. The vulnerability has a CVSS 3.1 score of 7.8, indicating high impact on confidentiality, integrity, and availability. It affects specific Ubuntu package versions of LightDM ranging from 1.16.4-0ubuntu1 through 1.25.2-0ubuntu1. No public exploits or known active exploitation have been reported. The vulnerability requires local access with low privileges and does not require user interaction. The attack vector is local, and the vulnerability is not related to cloud services.
A vulnerability in DOMPurify when configured with SAFE_FOR_TEMPLATES and a DOM-returning mode allows template expressions split across text nodes in attached shadow roots to survive sanitization. This occurs because the post-walk safety net does not recurse into shadow roots, enabling attackers who supply DOM nodes with shadow roots to inject expressions that are later evaluated by template engines. Exploitation requires specific non-default configurations and attacker control over DOM nodes with attached shadow roots. The vulnerability is fixed in version 3.4.17.
DOMPurify versions prior to 3.4.17 have a vulnerability in the IN_PLACE sanitization mode where hooks that remove a parent or sibling node leave detached subtrees with active event handlers unneutralized. This allows event handlers such as <img onerror> to fire after sanitize() returns, potentially leading to DOM-based XSS. The issue arises because the sanitization process only neutralizes the node directly removed by the hook, not other detached nodes like parents or siblings. This behavior breaks the expected guarantee that detached subtrees are neutralized inline in IN_PLACE mode.
An off-by-one error in the BSON bulk document writer in the MongoDB C Driver can write one zero byte immediately past a heap allocation when a document ends at a specific buffer boundary. An actor who can influence the size of documents serialized by an embedding application can corrupt adjacent process memory or terminate the process. Reaching this issue requires the application to use the BSON bulk-writer API and produce a precise cumulative document size.