{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54126 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2025-54126 is a medium-severity vulnerability in bytecodealliance wasm-micro-runtime, published on 29 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-54126 and fix it if it is affected.\n\nWhat it is: CVE-2025-54126 is a medium-severity vulnerability in bytecodealliance wasm-micro-runtime, published on 29 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54126 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-54126/ (Markdown: https://insights.sbomify.com/CVE-2025-54126/index.md)","id":"CVE-2025-54126","markdown":"https://insights.sbomify.com/CVE-2025-54126/index.md","name":"CVE-2025-54126","record":{"aliases":["AZL-66045","AZL-66048","GHSA-vh64-mfvw-pxqp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"WebAssembly runtime","requires_auth":"none","summary":"WAMR's iwasm allows all IPv4 addresses when --addr-pool lacks a subnet mask, potentially exposing services to unauthorized access.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"webassembly_micro_runtime","vendor":"bytecodealliance"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"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. In versions 2.4.0 and below, iwasm uses --addr-pool with an IPv4 address that lacks a subnet mask, allowing the system to accept all IP addresses. This can unintentionally expose the service to all incoming connections and bypass intended access restrictions. Services relying on --addr-pool for restricting access by IP may unintentionally become open to all external connections. This may lead to unauthorized access in production deployments, especially when users assume that specifying an IP without a subnet mask implies a default secure configuration. This is fixed in version 2.4.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"WebAssembly Micro Runtime's `--addr-pool` option allows all IPv4 addresses when subnet mask is not specified","id":"CVE-2025-54126","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"HAXcms's Insecure Default Configuration Leads to Unauthenticated Access","id":"CVE-2025-54127"},"packages":[],"prev":{"headline":"XWiki Platform: Password and email exposure in xml.vm fields","id":"CVE-2025-54125"},"products":["wasm-micro-runtime"],"published":"2025-07-29","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":7,"headline":"iwasm vulnerable to filesystem sandbox escape with symlink when using uvwasi feature","id":"CVE-2025-43853","kev_date_added":null,"published":"2025-05-15"},{"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-30","vendors":["bytecodealliance"]},"summary":"WAMR's iwasm allows all IPv4 addresses when --addr-pool lacks a subnet mask, potentially exposing services to unauthorized access.","url":"https://insights.sbomify.com/CVE-2025-54126/"}