{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15413 exists.","fix":"No fix has been published for CVE-2025-15413 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-15413 is a medium-severity memory corruption vulnerability in wasm3, published on 1 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-15413 and fix it if it is affected.\n\nWhat it is: CVE-2025-15413 is a medium-severity memory corruption vulnerability in wasm3, published on 1 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15413 exists.\n\nAffected product: wasm3. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2025-15413/ (Markdown: https://insights.sbomify.com/CVE-2025-15413/index.md)","id":"CVE-2025-15413","markdown":"https://insights.sbomify.com/CVE-2025-15413/index.md","name":"CVE-2025-15413","record":{"aliases":["GHSA-fgq8-gvxr-ghw7"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WebAssembly runtime library","requires_auth":"low_privilege","summary":"Local attackers can exploit memory corruption in wasm3 to execute arbitrary code or cause denial of service, with no active maintainer to provide a fix.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"wasm3","vendor":"wasm3_project"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A vulnerability was detected in wasm3 up to 0.5.0. Impacted is the function op_SetSlot_i32/op_CallIndirect of the file m3_exec.h. Performing a manipulation results in memory corruption. The attack needs to be approached locally. The exploit is now public and may be used. Unfortunately, the project has no active maintainer at the moment.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"wasm3 m3_exec.h op_CallIndirect memory corruption","id":"CVE-2025-15413","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"go-sonic Theme Fetching API git_fetcher.go FetchTheme server-side request forgery","id":"CVE-2025-15414"},"packages":[],"prev":{"headline":"WebAssembly wabt wasm-decompile VarName out-of-bounds","id":"CVE-2025-15412"},"products":["wasm3"],"published":"2026-01-01","related":[{"cvss_score":9.8,"headline":"pywasm3 contains a heap buffer overflow which leads to segmentation fault","id":"CVE-2024-34249","kev_date_added":null,"published":"2024-05-06"},{"cvss_score":8.4,"headline":"pywasm3 has an Invalid Memory Read, Leading to DoS and Potential Code Execution","id":"CVE-2024-27528","kev_date_added":null,"published":"2024-11-08"},{"cvss_score":8.4,"headline":"wasm3 uncontrolled memory allocation vulnerability","id":"CVE-2024-27529","kev_date_added":null,"published":"2024-11-08"},{"cvss_score":8.4,"headline":"pywasm3 contains a Use-After-Free in ForEachModule","id":"CVE-2024-27530","kev_date_added":null,"published":"2024-11-08"},{"cvss_score":7.8,"headline":"Buffer overflow in wasm3","id":"CVE-2022-28990","kev_date_added":null,"published":"2022-05-20"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-27527","kev_date_added":null,"published":"2024-11-08"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2024-34246","kev_date_added":null,"published":"2024-05-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-23","vendors":["n/a"]},"summary":"Local attackers can exploit memory corruption in wasm3 to execute arbitrary code or cause denial of service, with no active maintainer to provide a fix.","url":"https://insights.sbomify.com/CVE-2025-15413/"}