CVE-2026-27195
HighSummary
Wasmtime to środowisko uruchomieniowe dla WebAssembly. Od wersji 39.0.0 funkcja `component-model-async` stała się domyślna, co wprowadziło nową implementację `[Typed]Func::call_async`, która miała błąd prowadzący do paniki w określonych okolicznościach związanych z wywołaniami asynchronicznymi.
Risk Assessment
Błąd ten może prowadzić do niestabilności aplikacji, ponieważ instancja komponentu może znaleźć się w stanie, w którym nie można jej ponownie wywołać, co wpływa na dostępność usług.
Recommendation
Zaleca się aktualizację do najnowszej wersji Wasmtime, aby usunąć ten błąd oraz monitorowanie aplikacji pod kątem wystąpienia paniki związanej z wywołaniami asynchronicznymi.
Related vulnerabilities
- CVE-2026-15688Critical
A vulnerability in Mitsubishi Electric GX Works3 and Motion Control Setting stems from an incorrect implementation of the authentication algorithm. A local attacker can successfully authenticate even with an invalid block password by modifying part of the executable module in memory.
- CVE-2026-88795Critical
The wpShopGermany IT-RECHT KANZLEI WordPress plugin before 2.4 does not generate its API authentication token securely, deriving it from data the requester controls and creating it as a side effect of the check that is supposed to validate it. This allows unauthenticated attackers to predict the token and use the access it grants to write arbitrary files, leading to remote code execution.
- CVE-2026-86710Critical
The Login with QR WordPress plugin through 1.0.0 does not verify that the code used to log a user in is one it issued, matching any stored user metadata value instead. This allows unauthenticated attackers to log in as any user, including administrators.
- CVE-2026-86709Critical
The Pressengine WordPress plugin through 1.0 does not stop its login handler from issuing a session when authentication fails. This allows unauthenticated attackers to log in as any user, including administrators.
- CVE-2026-86707Critical
The Private Feed Key WordPress plugin through 0.1 does not verify that the key used to authenticate a feed request is one it issued, matching any stored user metadata value instead. This allows unauthenticated attackers to log in as any user, including administrators.
- CVE-2026-87796Critical
The Multi Uploader for Gravity Forms plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to and including 1.1.9 via the move_file function. This is due to insufficient file type validation during chunked upload handling. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
- CVE-2026-61594Critical
djust prior to version 1.0.7 has a vulnerability in the WebSocket transport that bypasses standard Django authorization mechanisms (such as LoginRequiredMixin, PermissionRequiredMixin, etc.) and the staff gate in the admin extension. Mount authorization is done via check_view_auth, not the View.dispatch() chain, allowing anonymous or under-privileged clients to open a WebSocket and dispatch view handlers, including admin ones.
- CVE-2026-92805Critical
UVdesk Community Skeleton through 1.1.8 fails to authenticate or validate installation state on wizard endpoints in ConfigureHelpdesk controller actions. Unauthenticated attackers can repoint the database and create super administrator accounts by submitting crafted requests to wizard endpoints, gaining full control of the instance.
- CVE-2026-92787Critical
Feast through 0.66.0 fails to verify JWT token signatures before establishing user identity, allowing attackers to bypass all role-based access control by presenting an unverified token with a hardcoded claim value. Attackers can obtain trusted internal identity and gain unchecked read and write access to all entities, feature views, data sources, and permission policies on the server.
- CVE-2026-76460CriticalActively exploited
A vulnerability in the API of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to bypass authentication. This is due to insufficient authentication control on an API endpoint. An attacker could send a crafted request to gain unauthorized access to the device by bypassing the web-based management interface.
Original NVD description (English source)
Wasmtime is a runtime for WebAssembly. Starting with Wasmtime 39.0.0, the `component-model-async` feature became the default, which brought with it a new implementation of `[Typed]Func::call_async` which made it capable of calling async-typed guest export functions. However, that implementation had a bug leading to a panic under certain circumstances: First, the host embedding calls `[Typed]Func::call_async` on a function exported by a component, polling the returned `Future` once. Second, the component function yields control to the async runtime (e.g. Tokio), e.g. due to a call to host function registered using `LinkerInstance::func_wrap_async` which yields, or due an epoch interruption. Third, the host embedding drops the `Future` after polling it once. This leaves the component instance in a non-reenterable state since the call never had a chance to complete. Fourth, the host embedding calls `[Typed]Func::call_async` again, polling the returned `Future`. Since the component inst