# CVE-2025-31946: Pixmeo OsiriX MD Use After Free

> A local attacker can cause memory corruption or system crash by importing a crafted DICOM file into OsiriX MD.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2025
- **Updated:** 9 May 2025
- **Also known as:** GHSA-m38h-87r3-2882

## What is CVE-2025-31946?

CVE-2025-31946 is a medium-severity use after free vulnerability in Pixmeo OsiriX MD, published on 8 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Pixmeo OsiriX MD  is vulnerable to a local use after free scenario, which could allow an attacker to locally import a crafted DICOM file and cause memory corruption or a system crash.

Weakness: CWE-416 (Use After Free)

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


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

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

## Is CVE-2025-31946 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-31946 is a medium-severity use after free vulnerability in Pixmeo OsiriX MD, published on 8 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31946 in the wild and no public exploit code.

Affected product: Pixmeo OsiriX MD. 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-31946/ (Markdown: https://insights.sbomify.com/CVE-2025-31946/index.md)
```

## Sources

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

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