← Back
CVE-2025-53010
Vulnerability in materialx (CVE-2025-53010)
Summary
vulnerability in materialx (CVE-2025-53010). Risk of unauthorized operations or information disclosure. Exploitable via ``getShaderNodes``. Mitigation: upgrade to `1.39.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-53010** has been found in materialx.
Attackers can target a specific entry point like ``getShaderNodes`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade materialx to **1.39.3** or later.
If unsure, ask your IT team or search "materialx CVE-2025-53010" on the vendor's site.
CVE-2025-53010 (materialx) — CWE-476 /
Attack surface: `getShaderNodes` / `nodegraph` / `nullptr_getshadernodes.mltx`
Patched: `1.39.3` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-476) exists in materialx. Attackers reach the vulnerable code path via ``getShaderNodes`` without authentication.
📍 Affected scope
materialx — . Attack surface: `getShaderNodes` / `nodegraph` / `nullptr_getshadernodes.mltx`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.39.3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'materialx' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'materialx' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `materialx` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade materialx to 1.39.3ステージング環境で 1.39.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
materialx
[{"type":"ECOSYSTEM","events":[{"introduced":"1.39.2"},{"fixed":"1.39.3"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-53010
- advisory https://github.com/advisories/GHSA-3jhf-gxhr-q4cx
- package https://github.com/AcademySoftwareFoundation/MaterialX
- package https://pypi.org/project/materialx
- web https://github.com/AcademySoftwareFoundation/MaterialX/security/advisories/GHSA-3jhf-gxhr-q4cx
- web https://github.com/AcademySoftwareFoundation/MaterialX/commit/e13344ba13326869d7820b444705f24d56fab73d
- web https://github.com/ShielderSec/poc/tree/main/CVE-2025-53010