CVE-2025-31946
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPixmeo 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePixmeo OsiriX MD contains a use-after-free vulnerability in its DICOM file parsing functionality. A local attacker can import a specially crafted DICOM file that triggers a use-after-free condition during parsing, leading to memory corruption and potential system crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm OsiriX MD installationCheck for OsiriX MD application in the installed programs list (Windows: Control Panel > Programs and Features, macOS: /Applications folder or Finder)Affected if OsiriX MD is installed on the system
-
Identify installed versionOpen OsiriX MD, go to Help > About or check the application bundle for version information; on macOS right-click app > Get Info to see version numberAffected if Version matches or falls within the affected range (check vendor advisory for specific version numbers)
-
Verify DICOM import capability is accessibleCheck if the DICOM import feature is available in the OsiriX MD interface (File > Import DICOM or similar menu option)Affected if DICOM file import functionality is present and operational
-
Review recent DICOM file importsCheck the application logs or recent file history for any DICOM files imported around the time of any suspicious crashes or errorsAffected if Unsolicited or unexpected DICOM files were imported from untrusted sources
-
Monitor for crash logsExamine system crash logs or OsiriX MD internal logs for use-after-free indicators or memory corruption errors following DICOM operationsAffected if Crashes or memory errors occur during or after DICOM file parsing
The environment is affected if OsiriX MD is installed with a version within the affected range AND the DICOM import feature is accessible and has been used to process files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor patches when available; implement strict input validation on DICOM file imports; consider sandboxing the DICOM parsing process to limit impact of memory corruption.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31946 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31946 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data