{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-0537 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-0537 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-0537 is a high-severity memory corruption vulnerability in Autodesk 3ds Max, published on 4 Feb 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-0537 and fix it if it is affected.\n\nWhat it is: CVE-2026-0537 is a high-severity memory corruption vulnerability in Autodesk 3ds Max, published on 4 Feb 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-0537 in the wild and no public exploit code.\n\nAffected product: Autodesk 3ds Max. 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-0537/ (Markdown: https://insights.sbomify.com/CVE-2026-0537/index.md)","id":"CVE-2026-0537","markdown":"https://insights.sbomify.com/CVE-2026-0537/index.md","name":"CVE-2026-0537","record":{"aliases":["GHSA-7pw6-2xv6-25xh"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"3D modeling software","requires_auth":"none","summary":"A malicious RGB file can trigger memory corruption in Autodesk 3ds Max, allowing attackers to execute arbitrary code.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"autodesk","cpe":[{"product":"3ds_max","vendor":"autodesk"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"A maliciously crafted RGB file, when parsed through Autodesk 3ds Max, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"RGB File Parsing Memory Corruption","id":"CVE-2026-0537","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"GIF File Parsing Out-of-Bounds Write","id":"CVE-2026-0538"},"packages":[],"prev":{"headline":"GIF File Parsing Stack Based Buffer Overflow","id":"CVE-2026-0536"},"products":["3ds Max"],"published":"2026-02-04","related":[{"cvss_score":9.3,"headline":"Code injection in n/a","id":"CVE-2009-3577","kev_date_added":null,"published":"2009-11-24"},{"cvss_score":8.4,"headline":"GIF File Parsing Out-of-Bounds Write","id":"CVE-2026-0538","kev_date_added":null,"published":"2026-02-04"},{"cvss_score":8.4,"headline":"Stack Based Buffer Overflow in GIF File Parsing","id":"CVE-2026-0660","kev_date_added":null,"published":"2026-02-04"},{"cvss_score":8.4,"headline":"Out-of-Bounds Write in RGB File Parsing","id":"CVE-2026-0661","kev_date_added":null,"published":"2026-02-04"},{"cvss_score":7.8,"headline":"ABC File Parsing Out-of-Bounds Write Vulnerability in Autodesk 3ds Max","id":"CVE-2026-16783","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":7.8,"headline":"SVG File Parsing Memory Corruption Vulnerability in Autodesk 3ds Max","id":"CVE-2026-19568","kev_date_added":null,"published":"2026-08-24"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-03","vendors":["Autodesk"]},"summary":"A malicious RGB file can trigger memory corruption in Autodesk 3ds Max, allowing attackers to execute arbitrary code.","url":"https://insights.sbomify.com/CVE-2026-0537/"}