CVE-2025-2029
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 · uneditedA vulnerability was found in MicroDicom DICOM Viewer 2025.1 Build 3321. It has been classified as critical. Affected is an unknown function of the file mDicom.exe. The manipulation leads to memory corruption. The attack needs to be approached locally. It is recommended to upgrade the affected component. The vendor quickly confirmed the existence of the vulnerability and fixed it in the latest beta.
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 · high confidenceA memory corruption vulnerability exists in MicroDicom DICOM Viewer 2025.1 Build 3321 within the mDicom.exe file. The vulnerability is locally exploitable and has been classified as critical by the vendor. The vendor has confirmed the issue and released a fix in the latest beta version.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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.
-
Locate MicroDicom DICOM Viewer installationSearch for mDicom.exe on the system using File Explorer search or command: dir /s C:\mDicom.exe (adjust drive letter as needed)Affected if mDicom.exe is found on the system indicating the software is installed
-
Identify installed versionRight-click mDicom.exe, select Properties, then go to the Details tab to view the File Version or Product Version fieldAffected if The version shown is 2025.1 Build 3321 (or any version lower than the fixed beta version)
-
Verify build number from applicationLaunch MicroDicom DICOM Viewer, then access Help > About to display the exact build number displayed by the applicationAffected if The displayed build number is 3321 or falls within the vulnerable range before the patched beta release
If MicroDicom DICOM Viewer is installed with version 2025.1 Build 3321 or earlier, the environment is affected by this memory corruption vulnerability in mDicom.exe.
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.
dbcve · scopedUpgrade MicroDicom DICOM Viewer to the latest beta version as the vendor has already released a patch. Since this is a local attack vector, ensure untrusted DICOM files are not processed by outdated versions.
Latest beta version (newer than 2025.1 Build 3321)
- 1. Verify current MicroDicom DICOM Viewer version by opening mDicom.exe and checking About/Help menu
- 2. Download the latest beta version of MicroDicom DICOM Viewer from the official website www.microdicom.com
- 3. Uninstall the current vulnerable version (2025.1 Build 3321)
- 4. Install the latest beta version which contains the security fix
- 5. Verify the installation and confirm the new build version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2029 — 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-2029 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