CVE Vulnerability Catalog

The OpenSSL QUIC stack does not enforce connection-level flow control for streams. A malicious remote peer can send more bytes as long as they fit within stream flow control limits, leading to excessive memory allocation.

A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap, potentially leading to a Denial of Service.

OpenSSL's optimized scalar point multiplication implementation for SM2 private key operations on ARM64 and RISC-V platforms is not constant-time. Conditional branches and table lookups depend on the bits of the secret scalar, so execution time and cache-access patterns leak information about the private key or signature nonce.

A vulnerability in the QUIC implementation in OpenSSL allows a remote attacker to keep allocated packet buffer memory for an extended period by sending specially crafted packets. The issue stems from missing resource allocation limits (CWE-770), potentially leading to excessive memory consumption.

The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves lacking a dedicated implementation leaks information about the secret nonce through timing. An attacker measuring signing times may learn the nonce, which over many signatures can lead to private key recovery.

The QUIC stream reassembly algorithm in OpenSSL degrades progressively as packets arrive out of order, with worst-case quadratic complexity. A remote QUIC peer that completes the handshake can cause CPU pressure and potential DoS with low bandwidth.

The OpenSSL QUIC server, when address validation is disabled, can count incoming datagrams multiple times in its unvalidated credit computation. This violates the RFC 9000 3x amplification limit, allowing a remote attacker to use the server for DDoS amplification.

A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service.

Improper path validation in the local IPC service of TeamViewer Full Client and Host on Windows, Linux, and macOS prior to version 15.82 allows a local authenticated user with low privileges to perform arbitrary file writes with elevated privileges (NT AUTHORITY/SYSTEM \ root). By sending crafted IPC commands to the local service daemon, an attacker could manipulate file paths, leading to local privilege escalation.

UnoPim versions before 2.0.1 and 2.1.1 trust all connecting clients as proxies and honor the X-Forwarded-Host header without validation, allowing unauthenticated attackers to inject arbitrary origins into admin layout pages. Attackers can set X-Forwarded-Host to redirect JavaScript asset loading to their server, and when responses are cached by shared proxies, subsequent administrators execute attacker-supplied code in their authenticated sessions.

Flysystem prior to 3.35.3 has a vulnerability in the default WhitespacePathNormalizer that calls preg_match with the u modifier and treats both false and 0 as falsy. A path containing malformed UTF-8 causes PCRE to return false, allowing paths with control characters to bypass validation. This can lead to hidden or spoofed terminal file listings when an administrator displays them.

Prior to version 0.1.1, @socket.io/cluster-engine uses inherited object properties when looking up attacker-controlled session IDs in clustered deployments. Special property names such as __proto__ or constructor can resolve through the object prototype chain instead of identifying an actual connected client, causing the Node.js process to crash and resulting in denial of service. Applications that do not use @socket.io/cluster-engine are not affected.

In Werkzeug before 3.1.9, the safe_join function used by send_from_directory can allow a NUL: special-device path because safe_join checks the Windows device name without first removing an empty NTFS ADS marker. The trigger is an application running on Windows with NTFS serving a user-specified path ending in a special device name such as NUL:.

Deserialization of untrusted data in the model loading component in Amazon GluonTS before 0.17.0 might allow context-dependent attackers to execute arbitrary operating system commands with the privileges of the loading process via a crafted serialized model directory. To remediate this issue, users should upgrade to version 0.17.0 or later.

In Devolutions Server 2026.3.5.0 and earlier, missing authorization in the gateway network scan token API allows an authenticated low-privileged user to generate a network scan token and perform internal network discovery and port scanning through the gateway via a crafted API request.

Devolutions Server 2026.3.5.0 and earlier stores sensitive information in cleartext in the database. An attacker with read access to the database can obtain external identity provider tokens and active session identifiers.

In Devolutions Server 2026.3.5.0 and earlier, missing authorization in the attachment history API allows an authenticated low-privileged user to permanently delete or restore vault attachments via a crafted API request.

In Devolutions Server 2026.3.5.0 and earlier, missing authorization in the data source settings API allows an authenticated non-administrative user to disclose integration secrets via a crafted API request.

Fumasoft Fumeng Cloud contains a SQL injection vulnerability in the AjaxMethod.ashx endpoint that allows unauthenticated remote attackers to inject arbitrary SQL through the Name parameter of the getEmpByname action without any authentication. Attackers can exploit UNION-based SQL injection techniques against the Microsoft SQL Server backend to extract, disclose, and modify database contents, with potential for further compromise of the underlying server. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-18.

Weblate 4.11.1 through 2026.7.1 contains an argument-injection vulnerability in its Mercurial backend. Repository filenames beginning with - could be interpreted as Mercurial options instead of literal paths. An authenticated user with project-scoped component.edit permission could exploit this through a Mercurial-backed RESX component using the Update RESX files add-on, potentially executing arbitrary commands with the privileges of the Weblate service account. This issue has been patched in version 2026.8.