CVE-2025-35975
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 · uneditedMicroDicom DICOM Viewer is vulnerable to an out-of-bounds write which may allow an attacker to execute arbitrary code. The user must open a malicious DCM file for exploitation.
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 confidenceMicroDicom DICOM Viewer contains an out-of-bounds write vulnerability in its DICOM file parsing logic. When processing a specially crafted malicious DCM file, the viewer writes data beyond allocated buffer boundaries, which can corrupt memory and enable arbitrary code execution on the affected system.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 MicroDicom installationSearch for MicroDicom in installed programs (Windows: Control Panel > Programs and Features, or check C:\Program Files\MicroDicom or C:\Program Files (x86)\MicroDicom)Affected if MicroDicom DICOM Viewer is present on the system
-
Identify installed versionLaunch MicroDicom, go to Help > About, or right-click the executable in Program Files and select Properties > Details to view the version numberAffected if The installed version matches the affected version range for CVE-2025-35975 (compare against any official vendor advisory)
-
Check for untrusted DCM file processing capabilityVerify if the application can open DCM files from untrusted sources - check if file association for .dcm files exists and the viewer is set as defaultAffected if The viewer is configured to open DCM files from untrusted or unknown sources
-
Review recent DCM file opening activityCheck Windows Event Logs (Application log) or the application's recent files list for any recently opened DCM files, especially from unknown sourcesAffected if The user has recently opened suspicious or untrusted DCM files in MicroDicom
A user is affected if MicroDicom DICOM Viewer is installed with a vulnerable version AND processes a specially crafted malicious DCM file.
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 dataUsers should refrain from opening untrusted or unknown DCM files in MicroDicom DICOM Viewer. Organizations should implement file validation policies and consider upgrading to any available patched version once released.
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-35975 — 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-35975 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