{"answers":{"affected":"3 open source packages ship an affected version, including materialx and MaterialX. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53009 exists.","fix":"Upgrade materialx to 1.39.3 or later.","what":"CVE-2025-53009 is a medium-severity denial of service vulnerability in AcademySoftwareFoundation MaterialX, published on 1 Aug 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-53009 and fix it if it is affected.\n\nWhat it is: CVE-2025-53009 is a medium-severity denial of service vulnerability in AcademySoftwareFoundation MaterialX, published on 1 Aug 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-53009 exists.\n\nAffected packages and fixed versions:\n- materialx (PyPI): affected from 1.39.2; fixed in 1.39.3\n- materialx (PyPI): affected from 1.39.2; fixed in 1.39.3\n- MaterialX (PyPI): affected from 1.39.2; fixed in 1.39.3\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-53009/ (Markdown: https://insights.sbomify.com/CVE-2025-53009/index.md)","id":"CVE-2025-53009","markdown":"https://insights.sbomify.com/CVE-2025-53009/index.md","name":"CVE-2025-53009","record":{"aliases":["GHSA-wx6g-fm6f-w822","PYSEC-2026-1609"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MaterialX library","requires_auth":"none","summary":"An attacker can crash applications using MaterialX by sending a malicious MTLX file with deeply nested nodegraphs, causing stack exhaustion.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"materialx","vendor":"linuxfoundation"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"MaterialX is an open standard for the exchange of rich material and look-development content across applications and renderers. In versions 1.39.2 and below, when parsing an MTLX file with multiple nested nodegraph implementations, the MaterialX XML parsing logic can potentially crash due to stack exhaustion. An attacker could intentionally crash a target program that uses OpenEXR by sending a malicious MTLX file. This is fixed in version 1.39.3.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"MaterialX Stack Overflow via Lack of MTLX XML Parsing Recursion Limit","id":"CVE-2025-53009","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":3,"n_references":5,"next":{"headline":"MaterialX's unchecked nodeGraph-\u003egetOutput return is vulnerable to NULL Pointer Dereference","id":"CVE-2025-53010"},"packages":[{"ecosystem":"PyPI","fixed":["1.39.3"],"introduced":["1.39.2"],"last_affected":[],"package":"MaterialX","purl":null,"source":"GHSA-wx6g-fm6f-w822"},{"ecosystem":"PyPI","fixed":["1.39.3"],"introduced":["1.39.2"],"last_affected":[],"package":"materialx","purl":"pkg:pypi/materialx","source":"GHSA-wx6g-fm6f-w822"},{"ecosystem":"PyPI","fixed":["1.39.3"],"introduced":["1.39.2"],"last_affected":[],"package":"materialx","purl":"pkg:pypi/materialx","source":"PYSEC-2026-1609"}],"prev":{"headline":"GLPI's MailCollector Receiver is vulnerable to credential exfiltration","id":"CVE-2025-53008"},"products":["MaterialX"],"published":"2025-08-01","related":[{"cvss_score":5.5,"headline":"MaterialX's Lack of Import Depth Limit Leads to DoS (Denial-Of-Service) Via Stack Exhaustion","id":"CVE-2025-53012","kev_date_added":null,"published":"2025-08-01"},{"cvss_score":2,"headline":"MaterialX's unchecked nodeGraph-\u003egetOutput return is vulnerable to NULL Pointer Dereference","id":"CVE-2025-53010","kev_date_added":null,"published":"2025-08-01"},{"cvss_score":2,"headline":"MaterialX is Vulnerable to NULL Pointer Dereference due to Unchecked implGraphOutput","id":"CVE-2025-53011","kev_date_added":null,"published":"2025-08-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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-08-01","vendors":["AcademySoftwareFoundation"]},"summary":"An attacker can crash applications using MaterialX by sending a malicious MTLX file with deeply nested nodegraphs, causing stack exhaustion.","url":"https://insights.sbomify.com/CVE-2025-53009/"}