{"answers":{"affected":"3 open source packages ship an affected version, including pywasm3. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6272 exists.","fix":"No fix has been published for CVE-2025-6272 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6272 is a medium-severity memory corruption vulnerability in wasm3, 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-6272 and fix it if it is affected.\n\nWhat it is: CVE-2025-6272 is a medium-severity memory corruption vulnerability in wasm3, 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-6272 exists.\n\nAffected packages and fixed versions:\n- pywasm3 (PyPI): affected all versions up to 0.5.0; no fix listed\n- pywasm3 (PyPI): affected all versions up to 0.5.0; no fix listed\n- pywasm3 (PyPI): affected all versions up to 0.5.0; no fix listed\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-6272/ (Markdown: https://insights.sbomify.com/CVE-2025-6272/index.md)","id":"CVE-2025-6272","markdown":"https://insights.sbomify.com/CVE-2025-6272/index.md","name":"CVE-2025-6272","record":{"aliases":["GHSA-rrmw-gv85-w824","PYSEC-2025-186"],"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":"A local attacker can trigger an out-of-bounds write in the wasm3 library, potentially leading to code execution or denial of service.","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:N/VI:N/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 has been found in wasm3 0.5.0 and classified as problematic. This vulnerability affects the function MarkSlotAllocated of the file source/m3_compile.c. The manipulation leads to out-of-bounds write. An attack has to be approached locally. The exploit has been disclosed to the public and may be used.","ecosystems":["PyPI"],"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_compile.c MarkSlotAllocated out-of-bounds write","id":"CVE-2025-6272","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":3,"n_references":5,"next":{"headline":"WebAssembly wabt binary-reader-objdump.cc LogOpcode assertion","id":"CVE-2025-6273"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.5.0"],"package":"pywasm3","purl":null,"source":"GHSA-rrmw-gv85-w824"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.5.0"],"package":"pywasm3","purl":"pkg:pypi/pywasm3","source":"GHSA-rrmw-gv85-w824"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.5.0"],"package":"pywasm3","purl":"pkg:pypi/pywasm3","source":"PYSEC-2025-186"}],"prev":{"headline":"swftools wav2swf wav.c wav_convert2mono out-of-bounds","id":"CVE-2025-6271"},"products":["wasm3"],"published":"2025-06-19","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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":["n/a"]},"summary":"A local attacker can trigger an out-of-bounds write in the wasm3 library, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2025-6272/"}