dbcve.org
DimensionApplication · Adobe

CVE-2025-61799

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 an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code 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 · high confidence

Dimension versions 4.1.4 and earlier contain an out-of-bounds read vulnerability when parsing malformed files, allowing an attacker to read memory beyond allocated buffers. This memory disclosure can be leveraged to achieve arbitrary code execution in the context of the current user. Exploitation requires social engineering a victim into opening a specially crafted malicious file.

MitigationUpdate Dimension to version 4.1.5 or later when released. Until a patch is available, avoid opening files from untrusted sources and consider running Dimension in an isolated environment to limit impact.

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. Locate Adobe Dimension installation
    On Windows, open Control Panel > Programs and Features and find 'Adobe Dimension' in the list. On macOS, open Finder > Applications and locate Adobe Dimension.app
    Affected if Adobe Dimension is installed
  2. Determine installed version number
    Right-click Adobe Dimension in the programs list (Windows) or right-click the app and select Get Info (macOS). The version number will be displayed (for example, 4.1.4, 4.1.3, etc.)
    Affected if Version cannot be determined or is not visible
  3. Compare against vulnerable range
    Check if the installed version is 4.1.4 or any earlier version (such as 4.1.3, 4.1.2, 4.0.x, etc.). All versions below 4.1.5 are affected.
    Affected if Installed version is 4.1.4 or earlier
  4. Assess exposure to malicious files
    Consider whether users in your environment open Adobe Dimension files (.dmn, .obj with materials, or other formats) from untrusted or unknown sources, as exploitation requires the victim to open a specially crafted file
    Affected if Users routinely open files from untrusted sources without verification

If Adobe Dimension version 4.1.4 or earlier is installed, the environment is vulnerable to this out-of-bounds read flaw when parsing malformed files.

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

Update Dimension to version 4.1.5 or later when released. Until a patch is available, avoid opening files from untrusted sources and consider running Dimension in an isolated environment to limit impact.

Recommended fix High confidence

4.1.5

  1. Check the currently installed version of Adobe Dimension (Help > About Adobe Dimension)
  2. Download Adobe Dimension version 4.1.5 or later from the official Adobe website (helpx.adobe.com)
  3. Close any running instances of Adobe Dimension
  4. Install the updated version following the on-screen instructions
  5. Restart Adobe Dimension and verify the new version is installed

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

Fix this in Dimension Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61799 — 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-61799 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