CVE-2025-27578
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 use after free scenario, which could allow an attacker to upload a crafted DICOM file and cause memory corruption leading to a denial-of-service condition.
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. An attacker can trigger this vulnerability by uploading a specially crafted DICOM file, causing memory corruption that leads to denial of service.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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.
-
Verify OsiriX MD is installedSearch for OsiriX MD application in the system: on macOS check /Applications folder or use 'find /Applications -name '*OsiriX*' -type d' command; on Windows check Program Files directories or use Get-ItemProperty registry key for installed softwareAffected if OsiriX MD software is present on the system
-
Identify installed OsiriX MD versionOn macOS, right-click OsiriX MD.app > Get Info > Version, or run 'defaults read /Applications/OsiriX\ MD.app/Contents/Info CFBundleShortVersionString'; on Windows check file properties of the executable or examine version info in registryAffected if Installed version cannot be determined or falls within any vulnerable version range (compare against vendor release notes for CVE-2025-27578)
-
Confirm DICOM file processing is accessibleCheck if DICOM import, upload, or parsing functionality is available: look for DICOM listener services, web upload interfaces, or local file import features in the applicationAffected if DICOM file parsing functionality is enabled and accessible to users or external systems
-
Review access to DICOM file upload pointsExamine network-exposed interfaces where DICOM files can be uploaded: web portals, DICOM C-STORE SCP services, API endpoints accepting DICOM uploads, or shared network folders processed by OsiriX MDAffected if Untrusted DICOM files can be uploaded or received by the OsiriX MD system without prior sanitization
-
Check for crash logs or memory corruption indicatorsReview system logs, application crash reports, and security logs for evidence of unexpected crashes related to DICOM file processing: on macOS check ~/Library/Logs and Console.app; on Windows check Event Viewer Application logsAffected if Unexpected crashes or memory corruption events occur when processing DICOM files
The environment is affected if OsiriX MD is installed with DICOM parsing enabled and external users or systems can supply DICOM files to the system, particularly through upload interfaces.
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 dataImplement proper memory management in the DICOM parser, ensuring all allocated memory is freed before pointers are reused. Validate DICOM file structure before processing and consider deploying input validation and file type verification at upload points.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27578 — 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-27578 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