Qwik: Crashing any Qwik Server via Resource thenable

Summary A Qwik server in the default configuration can be crashed with one unauthenticated HTTP request. During qwik-json body parsing, ResourceSerializer.$fill$ does Promise.resolveresource.resolved. If resolved is a plain object whose .then is a QRL for an unregistered symbol, the async QRL...

GHSA-X586-XVC8-G7Q6 Qwik: Crashing any Qwik Server via Resource thenable

Summary A Qwik server in the default configuration can be crashed with one unauthenticated HTTP request. During qwik-json body parsing, ResourceSerializer.$fill$ does Promise.resolveresource.resolved. If resolved is a plain object whose .then is a QRL for an unregistered symbol, the async QRL...

CVE-2026-84994

Qwik is a performance-focused JavaScript framework. Prior to @builder.io/qwik 1.20.0 and @qwik.dev/core 2.0.0-beta.37, default server-side qwik-json deserialization causes ResourceSerializer.$fill$ to pass resource.resolved to Promise.resolve without first rejecting attacker-controlled thenables...

CVE-2026-84994 Qwik: Crashing any Qwik Server via Resource thenable

Qwik is a performance-focused JavaScript framework. Prior to @builder.io/qwik 1.20.0 and @qwik.dev/core 2.0.0-beta.37, default server-side qwik-json deserialization causes ResourceSerializer.$fill$ to pass resource.resolved to Promise.resolve without first rejecting attacker-controlled thenables...

CVE-2026-84994

The Qwik JavaScript framework is vulnerable in versions prior to @builder.io/qwik 1.20.0 and @qwik.dev/core 2.0.0-beta.37 . The root cause is a flaw in default server-side qwik-json deserialization where ResourceSerializer.$fill$ passes resource._resolved to Promise.resolve without rejecting atta...

CVE-2026-107392

music-metadata is a metadata parser for audio and video media files. Prior to 11.15.0, the DSF parser handles an unrecognized chunk by calling tokenizer.ignore without awaiting the returned promise and without first rejecting a chunk size smaller than the 12-byte chunk header. A crafted DSF input...

CVE-2026-107392

The music-metadata metadata parser (versions

PT-2026-108172

Name of the Vulnerable Software and Affected Versions music-metadata versions prior to 11.15.0 Description The DSF parser handles unrecognized chunks by calling tokenizer.ignore without awaiting the returned promise and without rejecting chunk sizes smaller than the 12-byte chunk header. A...

vm2: Host-returned Promise rejection can bypass vm2's unhandled-rejection hardening and terminate the host process

Summary vm2 current head v3.11.5, commit 7a1f5100b96f48d34e0fe104ab37c0acc5944f92 can still be used to terminate the host Node.js process when sandbox code calls a host-realm function that returns a rejected host Promise and then ignores the returned value. This is an incomplete-fix variant of th...

GHSA-GJQ8-XM47-88RC vm2: Host-returned Promise rejection can bypass vm2's unhandled-rejection hardening and terminate the host process

Summary vm2 current head v3.11.5, commit 7a1f5100b96f48d34e0fe104ab37c0acc5944f92 can still be used to terminate the host Node.js process when sandbox code calls a host-realm function that returns a rejected host Promise and then ignores the returned value. This is an incomplete-fix variant of th...

EUVD-2026-81603

vm2: Host-returned Promise rejection can bypass vm2's unhandled-rejection hardening and terminate the host process...

devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise

When serializing multiple promises, a later promise can reject before an earlier one settles. An internal rejected promise remains unhandled even if the caller catches the returned stringifyAsync promise. Under Node's default unhandled-rejection behavior this can terminate the process. Applicatio...

GHSA-X5RW-Q4PP-HG5G devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise

When serializing multiple promises, a later promise can reject before an earlier one settles. An internal rejected promise remains unhandled even if the caller catches the returned stringifyAsync promise. Under Node's default unhandled-rejection behavior this can terminate the process. Applicatio...

NPM: devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise

NPM: devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise vulnerability discovered by ? in WordPress Npm devalue versions = 5.8.0, = 5.9.2...

EUVD-2026-71465

undici vulnerable to Denial of Service via WebSocketStream unclean close...

CVE-2026-100722 vm2 before 3.12.2 Host Process Termination via Construct Trap

vm2 before 3.12.2 does not apply host-side Promise rejection handling in the sandbox-to-host construct trap. In BaseHandler, the apply trap calls markHostPromiseHandled on the returned value, but the adjacent construct path returns the result of Reflect.construct without the same sanitization. If...

Uncaught Exception

Overview vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules. Affected versions of this package are vulnerable to Uncaught Exception in the handling of Promises returned from the host realm into the sandbox. An attacker can cause the host process to terminate...

CVE-2026-92954

vm2 is a sandbox library for running untrusted JavaScript in Node.js. In versions = 3.10.0 and = 3.11.7, Promises returned from the host realm into the sandbox are not marked as handled at the bridge boundary; only Promises created inside the sandbox are wrapped with a rejection-swallowing handle...

CVE-2026-92954 vm2 3.10.0 through 3.11.7 Denial of Service via Host Promise

vm2 is a sandbox library for running untrusted JavaScript in Node.js. In versions = 3.10.0 and = 3.11.7, Promises returned from the host realm into the sandbox are not marked as handled at the bridge boundary; only Promises created inside the sandbox are wrapped with a rejection-swallowing handle...

CVE-2026-92954 vm2 3.10.0 through 3.11.7 Denial of Service via Host Promise

vm2 is a sandbox library for running untrusted JavaScript in Node.js. In versions = 3.10.0 and = 3.11.7, Promises returned from the host realm into the sandbox are not marked as handled at the bridge boundary; only Promises created inside the sandbox are wrapped with a rejection-swallowing handle...