The MongoDB C# Driver does not neutralize dot and dollar characters in dictionary keys, field names and array-filter identifiers used in LINQ queries before placing them into the field paths it sends to the server. An application user whose input reaches these positions can redirect a query or update to fields the application did not name, which can expose other users' documents and widen updates beyond the intended data. Certain values can also write malformed fields that leave stored documents unreadable by the application until they are repaired.
Wasmtime before 36.0.17, 37.0.0 before 48.0.4, and 49.0.0 before 49.0.2 contains an information disclosure vulnerability in the WASIp1 fd_readdir implementation that copies uninitialized struct padding into guest memory. Guests with a preopened directory can list entries to receive three bytes of leftover host stack or heap memory per directory entry.
Wasmtime versions 46.0.0 before 48.0.4 and 49.0.0 before 49.0.2 contain a denial of service vulnerability in the wasmtime-wasi WASIp3 implementation. This flaw allows guests with mutable preopened directory access to cause the Unix host process to abort by invoking set-times or set-times-at with negative timestamps before the epoch, triggering an assertion failure that crashes the host.
The MongoDB C# Driver does not reject replacement documents whose top-level field names begin with a dollar sign in FindOneAndReplace, unlike other replace operations. An application that builds such a document from user-supplied field names can have the server apply update operators instead of a full replacement. The effect is limited to the document matched by the application's own filter, whose contents can be modified in ways the application did not intend.
CVE-2026-115384 is a critical stack buffer overflow vulnerability in bytecodealliance's wasmtime affecting versions 39.0.0 before 48.0.4 and 49.0.0 before 49.0.2. It arises from improper input validation of async callback result types, allowing malicious guests to write approximately 16KB to the native stack. This can lead to crashing the host or escaping the sandbox environment.
A data-validation flaw exists in the BSON handling and binary serialization path of the MongoDB C# Driver. When an application constructs a raw or lazy BSON document object from externally supplied binary data, the driver does not verify that the size quantity declared inside that data matches the amount of data actually provided, and it copies the data onto the wire unchanged. An unauthenticated party who can supply binary content to such an application can thereby cause additional elements to be inserted into, or existing elements to be removed from, the database command the application issues, without needing any database credentials of their own. This can result in unauthorized modification of stored data and disclosure of data outside the intended scope of the application's request, bounded by the database privileges the application itself holds.
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.