Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
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 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…
Recommended action: Upgrade to 1.39.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When parsing an MTLX file with multiple nested nodegraph implementations, the MaterialX XML parsing logic can potentially crash due to stack exhaustion. Details By specification, multiple kinds of elements in MTLX support nesting other elements, such as in the case of nodegraph elements. Parsing these subtrees is implemented via recursion, and since there is no max depth imposed on the XML document, this can lead to a stack overflow when the library parses an MTLX file with an excessively high number of nested elements. PoC Please download the recursionoverflow.mtlx file from the following link: https://github.com/ShielderSec/poc/tree/main/CVE-2025-53009 build/bin/MaterialXView --material recursionoverflow.mtlx Impact An attacker could intentionally crash a target program that uses MaterialX by sending a malicious MTLX file.
Recommended action: Upgrade to 1.39.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When parsing shader nodes in a MTLX file, the MaterialXCore code accesses a potentially null pointer, which can lead to crashes with maliciously crafted files. Details In source/MaterialXCore/Material.cpp, the following code extracts the output nodes for a given implementation graph: However, when defining the implGraphOutput variable by getting the output node, the code doesn't check whether its value is null before accessing its iterator traverseGraph(). This leads to a potential null pointer dereference. PoC Please download nullptrimplgraph.mtlx from the following link: https://github.com/ShielderSec/poc/tree/main/CVE-2025-53011 build/bin/MaterialXView --material nullptrimplgraph.mtlx Impact An attacker could intentionally crash a target program that uses MaterialX by sending a malicious MTLX file.
Recommended action: Upgrade to 1.39.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When parsing shader nodes in a MTLX file, the MaterialXCore code accesses a potentially null pointer, which can lead to crashes with maliciously crafted files. Details In src/MaterialXCore/Material.cpp, in function getShaderNodes, the following code fetches the output nodes for a given nodegraph input node: The issues arise because the nodeGraph-getOutput(input-getOutputString()) call can return a null pointer, therefore when trying to call output-getConnectedNode(), this results in a crash . PoC Please download nullptrgetshadernodes.mltx from the following link: https://github.com/ShielderSec/poc/tree/main/CVE-2025-53010 build/bin/MaterialXView --material nullptrgetshadernodes.mtlx Impact An attacker could intentionally crash a target program that uses OpenEXR by sending a malicious MTLX file.
Recommended action: Upgrade to 1.39.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.