{"answers":{"affected":"2 open source packages ship an affected version, including waku.","exploited":"There is no known exploitation of CVE-2026-49455 in the wild and no public exploit code.","fix":"Upgrade waku to 1.0.0-beta.1 or later.","what":"CVE-2026-49455 is a medium-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-49455 and fix it if it is affected.\n\nWhat it is: CVE-2026-49455 is a medium-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-49455 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-49455/ (Markdown: https://insights.sbomify.com/CVE-2026-49455/index.md)","id":"CVE-2026-49455","markdown":"https://insights.sbomify.com/CVE-2026-49455/index.md","name":"CVE-2026-49455","record":{"aliases":["GHSA-75w3-gmqx-993q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"React framework","requires_auth":"none","summary":"Attackers can force victims to execute state-mutating server actions via cross-origin requests due to missing Origin validation in Waku.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Waku is the minimal React framework. Prior to version 1.0.0-beta.1, Waku's RSC request dispatcher invokes server actions without validating the request's Origin (or Sec-Fetch-Site) header. A cross-origin web attacker can therefore cause a victim browser to issue an authenticated POST to a registered server action endpoint using a CORS-safelisted content type (text/plain), which does not trigger a preflight. Any state-mutating server action that the application exposes via 'use server' can be invoked with the victim's cookies attached. 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: Cross-Origin CSRF on RSC Server Action Dispatch","id":"CVE-2026-49455","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Waku: Open Redirect via `unstable_redirect` Helper","id":"CVE-2026-49456"},"packages":[{"ecosystem":"npm","fixed":["1.0.0-beta.1"],"introduced":["0"],"last_affected":[],"package":"waku","purl":null,"source":"GHSA-75w3-gmqx-993q"},{"ecosystem":"npm","fixed":["1.0.0-beta.1"],"introduced":["0"],"last_affected":[],"package":"waku","purl":"pkg:npm/waku","source":"GHSA-75w3-gmqx-993q"}],"prev":{"headline":"Relyra SAML SignatureValue not cryptographically verified -\u003e authentication bypass","id":"CVE-2026-49454"},"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 force victims to execute state-mutating server actions via cross-origin requests due to missing Origin validation in Waku.","url":"https://insights.sbomify.com/CVE-2026-49455/"}