Quick answers
- Is CVE-2025-53010 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-53010 being exploited in the wild.
- How severe is CVE-2025-53010?
- Medium severity, with a CVSS score of 4, published 7 July 2026.
- Which products and versions are affected?
- MaterialX (PyPI) ECOSYSTEM:introduced=1.39.2,fixed=1.39.3.
- Is there a fix for CVE-2025-53010?
- Yes. MaterialX (PyPI): upgrade to 1.39.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-53010 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2025-53010?
- Check whether you run MaterialX (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- MaterialX (PyPI): upgrade to 1.39.3 or later
pip install "MaterialX>=1.39.3"
Technical details
This is a null pointer dereference vulnerability (CWE-476) in MaterialX's src/MaterialXCore/Material.cpp file within the getShaderNodes function. The vulnerability occurs when parsing MTLX shader files: the code calls nodeGraph->getOutput() which can return a null pointer, but the returned value is not checked before being dereferenced in a loop to call output->getConnectedNode(). An attacker can craft a malicious MTLX file with a nodegraph output reference that does not exist, triggering a crash when the application attempts to process it. No authentication or special privileges are required; the attack only requires the victim to open the malicious file with MaterialX-based software.
Affected products
- Academy Software Foundation MaterialX 1.39.2
Identifiers
- CVE-2025-53010
- GHSA-3jhf-gxhr-q4cx
- PYSEC-2026-1606
Timeline
- 2025-07-31: disclosed
- 2025-07-31: patched: Fixed in version 1.39.3