What is CVE-2025-53009?

CVE-2025-53009 is a medium-severity security vulnerability in MaterialX (pip), affecting versions = 1.39.2. It is fixed in 1.39.3.

Which versions of MaterialX are affected by CVE-2025-53009?

MaterialX (pip) versions = 1.39.2 is affected.

Is there a fix for CVE-2025-53009?

Yes. CVE-2025-53009 is fixed in 1.39.3. Upgrade to this version or later.

Is CVE-2025-53009 exploitable, and should I be worried?

Whether CVE-2025-53009 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-53009 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-53009 in MaterialX

Q: How do I fix CVE-2025-53009?

Upgrade MaterialX to 1.39.3 or later.

Summary

MaterialX Stack Overflow via Lack of MTLX XML Parsing Recursion Limit

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 recursion_overflow.mtlx file from the following link:

https://github.com/ShielderSec/poc/tree/main/CVE-2025-53009

build/bin/MaterialXView --material recursion_overflow.mtlx

Impact

An attacker could intentionally crash a target program that uses MaterialX by sending a malicious MTLX file.

Affected versions

MaterialX (= 1.39.2)

Security releases

MaterialX → 1.39.3 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade MaterialX to 1.39.3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-53009? CVE-2025-53009 is a medium-severity security vulnerability in MaterialX (pip), affecting versions = 1.39.2. It is fixed in 1.39.3.
Which versions of MaterialX are affected by CVE-2025-53009? MaterialX (pip) versions = 1.39.2 is affected.
Is there a fix for CVE-2025-53009? Yes. CVE-2025-53009 is fixed in 1.39.3. Upgrade to this version or later.
Is CVE-2025-53009 exploitable, and should I be worried? Whether CVE-2025-53009 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-53009 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-53009? Upgrade MaterialX to 1.39.3 or later.

Other vulnerabilities in MaterialX

CVE-IDSeverityPackage summary

CVE-2025-53012MediumMaterialX: MaterialX Lack of MTLX Import Depth Limit Leads to DoS (Denial-Of-Service) Via Stack Exhaustion CVE-2025-53011LowMaterialX: MaterialX Null Pointer Dereference in MaterialXCore Shader Generation due to Unchecked implGraphOutput CVE-2025-53010LowMaterialX: MaterialX Null Pointer Dereference in getShaderNodes due to Unchecked nodeGraph->getOutput return