{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-38754 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-38754 is a medium-severity memory corruption vulnerability in BusyBox, published on 15 Jul 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-2026-38754 and fix it if it is affected.\n\nWhat it is: CVE-2026-38754 is a medium-severity memory corruption vulnerability in BusyBox, published on 15 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-38754 in the wild and no public exploit code.\n\nAffected product: BusyBox. 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-2026-38754/ (Markdown: https://insights.sbomify.com/CVE-2026-38754/index.md)","id":"CVE-2026-38754","markdown":"https://insights.sbomify.com/CVE-2026-38754/index.md","name":"CVE-2026-38754","record":{"aliases":["AZL-92484","BELL-CVE-2026-38754","DEBIAN-CVE-2026-38754","ECHO-d18b-2042-fd80","GHSA-jj7c-h3wm-vjfw","MINI-w98q-8p27-cqq8","UBUNTU-CVE-2026-38754"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"BusyBox shell utility","requires_auth":"none","summary":"Attackers can cause a Denial of Service in BusyBox via a heap overflow in the ash shell when processing crafted input.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"busybox","vendor":"busybox"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"A heap overflow in the ifsbreakup() function (shell/ash.c) of Busybox v1.38.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted input.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in BusyBox","id":"CVE-2026-38754","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in BusyBox","id":"CVE-2026-38755"},"packages":[],"prev":{"headline":"Use after free in BusyBox","id":"CVE-2026-38753"},"products":["BusyBox"],"published":"2026-07-15","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2022-48174","kev_date_added":null,"published":"2023-08-22"},{"cvss_score":9.8,"headline":"Memory corruption in busybox","id":"CVE-2021-42377","kev_date_added":null,"published":"2021-11-15"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-2148","kev_date_added":null,"published":"2017-02-09"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2022-28391","kev_date_added":null,"published":"2022-04-03"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2017-16544","kev_date_added":null,"published":"2017-11-20"},{"cvss_score":8,"headline":"Memory corruption in n/a","id":"CVE-2018-1000517","kev_date_added":null,"published":"2018-06-26"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2023-39810","kev_date_added":null,"published":"2023-08-28"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-22","vendors":["BusyBox"]},"summary":"Attackers can cause a Denial of Service in BusyBox via a heap overflow in the ash shell when processing crafted input.","url":"https://insights.sbomify.com/CVE-2026-38754/"}