{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-43853 exists.","fix":"No fix has been published for CVE-2025-43853 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-43853 is a high-severity path traversal vulnerability in bytecodealliance wasm-micro-runtime, published on 15 May 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-43853 and fix it if it is affected.\n\nWhat it is: CVE-2025-43853 is a high-severity path traversal vulnerability in bytecodealliance wasm-micro-runtime, published on 15 May 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-43853 exists.\n\nAffected product: bytecodealliance wasm-micro-runtime. 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-43853/ (Markdown: https://insights.sbomify.com/CVE-2025-43853/index.md)","id":"CVE-2025-43853","markdown":"https://insights.sbomify.com/CVE-2025-43853/index.md","name":"CVE-2025-43853","record":{"aliases":["GHSA-8fc8-4g25-c8m7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"WebAssembly runtime","requires_auth":"none","summary":"Attackers can escape the filesystem sandbox via symlinks to read or create files on the host system when using the uvwasi feature on Windows.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"webassembly_micro_runtime","vendor":"bytecodealliance"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-61","name":"UNIX Symbolic Link (Symlink) Following"}],"description":"The WebAssembly Micro Runtime's (WAMR) iwasm package is the executable binary built with WAMR VMcore which supports WebAssembly System Interface (WASI) and command line interface. Anyone running WAMR up to and including version 2.2.0 or WAMR built with libc-uvwasi on Windows is affected by a symlink following vulnerability. On WAMR running in Windows, creating a symlink pointing outside of the preopened directory and subsequently opening it with create flag will create a file on host outside of the sandbox. If the symlink points to an existing host file, it's also possible to open it and read its content. Version 2.3.0 fixes the issue.","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":"iwasm vulnerable to filesystem sandbox escape with symlink when using uvwasi feature","id":"CVE-2025-43853","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"DIFY vulnerable to Clickjacking Attack","id":"CVE-2025-43854"},"packages":[],"prev":{"headline":"GHSL-2025-022_Retrieval-based-Voice-Conversion-WebUI","id":"CVE-2025-43852"},"products":["wasm-micro-runtime"],"published":"2025-05-15","related":[{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2024-25431","kev_date_added":null,"published":"2024-11-08"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2024-27532","kev_date_added":null,"published":"2024-11-08"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2024-34251","kev_date_added":null,"published":"2024-05-06"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2023-48105","kev_date_added":null,"published":"2023-11-22"},{"cvss_score":6.9,"headline":"WebAssembly Micro Runtime's `--addr-pool` option allows all IPv4 addresses when subnet mask is not specified","id":"CVE-2025-54126","kev_date_added":null,"published":"2025-07-29"},{"cvss_score":6.2,"headline":"Memory corruption in n/a","id":"CVE-2024-34250","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":"2025-05-15","vendors":["bytecodealliance"]},"summary":"Attackers can escape the filesystem sandbox via symlinks to read or create files on the host system when using the uvwasi feature on Windows.","url":"https://insights.sbomify.com/CVE-2025-43853/"}