Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.0amended

MaterialX Null Pointer Dereference in getShaderNodes due to Unchecked nodeGraph->getOutput return

CVE-2025-53010GHSA-3jhf-gxhr-q4cx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (materialx 1.39.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI materialx

    Affected
    >= 1.39.2, <= 1.39.2
    Fixed in
    1.39.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.0 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P · score source
EPSS
  • CVE-2025-53010: 0.55% estimated exploitation activity in the next 30 days; percentile 46.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-3jhf-gxhr-q4cx

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-3jhf-gxhr-q4cx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-53010

Advisory: MaterialX Null Pointer Dereference in getShaderNodes due to Unchecked nodeGraph->getOutput return
IDs: CVE-2025-53010, GHSA-3jhf-gxhr-q4cx
Record: https://patchnext.com/advisories/cve-2025-53010 (revision 3, source checked 26 Oct 2026, 13:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: materialx 1.39.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI materialx: affected >= 1.39.2, <= 1.39.2; fixed in 1.39.3

## Suggested inspection (read-only)
- `python -m pip show materialx`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on materialx.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3jhf-gxhr-q4cx (OSV record GHSA-3jhf-gxhr-q4cx lists affected ranges: PyPI materialx >=1.39.2 <1.39.3 (fixed))
- Verified: https://github.com/advisories/GHSA-3jhf-gxhr-q4cx (GitHub-reviewed advisory GHSA-3jhf-gxhr-q4cx lists affected ranges: PyPI materialx >=1.39.2 <=1.39.2)

Commands are suggestions: review each one before running it.

Loading voting…