{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6273 exists.","fix":"No fix has been published for CVE-2025-6273 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6273 is a medium-severity denial of service vulnerability in WebAssembly wabt, published on 19 Jun 2025. 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-6273 and fix it if it is affected.\n\nWhat it is: CVE-2025-6273 is a medium-severity denial of service vulnerability in WebAssembly wabt, published on 19 Jun 2025. 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-6273 exists.\n\nAffected product: WebAssembly wabt. 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-6273/ (Markdown: https://insights.sbomify.com/CVE-2025-6273/index.md)","id":"CVE-2025-6273","markdown":"https://insights.sbomify.com/CVE-2025-6273/index.md","name":"CVE-2025-6273","record":{"aliases":["DEBIAN-CVE-2025-6273","GHSA-frwp-9m3q-pjc8","UBUNTU-CVE-2025-6273"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WebAssembly binary toolkit","requires_auth":"low_privilege","summary":"A reachable assertion in wabt's binary reader allows local attackers to cause a denial of service via crafted WebAssembly binaries.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"wabt","vendor":"webassembly"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"}],"description":"A vulnerability was found in WebAssembly wabt up to 1.0.37 and classified as problematic. This issue affects the function LogOpcode of the file src/binary-reader-objdump.cc. The manipulation leads to reachable assertion. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The code maintainer explains that this issue might not affect \"real world wasm programs\".","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":"WebAssembly wabt binary-reader-objdump.cc LogOpcode assertion","id":"CVE-2025-6273","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"WebAssembly wabt binary-reader-interp.cc OnDataCount resource consumption","id":"CVE-2025-6274"},"packages":[],"prev":{"headline":"wasm3 m3_compile.c MarkSlotAllocated out-of-bounds write","id":"CVE-2025-6272"},"products":["wabt"],"published":"2025-06-19","related":[{"cvss_score":7.1,"headline":"Memory corruption in n/a","id":"CVE-2022-43280","kev_date_added":null,"published":"2022-10-28"},{"cvss_score":7.1,"headline":"Memory corruption in n/a","id":"CVE-2022-43282","kev_date_added":null,"published":"2022-10-28"},{"cvss_score":5.5,"headline":"Null dereference in n/a","id":"CVE-2023-27119","kev_date_added":null,"published":"2023-03-10"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2022-43283","kev_date_added":null,"published":"2022-10-28"},{"cvss_score":5.3,"headline":"WebAssembly wabt Malformed File binary-reader-interp.cc OnExport heap-based overflow","id":"CVE-2025-2368","kev_date_added":null,"published":"2025-03-17"},{"cvss_score":4.8,"headline":"WebAssembly wabt wasm-decompile InsertNode memory corruption","id":"CVE-2025-15411","kev_date_added":null,"published":"2026-01-01"},{"cvss_score":4.8,"headline":"WebAssembly wabt wasm-decompile VarName out-of-bounds","id":"CVE-2025-15412","kev_date_added":null,"published":"2026-01-01"}],"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":"2025-06-23","vendors":["WebAssembly"]},"summary":"A reachable assertion in wabt's binary reader allows local attackers to cause a denial of service via crafted WebAssembly binaries.","url":"https://insights.sbomify.com/CVE-2025-6273/"}