dbcve.org
DimensionApplication · Adobe

CVE-2025-61801

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 4.1.5 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Dimension versions 4.1.4 and earlier are affected by a Use After Free vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

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 confidence

Dimension versions 4.1.4 and earlier contain a Use After Free vulnerability in file parsing logic. When processing a specially crafted malicious file, the application frees a memory object but continues to reference it, leading to memory corruption that can be exploited for arbitrary code execution in the context of the user who opened the file.

MitigationUpgrade to a version newer than 4.1.4 when a patch is available. Until then, avoid opening untrusted files in Dimension and use caution with files from untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DimensionApplication
Affected:< 4.1.5

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Adobe Dimension is installed
    On Windows, look for Adobe Dimension in the Start Menu, Program Files, or check the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Adobe Dimension. On macOS, check /Applications for Adobe Dimension.app.
    Affected if Adobe Dimension is not found on the system, so the CVE does not apply.
  2. Find the installed version of Adobe Dimension
    In Windows, right-click the Adobe Dimension executable, select Properties, and view the Details tab for the Version field. On macOS, right-click Adobe Dimension.app, select Get Info, and view the Version field under General.
    Affected if The version cannot be determined, treat as potentially affected.
  3. Compare version to affected range
    Compare the installed version number to 4.1.5. Versions 4.1.4 and earlier are affected; version 4.1.5 and later are not.
    Affected if The installed version is 4.1.4 or earlier.
  4. Confirm the file parsing trigger condition
    This vulnerability is triggered when Adobe Dimension parses a specially crafted malicious file. The user must open such a file in the application for exploitation to occur.
    Affected if A vulnerable version is installed AND the user opens untrusted files in Adobe Dimension.

A user is affected if Adobe Dimension version 4.1.4 or earlier is installed AND they open files in the application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.1.5 or later
Fixed in 4.1.5
Interim mitigation

Upgrade to a version newer than 4.1.4 when a patch is available. Until then, avoid opening untrusted files in Dimension and use caution with files from untrusted sources.

Recommended fix High confidence

Dimension 4.1.5

  1. Close Adobe Dimension if currently running
  2. Download Adobe Dimension version 4.1.5 or later from the official Adobe website or Creative Cloud desktop application
  3. Install the updated version by running the installer and following the on-screen prompts
  4. Restart the application if it was running during installation
  5. Verify the installed version is 4.1.5 or later by checking Help > About Adobe Dimension

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dimension Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61801 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61801 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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