Wasmtime versions 47.0.0 before 48.0.4 and 49.0.0 before 49.0.2 have an improper validation vulnerability related to WebAssembly tags with subtypes. This flaw allows malicious guests to mis-type exception object payloads, potentially corrupting the garbage-collected heap and causing Wasmtime to panic when the exceptions proposal is enabled.
Wasmtime 46.0.0 before 48.0.4 and 49.0.0 before 49.0.2 contains a denial-of-service vulnerability in its wasi:http implementation that allows guests to panic the host. Guests can specify a zero between-bytes-timeout request option, which is forwarded directly to a Tokio API that panics, crashing the host embedding.
A 32-bit integer wraparound in the MongoDB C Driver's Windows-only Kerberos/SSPI authentication code can cause an undersized heap buffer to be allocated when an excessively long credential value is supplied in the client's connection configuration. A party able to control that client-side configuration, in conjunction with the affected authentication mechanism, can cause the driver to write outside the bounds of the allocated buffer. This may result in corruption of client process memory and denial of service of the client application. The issue affects only client builds compiled with the Windows-native authentication backend.
CVE-2026-115381 is a medium severity vulnerability in bytecodealliance's wasmtime. It involves unbounded memory allocation in the wasmtime-wasi WASIp2 write-zeroes method of SinkOutputStream, which is the default stream when stdout/stderr are not configured. Malicious WebAssembly guests can exploit this to request large zero-filled writes, exhausting host memory and causing denial of service. The issue affects wasmtime versions before 36.0.17, versions from 37.0.0 up to but not including 48.0.4, and versions from 49.0.0 up to but not including 49.0.2.
The MongoDB C# Driver's BSON library contains an uncontrolled resource consumption weakness in its deserialization handling of one BSON value type. An application that deserializes untrusted content with the library retains data derived from that content for the lifetime of the process, with no limit on how much accumulates. An unauthenticated remote party who can cause such content to be deserialized can drive unbounded memory growth, exhausting the host application's available memory and denying service. There is no impact to confidentiality or integrity, and no MongoDB server component is affected.
CVE-2026-115380 is a denial of service vulnerability in the wasmtime-wasi WASI preview 0 poll_oneoff adapter of the wasmtime runtime. It affects versions before 36.0.17, versions from 37.0.0 up to but not including 48.0.4, and versions from 49.0.0 up to but not including 49.0.2. The vulnerability arises because the adapter performs O(n) host work per subscription without consuming or checking fuel, allowing malicious guest modules to cause long-running host computations that ignore configured fuel limits.
The MongoDB C# Driver writes GeoJSON extra members without checking whether their names collide with reserved GeoJSON members such as type and coordinates. An application that places user-supplied field names into these extra members can store documents with duplicate geometry fields, so the server and the driver resolve different values for the same record. Affected records can also become unreadable through the driver, interrupting application code that reads them.
CVE-2026-115379 is a use-after-free vulnerability in bytecodealliance's wasmtime affecting versions 47.0.0 before 48.0.4 and 49.0.0 before 49.0.2. The flaw involves missing garbage collection rooting that leaves references unrooted across try_call when compiling WebAssembly modules. This can cause garbage collection heap corruption or incorrect execution when attackers supply specially crafted Wasm modules.
Incus before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0 contains an arbitrary file write vulnerability in sftpRecursivePullFile that allows a malicious incus-agent to escape the target directory during incus file pull -r. Attackers with root in a virtual machine can return duplicate entries reported first as symlinks then as files or directories, writing attacker-controlled files such as /etc/shadow on the operator's host.
CVE-2026-115377 is a critical arbitrary file write vulnerability in the Incus container management software (lxc). It affects versions before 6.0.7, versions from 6.1.0 up to but not including 7.0.2, and versions from 7.1.0 up to but not including 7.5.0. The flaw allows malicious migration sources to write files on the host system by planting symbolic links in transferred volumes during migration. This can lead to full host compromise if exploited.
Incus versions 7.0.1 before 7.0.2 and 7.2.0 before 7.5.0 contain an authorization bypass vulnerability. This flaw allows project-restricted clients to copy volumes by omitting the source.type parameter. Attackers can exploit this by sending crafted POST requests to the custom volumes endpoint with a chosen source.project, enabling them to copy and read volumes, snapshots, and configurations from other projects.
Incus versions 7.0.0 before 7.0.2 and 7.1.0 before 7.5.0 contain a path traversal vulnerability that allows clients with instance creation privileges to write files on the host system. The vulnerability arises from unvalidated custom volume names in instance backup index.yaml files, which can include '../' sequences. Exploiting this flaw enables attackers to create root-owned directories with attacker-controlled content, potentially leading to full host compromise.
Incus 7.0.0 before 7.0.2 and 7.1.0 before 7.5.0 contains a signature verification flaw in its built-in S3 server that allows presigned URL holders to inject unsigned x-amz-* headers. Attackers can add an unsigned X-Amz-Copy-Source header to a presigned upload URL to copy other bucket objects onto the granted key, disclosing their contents and ETags.
Incus versions before 6.0.7, versions from 6.1.0 up to but not including 7.0.2, and versions from 7.1.0 up to but not including 7.5.0 contain a missing authorization vulnerability in the GET /1.0/operations/{uuid} endpoint. This flaw allows project-restricted clients to access operations belonging to other projects. Exploitation requires possession of a restricted certificate and knowledge of a valid operation UUID. Successful exploitation can expose sensitive data including command lines, environment secrets, websocket secrets, and trust enrolment tokens.
CVE-2026-115372 is a critical vulnerability in Incus versions 7.3.0 up to but not including 7.5.0. It allows restricted project users to bypass project restrictions by setting block.create_options during volume update, copy, and move operations. This can lead to argument injection into the mkfs command executed as root, potentially allowing privilege escalation.
Incus versions 6.0.3 before 6.0.7, 6.6.0 before 7.0.2, and 7.1.0 before 7.5.0 contain an improper authorization vulnerability that allows restricted TLS clients to access storage bucket keys in the default project. This vulnerability enables attackers to retrieve S3 access and secret keys, potentially allowing them to read, modify, or delete objects in those buckets.
Incus 6.0.5 before 6.0.7, 6.12.0 before 7.0.2, and 7.1.0 before 7.5.0 contains a restriction bypass vulnerability that allows restricted project users to use pull mode migration via clustered refresh requests. Attackers with instance creation rights can send a refresh migration request for an existing instance to make the server open outbound TLS websocket connections and probe reachable services.
Mistune versions before 3.3.0 have a path traversal vulnerability in the Include directive that allows attackers to read arbitrary files by using ../ sequences. Additionally, attackers can inject HTML via unescaped error messages and included file contents, enabling cross-site scripting even when escape=True is set. This vulnerability has a high severity rating with a CVSS score of 8.7.
CVE-2026-114519 is a missing authorization vulnerability in Roskus Prospero Flow CRM versions from 2.0.0 up to but not including 5.26.0. It allows users with a basic role to read account details of other users within their company and, from version 3.5.0 onward, to delete those accounts. The vulnerability arises because the API routes for reading and deleting users only validate the JSON Web Token but do not enforce permission checks. Notably, users in the default company can delete any account across companies. This can lead to unauthorized access to personal data and deletion of accounts, including administrative ones.
Mistune versions before 3.3.0 have a path traversal vulnerability in the opt-in Include directive. This flaw allows attackers to read arbitrary local files by providing relative or absolute paths. Exploitation can lead to disclosure of sensitive files such as /etc/passwd and injection of unescaped HTML or script content into rendered Markdown output.