{"answers":{"affected":"2 open source packages ship an affected version, including waku.","exploited":"There is no known exploitation of CVE-2026-49456 in the wild and no public exploit code.","fix":"Upgrade waku to 1.0.0-beta.1 or later.","what":"CVE-2026-49456 is a low-severity vulnerability in wakujs waku, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-49456 and fix it if it is affected.\n\nWhat it is: CVE-2026-49456 is a low-severity vulnerability in wakujs waku, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-49456 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- waku (npm): affected all versions; fixed in 1.0.0-beta.1\n- waku (npm): affected all versions; fixed in 1.0.0-beta.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-49456/ (Markdown: https://insights.sbomify.com/CVE-2026-49456/index.md)","id":"CVE-2026-49456","markdown":"https://insights.sbomify.com/CVE-2026-49456/index.md","name":"CVE-2026-49456","record":{"aliases":["GHSA-43fc-v873-qw85"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"React framework","requires_auth":"none","summary":"Attackers can redirect users to malicious sites via the unstable_redirect helper, enabling phishing and credential theft in Waku applications.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"Waku is the minimal React framework. Prior to version 1.0.0-beta.1, the unstable_redirect() helper exported from waku/router/server (packages/waku/src/router/define-router.tsx:156–161) accepts an arbitrary string and reflects it unchanged into the HTTP Location response header with no URL validation, scheme restriction, or path-only enforcement. Any application that passes user-controlled input to this helper — the natural pattern documented in the JSDoc and official fixtures — is vulnerable to open redirect attacks. An attacker who convinces a victim to click a crafted link can silently redirect the browser to an arbitrary external domain, enabling phishing, credential harvesting, and OAuth token theft. Additionally, scheme-relative URLs (//evil.example/) bypass naive https?://-only allow-list filters that developers might add as ad-hoc mitigations. This issue has been patched in version 1.0.0-beta.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Waku: Open Redirect via `unstable_redirect` Helper","id":"CVE-2026-49456","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"open_redirect","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"QUIC has Broken TLS verification","id":"CVE-2026-49457"},"packages":[{"ecosystem":"npm","fixed":["1.0.0-beta.1"],"introduced":["0"],"last_affected":[],"package":"waku","purl":null,"source":"GHSA-43fc-v873-qw85"},{"ecosystem":"npm","fixed":["1.0.0-beta.1"],"introduced":["0"],"last_affected":[],"package":"waku","purl":"pkg:npm/waku","source":"GHSA-43fc-v873-qw85"}],"prev":{"headline":"Waku: Cross-Origin CSRF on RSC Server Action Dispatch","id":"CVE-2026-49455"},"products":["waku"],"published":"2026-09-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-03","vendors":["wakujs"]},"summary":"Attackers can redirect users to malicious sites via the unstable_redirect helper, enabling phishing and credential theft in Waku applications.","url":"https://insights.sbomify.com/CVE-2026-49456/"}