NPM · JULY 2026 · EARLY WARNING

Potential Open Redirect in Waku npm Package

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
GHSA-43FC-V873-QW85Severity: HIGH

An early warning has been issued regarding a potential open redirect vulnerability in the `waku` npm package, specifically in the `unstable_redirect()` helper. This issue appears to allow user-controlled input to be reflected into the HTTP `Location` response header without proper validation.

What happened

The `unstable_redirect()` helper in the `waku` npm package is under investigation for reflecting user-controlled input into the HTTP `Location` response header without validation. This behavior reportedly leads to open redirect attacks. The affected version is `waku` npm package version 1.0.0-beta.0. It is recommended to avoid using the `unstable_redirect()` helper with untrusted input and to monitor for updates to the `waku` package that may address this vulnerability. For more detailed information, consult the primary sources.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If waku is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats