{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56111 exists.","fix":"No fix has been published for CVE-2026-56111 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56111 is a high-severity memory corruption vulnerability in MarlinFirmware Marlin, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-56111 and fix it if it is affected.\n\nWhat it is: CVE-2026-56111 is a high-severity memory corruption vulnerability in MarlinFirmware Marlin, published on 24 Jun 2026. 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-2026-56111 exists.\n\nAffected product: MarlinFirmware Marlin. 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-56111/ (Markdown: https://insights.sbomify.com/CVE-2026-56111/index.md)","id":"CVE-2026-56111","markdown":"https://insights.sbomify.com/CVE-2026-56111/index.md","name":"CVE-2026-56111","record":{"aliases":["GHSA-x5qg-qgv8-q7cr"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["denial_of_service","other"],"network_reachable":"yes","non_default_config":true,"product_category":"3D printer firmware","requires_auth":"none","summary":"Attackers can corrupt firmware memory and cause denial of service by sending crafted G-code commands to Marlin firmware with mesh bed leveling enabled.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-129","name":"Improper Validation of Array Index"}],"description":"Marlin Firmware through 2.1.2.7, fixed in commit 1f255d1, when built with MESH_BED_LEVELING enabled, contains an out-of-bounds write vulnerability in the M421 G-code handler that allows attackers to corrupt firmware memory by supplying out-of-range X and Y grid indices. Attackers can send a single crafted G-code command via USB serial, network interface, or malicious gcode file to write an attacker-controlled 32-bit float value past the z_values array bounds, corrupting adjacent firmware variables and causing denial of service or firmware state corruption.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-06-24","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-06-24T21:00:03Z","kind":"github_poc","ref":"https://github.com/Christbowel/CVE-2026-56111","stars":1,"title":"Proof of concept for CVE-2026-56111, an out-of-bounds write in the M421 G-code handler of Marlin Firmware"}],"tier":"weaponised"},"has_fix":false,"headline":"Marlin Firmware 2.1.2.7 Out-of-Bounds Write via M421 G-code Handler","id":"CVE-2026-56111","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"dhcpcd Heap Use-After-Free in dhcp6_deprecateaddrs via DHCPv6 RENEW","id":"CVE-2026-56113"},"packages":[],"prev":{"headline":"ALSA Library \u003c 1.2.16.1 Double-Free via parse_def() in conf.c","id":"CVE-2026-56109"},"products":["Marlin"],"published":"2026-06-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["MarlinFirmware"]},"summary":"Attackers can corrupt firmware memory and cause denial of service by sending crafted G-code commands to Marlin firmware with mesh bed leveling enabled.","url":"https://insights.sbomify.com/CVE-2026-56111/"}