<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T04:00:09.754575+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2025-53011</id>
    <title>CVE-2025-53011 — MaterialX is Vulnerable to NULL Pointer Dereference due to Unchecked implGraphOutput</title>
    <updated>2026-10-03T04:00:09.785358+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AcademySoftwareFoundation MaterialX</p>
<p>MaterialX is an open standard for the exchange of rich material and look-development content across applications and renderers. In version 1.39.2, 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. An attacker could intentionally crash a target program that uses MaterialX by sending a malicious MTLX file. This is fixed in version 1.39.3.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-53011"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-7qw8-3vmf-gj32</id>
    <title>GHSA-7qw8-3vmf-gj32 — MaterialX Null Pointer Dereference in MaterialXCore Shader Generation due to Unchecked implGraphOutput</title>
    <updated>2026-10-03T04:00:09.785420+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: MaterialX</p>
<p>### Summary</p>
<p>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.</p>
<p>### Details</p>
<p>In `source/MaterialXCore/Material.cpp`, the following code extracts the output nodes for a given implementation graph:</p>
<p>```cpp
   InterfaceElementPtr impl = materialNodeDef-&gt;getImplementation();
            if (impl &amp;&amp; impl-&gt;isA&lt;NodeGraph&gt;())
            {
                NodeGraphPtr implGraph = impl-&gt;asA&lt;NodeGraph&gt;();
                for (OutputPtr defOutput : materialNodeDef-&gt;getOutputs())
                {
                    if (defOutput-&gt;getType() == MATERIAL_TYPE_STRING)
                    {
                        OutputPtr implGraphOutput = implGraph-&gt;getOutput(defOutput-&gt;getName());
                        for (GraphIterator it = implGraphOutput-&gt;traverseGraph().begin(); it != GraphIterator::end(); ++it)
                        {
                            ElementPtr upstreamElem = it.getUpstreamElement();
                            if (!upstreamElem)
                            {
                                it.setPruneSubgraph(true);
                                continue;
                            }
                            NodePtr upstreamNode = upstreamElem-&gt;asA&lt;Node&gt;();
                            if (upstreamNode &amp;&amp; upstream
```</p>
<p>However, when defining the `implGraphOutput` variable by getting the output node, the code doesn't check whether its value is null be…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-7qw8-3vmf-gj32"/>
  </entry>
</feed>
