# CVE-2025-43583: Substance3D - Viewer | NULL Pointer Dereference (CWE-476)

> An attacker can crash the Substance3D Viewer application by tricking a user into opening a malicious file, causing a denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 9 Jul 2025
- **Also known as:** GHSA-v3vw-6693-q8gx

## What is CVE-2025-43583?

CVE-2025-43583 is a medium-severity vulnerability in Adobe Substance3D - Viewer, published on 8 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Substance3D - Viewer versions 0.22 and earlier are affected by a NULL Pointer Dereference vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability to crash the application, causing disruption in service. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2025-43583?

It affects 1 product.


Products: Adobe Substance 3d Viewer.

## How do I fix CVE-2025-43583?

No fix has been published for CVE-2025-43583 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-43583 being exploited?

There is no known exploitation of CVE-2025-43583 in the wild and no public exploit code.

## Other vulnerabilities in Adobe Substance3D - Viewer

- [CVE-2025-54273](https://insights.sbomify.com/CVE-2025-54273/): Substance3D - Viewer | Out-of-bounds Write (CWE-787) (high 7.8)
- [CVE-2025-54274](https://insights.sbomify.com/CVE-2025-54274/): Substance3D - Viewer | Stack-based Buffer Overflow (CWE-121) (high 7.8)
- [CVE-2025-54280](https://insights.sbomify.com/CVE-2025-54280/): Substance3D - Viewer | Out-of-bounds Write (CWE-787) (high 7.8)
- [CVE-2025-54243](https://insights.sbomify.com/CVE-2025-54243/): Substance3D - Viewer | Out-of-bounds Write (CWE-787) (high 7.8)
- [CVE-2025-54244](https://insights.sbomify.com/CVE-2025-54244/): Substance3D - Viewer | Heap-based Buffer Overflow (CWE-122) (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-43583 and fix it if it is affected.

What it is: CVE-2025-43583 is a medium-severity vulnerability in Adobe Substance3D - Viewer, published on 8 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-43583 in the wild and no public exploit code.

Affected product: Adobe Substance3D - Viewer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-43583/ (Markdown: https://insights.sbomify.com/CVE-2025-43583/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-43583
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-43583
- OSV: https://osv.dev/vulnerability/CVE-2025-43583

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-43583/
Summaries are generated and may contain mistakes; the official description above is the record.