<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 23:20:12 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-248900</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-248900</link>
      <description>EUVD-2026-248900</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-248900</guid>
    </item>
    <item>
      <title>fkie_cve-2025-53011</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-53011</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-53011</guid>
    </item>
    <item>
      <title>GHSA-7qw8-3vmf-gj32 — MaterialX Null Pointer Dereference in MaterialXCore Shader Generation due to Unchecked implGraphOutput</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7qw8-3vmf-gj32</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: MaterialX&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `source/MaterialXCore/Material.cpp`, the following code extracts the output nodes for a given implementation graph:&lt;/p&gt;
&lt;p&gt;```cpp
   InterfaceElementPtr impl = materialNodeDef-&amp;gt;getImplementation();
            if (impl &amp;amp;&amp;amp; impl-&amp;gt;isA&amp;lt;NodeGraph&amp;gt;())
            {
                NodeGraphPtr implGraph = impl-&amp;gt;asA&amp;lt;NodeGraph&amp;gt;();
                for (OutputPtr defOutput : materialNodeDef-&amp;gt;getOutputs())
                {
                    if (defOutput-&amp;gt;getType() == MATERIAL_TYPE_STRING)
                    {
                        OutputPtr implGraphOutput = implGraph-&amp;gt;getOutput(defOutput-&amp;gt;getName());
                        for (GraphIterator it = implGraphOutput-&amp;gt;traverseGraph().begin(); it != GraphIterator::end(); ++it)
                        {
                            ElementPtr upstreamElem = it.getUpstreamElement();
                            if (!upstreamElem)
                            {
                                it.setPruneSubgraph(true);
                                continue;
                            }
                            NodePtr upstreamNode = upstreamElem-&amp;gt;asA&amp;lt;Node&amp;gt;();
                            if (upstreamNode &amp;amp;&amp;amp; upstream
```&lt;/p&gt;
&lt;p&gt;However, when defining the `implGraphOutput` variable by getting the output node, the code doesn&amp;#39;t check whether its value is null be…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: MaterialX&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `source/MaterialXCore/Material.cpp`, the following code extracts the output nodes for a given implementation graph:&lt;/p&gt;
&lt;p&gt;```cpp
   InterfaceElementPtr impl = materialNodeDef-&amp;gt;getImplementation();
            if (impl &amp;amp;&amp;amp; impl-&amp;gt;isA&amp;lt;NodeGraph&amp;gt;())
            {
                NodeGraphPtr implGraph = impl-&amp;gt;asA&amp;lt;NodeGraph&amp;gt;();
                for (OutputPtr defOutput : materialNodeDef-&amp;gt;getOutputs())
                {
                    if (defOutput-&amp;gt;getType() == MATERIAL_TYPE_STRING)
                    {
                        OutputPtr implGraphOutput = implGraph-&amp;gt;getOutput(defOutput-&amp;gt;getName());
                        for (GraphIterator it = implGraphOutput-&amp;gt;traverseGraph().begin(); it != GraphIterator::end(); ++it)
                        {
                            ElementPtr upstreamElem = it.getUpstreamElement();
                            if (!upstreamElem)
                            {
                                it.setPruneSubgraph(true);
                                continue;
                            }
                            NodePtr upstreamNode = upstreamElem-&amp;gt;asA&amp;lt;Node&amp;gt;();
                            if (upstreamNode &amp;amp;&amp;amp; upstream
```&lt;/p&gt;
&lt;p&gt;However, when defining the `implGraphOutput` variable by getting the output node, the code doesn&amp;#39;t check whether its value is null be…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7qw8-3vmf-gj32</guid>
    </item>
    <item>
      <title>PYSEC-2026-1607 — MaterialX Null Pointer Dereference in MaterialXCore Shader Generation due to Unchecked implGraphOutput</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-1607</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: materialx&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `source/MaterialXCore/Material.cpp`, the following code extracts the output nodes for a given implementation graph:&lt;/p&gt;
&lt;p&gt;```cpp
   InterfaceElementPtr impl = materialNodeDef-&amp;gt;getImplementation();
            if (impl &amp;amp;&amp;amp; impl-&amp;gt;isA&amp;lt;NodeGraph&amp;gt;())
            {
                NodeGraphPtr implGraph = impl-&amp;gt;asA&amp;lt;NodeGraph&amp;gt;();
                for (OutputPtr defOutput : materialNodeDef-&amp;gt;getOutputs())
                {
                    if (defOutput-&amp;gt;getType() == MATERIAL_TYPE_STRING)
                    {
                        OutputPtr implGraphOutput = implGraph-&amp;gt;getOutput(defOutput-&amp;gt;getName());
                        for (GraphIterator it = implGraphOutput-&amp;gt;traverseGraph().begin(); it != GraphIterator::end(); ++it)
                        {
                            ElementPtr upstreamElem = it.getUpstreamElement();
                            if (!upstreamElem)
                            {
                                it.setPruneSubgraph(true);
                                continue;
                            }
                            NodePtr upstreamNode = upstreamElem-&amp;gt;asA&amp;lt;Node&amp;gt;();
                            if (upstreamNode &amp;amp;&amp;amp; upstream
```&lt;/p&gt;
&lt;p&gt;However, when defining the `implGraphOutput` variable by getting the output node, the code doesn&amp;#39;t check whether its value is null be…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: materialx&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `source/MaterialXCore/Material.cpp`, the following code extracts the output nodes for a given implementation graph:&lt;/p&gt;
&lt;p&gt;```cpp
   InterfaceElementPtr impl = materialNodeDef-&amp;gt;getImplementation();
            if (impl &amp;amp;&amp;amp; impl-&amp;gt;isA&amp;lt;NodeGraph&amp;gt;())
            {
                NodeGraphPtr implGraph = impl-&amp;gt;asA&amp;lt;NodeGraph&amp;gt;();
                for (OutputPtr defOutput : materialNodeDef-&amp;gt;getOutputs())
                {
                    if (defOutput-&amp;gt;getType() == MATERIAL_TYPE_STRING)
                    {
                        OutputPtr implGraphOutput = implGraph-&amp;gt;getOutput(defOutput-&amp;gt;getName());
                        for (GraphIterator it = implGraphOutput-&amp;gt;traverseGraph().begin(); it != GraphIterator::end(); ++it)
                        {
                            ElementPtr upstreamElem = it.getUpstreamElement();
                            if (!upstreamElem)
                            {
                                it.setPruneSubgraph(true);
                                continue;
                            }
                            NodePtr upstreamNode = upstreamElem-&amp;gt;asA&amp;lt;Node&amp;gt;();
                            if (upstreamNode &amp;amp;&amp;amp; upstream
```&lt;/p&gt;
&lt;p&gt;However, when defining the `implGraphOutput` variable by getting the output node, the code doesn&amp;#39;t check whether its value is null be…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-1607</guid>
    </item>
  </channel>
</rss>
