{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42212 exists.","fix":"No fix has been published for CVE-2026-42212 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-42212 is a high-severity vulnerability in anzory SolidCAM-GPPL-IDE, published on 8 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-42212 and fix it if it is affected.\n\nWhat it is: CVE-2026-42212 is a high-severity vulnerability in anzory SolidCAM-GPPL-IDE, published on 8 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42212 exists.\n\nAffected product: anzory SolidCAM-GPPL-IDE. 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-42212/ (Markdown: https://insights.sbomify.com/CVE-2026-42212/index.md)","id":"CVE-2026-42212","markdown":"https://insights.sbomify.com/CVE-2026-42212/index.md","name":"CVE-2026-42212","record":{"aliases":["GHSA-92vg-f4fq-fxm9"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"SolidCAM Postprocessor IDE","requires_auth":"none","summary":"Attackers can disclose local files and cause denial of service via malicious VMID files in SolidCAM Postprocessor IDE due to unsafe XML parsing.","user_interaction":"required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-776","name":"Improper Restriction of Recursive Entity References in DTDs"},{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"SolidCAM-GPPL-IDE is an unofficial, independently developed extension, Postprocessor IDE for SolidCAM. From version 1.0.0 to before version 1.0.2, Opening a .gpp file in the SolidCAM Postprocessor IDE extension causes the language server to parse a companion .vmid file from the same directory (naming convention: foo.gpp to foo.vmid). The VMID parser called XDocument.Load(path) without any XmlReaderSettings, inheriting the framework defaults which in .NET 8 allow DTD processing. A malicious .vmid file could therefore: disclose local files via external entity references, exhaust memory via recursive entity expansion, and cause denial of service via oversized or deeply nested XML. This issue has been patched in version 1.0.2.","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":"SolidCAM-GPPL-IDE: XML External Entity (XXE) and billion-laughs DoS in VMID parser","id":"CVE-2026-42212","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xxe","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"SolidCAM-GPPL-IDE: Path traversal in `inc` directive enables file probing and NTLM-hash leak","id":"CVE-2026-42213"},"packages":[],"prev":{"headline":"React Router's vendored turbo-stream v2 allows arbitrary constructor invocation via TYPE_ERROR deserialization leading to Unauth RCE","id":"CVE-2026-42211"},"products":["SolidCAM-GPPL-IDE"],"published":"2026-05-08","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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["anzory"]},"summary":"Attackers can disclose local files and cause denial of service via malicious VMID files in SolidCAM Postprocessor IDE due to unsafe XML parsing.","url":"https://insights.sbomify.com/CVE-2026-42212/"}