dbcve.org
DimensionApplication · Adobe

CVE-2025-43572

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 4.1.2 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.2 and earlier are affected by an out-of-bounds write 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.2 and earlier contain an out-of-bounds write vulnerability that can be triggered by opening a specially crafted malicious file, leading to arbitrary code execution in the context of the current user. The vulnerability requires user interaction (opening a file) for exploitation.

MitigationUpgrade Dimension to a patched version newer than 4.1.2. Until the patch is available, exercise caution when opening files from untrusted sources and consider application whitelisting to mitigate code execution risks.

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.2

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 in Program Files or Program Files (x86) for an 'Adobe Dimension' folder. On macOS, check /Applications for Adobe Dimension.app.
    Affected if The application folder exists on the system
  2. Locate the version information
    On Windows, right-click the Dimension executable (typically in the installation folder) and select Properties > Details to view the File Version. On macOS, right-click Adobe Dimension.app, select Get Info, and look under Version or Get Info > General.
    Affected if You can locate version information for the installed application
  3. Compare your installed version to the affected range
    Review the version number found in the previous step. Adobe Dimension versions follow a format like X.X.X. Compare the full version string against 4.1.2.
    Affected if The installed version is 4.1.2 or any earlier version (for example, 4.1.1, 4.1.0, 4.0.x, etc.)
  4. Verify the file type handling configuration
    This vulnerability is triggered by opening a specially crafted file. Check if Adobe Dimension is set as the default handler for any file types (such as .dimension or associated 3D file formats).
    Affected if Dimension is configured as the default application for opening files, increasing the risk of accidental opening of untrusted files

You are affected if Adobe Dimension is installed and the version is 4.1.2 or earlier, as these versions contain the out-of-bounds write vulnerability that can execute arbitrary code when a malicious file is opened.

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.2 or later
Fixed in 4.1.2
Interim mitigation

Upgrade Dimension to a patched version newer than 4.1.2. Until the patch is available, exercise caution when opening files from untrusted sources and consider application whitelisting to mitigate code execution risks.

Recommended fix High confidence

Adobe Dimension 4.1.2 or later

  1. 1. Close Adobe Dimension if it is currently running
  2. 2. Open Adobe Creative Cloud desktop application or navigate to the Adobe Dimension download page
  3. 3. Locate Adobe Dimension in your installed applications
  4. 4. Check the current installed version (Help > About Adobe Dimension)
  5. 5. If the version is 4.1.2 or earlier, initiate an update through the Creative Cloud app or download the latest version from helpx.adobe.com
  6. 6. Install the updated version (4.1.2 or later)
  7. 7. Restart Adobe Dimension after installation
  8. 8. Verify the installed version shows 4.1.2 or later

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

Fix this in Dimension Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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