Threats affecting pkg:generic/hdf5

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.

ZITADEL 3.0.0 through 3.4.15 and 4.0.0 before 4.19.5 contains a missing authorization vulnerability in Login V2 that allows attackers to approve OAuth 2.0 device authorizations using a victim's existing session without consent. Attackers can send a signed-in user a link carrying the attacker's user code to obtain the victim's tokens, and can bypass project access settings via the OIDC device authorization API.

ZITADEL versions 4.0.0 through 4.19.4 have an authentication bypass vulnerability in the Login V2 UI. This flaw allows unauthenticated attackers to set the initial credential for users who do not have any authentication method configured. By computing a valid verificationCheck cookie using the user ID and browser fingerprint, attackers can set passwords, register passkeys, or link identity providers, effectively taking over user accounts.

ZITADEL versions 4.0.0 up to but not including 4.19.5 contain a host header injection vulnerability in the Login V2 UI. This flaw allows unauthenticated attackers to manipulate password-reset, invite, and email-verification links by supplying malicious host headers. By exploiting this, attackers who know a victim's login name can redirect these single-use links to their own host, intercept the codes, and potentially take over user accounts, including those of instance administrators. The vulnerability is rated high severity with a CVSS score of 8.6. A fix is available in version 4.19.5.

Parse Server before 8.6.106 and 9.0.0 before 9.10.5-alpha.7 mishandles dot notation keys with null or undefined values when building the saved object, so a write is stored but returns an error and skips afterSave triggers and LiveQuery events. A client with write access can exploit this to evade audit logging, notifications, and derived data updates.

Parse Server before 8.6.107 and 9.0.0 before 9.10.5-alpha.8 returns the stored value of a field reverted by a beforeSave trigger in object update responses, even to clients without read access to that object or field. An authenticated client able to update an object whose beforeSave trigger reverts a field, via revert() or a constant: true validator, can read protected values, including its own account's raw MFA authData when protectedFieldsTriggerExempt is enabled.

CVE-2026-119124 is a heap-based buffer overflow vulnerability in ImageMagick versions before 7.1.2-34. The flaw occurs in the -morph processing feature, where specially crafted images can cause writes beyond the bounds of a heap buffer. This can lead to heap memory corruption and application crashes when processing such images.