KeePassXC versions from 2.3.0 up to but not including 2.8.0 contain an out-of-bounds write vulnerability in the browser integration component. The issue arises because a fixed 1 MiB output buffer is used for encrypting authorized responses, but the encryption function writes more data than this buffer can hold under certain conditions. This flaw can be triggered by a browser-protocol client with valid database association and access to the per-user IPC endpoint when an unlocked database generates a large authorized response. The vulnerability is fixed in version 2.8.0.
Microsoft has been named a Leader in the 2026 IDC MarketScape for Worldwide Modern Endpoint Security for Enterprises. The recognition highlights Microsoft Defender's autonomous attack disruption and predictive shielding capabilities that contain ransomware and identity attacks within minutes. The platform integrates AI-driven detection and response across endpoints, identities, email, and cloud, enabling near real-time containment of threats. The solution includes agentic AI through Security Copilot, improving alert accuracy and reducing analyst workload. Microsoft Defender's unified portal correlates signals from multiple sources into single incidents, facilitating rapid and effective response. The platform also supports securing local AI agents used by employees, providing visibility and control over their activity. This integrated approach addresses the increasing speed and complexity of ransomware and AI-driven attacks observed between 2025 and 2026.
North Korean threat actors are increasingly integrating AI technologies into their cyber operations to enhance speed, efficiency, and complexity. These actors use AI to accelerate social engineering, targeting, malware development, and operational scaling, but their activities remain human-directed rather than fully autonomous. Key groups such as Jade Sleet, Coral Sleet, and Jasper Sleet have operationalized AI across their workflows, while others are at various stages of adoption. Their operations primarily target cryptocurrency, financial organizations, IT companies, government entities, and education sectors to generate revenue, collect intelligence, and pursue political objectives. Microsoft provides mitigation guidance and Defender detections to help defend against these evolving threats.
CVE-2025-13050 is a medium severity vulnerability in Centreon that involves broken function level authorization. It allows an authenticated user with low privileges to execute poller post-restart commands, potentially impacting integrity and availability. The flaw affects Centreon versions 24.04, 24.10, and 25.10. Fixes are available in versions centreon-web-24.04.25, centreon-web-24.10.21, and centreon-web-25.10.9.
Frappe before 15.121.0 and 16.x before 16.34.0 contains a path traversal vulnerability because certain file-upload handling does not validate the destination path before writing to disk. Authenticated attackers can upload crafted files to locations outside the intended storage directory to achieve remote code execution on the server.
CVE-2026-119144 is a server-side template injection vulnerability in the Frappe Framework affecting versions before 15.111.0 and 16.x before 16.21.0. It arises because user-controlled message fields are rendered as templates without proper neutralization, allowing an authenticated attacker with common operational privileges to inject and execute arbitrary template expressions on the server.
CVE-2026-119143 is a denial of service vulnerability in bytecodealliance's wasmtime affecting versions 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3. The flaw allows guest code to cause a host panic by performing out-of-bounds zero-length stream operations, leading to a crash in WASIp3 embedders.
Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a denial of service vulnerability where dropping the Future returned by TypedFunc::call_async can panic the host. When the guest task has not started, cleanup code searches only one location for work items and unwraps the resulting error, crashing embedders that cancel pending calls.
Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a denial of service vulnerability that allows malicious Wasm modules to panic the host because the may_leave flag is not cleared during realloc. Attackers can call into the host from realloc while lowering stream or future results, such as cancelling the active read or re-waiting a waitable-set, crashing the host.
CVE-2026-119140 is a denial of service vulnerability in bytecodealliance's wasmtime affecting versions 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3. It allows malicious components to cause the host to panic by exploiting thread.yield calls in start functions, leading to a crash due to undisposed fiber drops.
CVE-2026-119139 is a reachable assertion vulnerability in bytecodealliance's wasmtime affecting versions 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3. The flaw occurs in component::Func::call, where a leftover assertion rejects guest exports using the async ABI option. An attacker supplying a component with an async-lifted export can cause the host process to crash when that export is invoked.
Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a denial of service vulnerability that allows pending calls to trigger an assertion failure after a trap poisons the Store. Attackers supplying misbehaving guest code can cause a trap and let earlier calls proceed, crashing embedders that continue using the inconsistent Store.
Wasmtime 42.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a stack overflow vulnerability that allows guests to crash the host through recursive type drops. Guests can define a long chain of recursive types so that removing the top-level type triggers unbounded recursive drops, exhausting the host stack.
CVE-2026-119136 affects Wasmtime versions 42.0.0 before 48.0.6 and 49.0.0 before 49.0.3. The vulnerability arises from insufficient checks in the Store component when mixing asynchronous and synchronous WebAssembly calls. This can lead to runtime panics or unsafe cross-thread movement of non-Send host variables when embedders re-enter WebAssembly synchronously from asynchronously called host functions.
CVE-2026-119135 is a vulnerability in bytecodealliance's wasmtime affecting versions 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3. The issue causes a panic (crash) when the host reads a component model stream as a different Rust item type than it was originally created with. This occurs because the host-to-host read path asserts matching TypeIds instead of returning an error, allowing guest code to trigger a crash by returning a host-created StreamReader<U> that the embedder reads as StreamReader<T>.
Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 caps component-model resource handle tables only per component instance and does not charge handle allocations to any ResourceLimiter or StoreLimits. A malicious guest can repeatedly call resource.new and instantiate sub-components to exceed the per-instance cap many times over, causing unbounded host memory growth.
Wasmtime 47.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a memory misalignment flaw in VMContext layout that causes undefined behavior when modules contain an odd number of exception tags. A WebAssembly module with an odd tag count misaligns subsequent host fields in embedders with exceptions enabled, although no exploitation path is currently known.
Wasmtime versions from 49.0.0 up to but not including 49.0.3 contain a denial-of-service vulnerability. This flaw allows a WebAssembly guest to cause the host to panic by transcoding overlapping strings in fused adapters during component-to-component calls. The issue arises when the source and destination strings alias each other, leading to a crash instead of a controlled trap.
CVE-2026-119131 is a denial of service vulnerability in wasmtime versions 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3. The flaw exists in wasmtime-wasi-http where guests can cause the host to crash by sending excessively long request URLs. Specifically, using set-path-with-query with a '?' character after byte 65535 causes an integer overflow of a u16 index in the http crate, triggering a host panic.
Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 does not verify that set-path-with-query values in wasmtime-wasi-http are paths, so absolute-form URLs are written verbatim as the HTTP/1.1 request target while the connection uses the allowed authority. A malicious guest can supply an absolute URL that a forward proxy or gateway at that authority honors, reaching hosts disallowed by embedder filtering policies.