dbcve.org
Autocad MechanicalApplication · Autodesk

CVE-2025-1275

HIGH · 7.8 CVSS v3.1 Published 2025-04-15
Fix available
A fix is available. Upgrade to 2023.1.7 / 2024.1.7 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
A maliciously crafted JPG file, when linked or imported into certain Autodesk applications, can force a Heap-Based Overflow vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.

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

A heap-based buffer overflow vulnerability exists in certain Autodesk applications when parsing maliciously crafted JPG image files. The vulnerability is triggered when a user links or imports a specially crafted JPG file, leading to memory corruption that can be exploited for denial of service, sensitive data disclosure, or arbitrary code execution in the context of the current process.

MitigationApply vendor-provided patches for affected Autodesk products. Until patches are available, avoid opening or importing JPG files from untrusted sources into vulnerable applications.

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
Autocad MechanicalApplication
Affected:>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad MepApplication
Affected:>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad Plant 3dApplication
Affected:>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Civil 3dApplication
Affected:>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Advance SteelApplication
Affected:>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad Map 3dApplication
Affected:>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad LtApplication
Affected:>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Dwg TrueviewApplication
Affected:>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.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. Identify installed Autodesk product
    Open the application and go to Help > About Autodesk [Product], or check Add/Remove Programs for the installed Autodesk application name
    Affected if The product is one of: AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, Advance Steel, AutoCAD Map 3D, AutoCAD LT, or DWG Trueview
  2. Determine installed version number
    Run the application, type VER or INFO at the command prompt, or check the program's Properties in Control Panel > Programs and Features
    Affected if The exact version number is displayed (format like 2023.x.x, 2024.x.x, or 2025.x.x)
  3. Compare version against affected ranges
    Match your installed version to the vulnerable ranges: 2023 versions before 2023.1.7, 2024 versions before 2024.1.7, or 2025 versions before 2025.1.2
    Affected if Your version falls within any of these ranges: >= 2023 and < 2023.1.7; >= 2024 and < 2024.1.7; >= 2025 and < 2025.1.2
  4. Assess JPG file import usage
    Review recent workflow or check if the DWG Trueview or AutoCAD product is used to link or import external JPG image files into drawings
    Affected if The product is used to import or link JPG files from any source, especially untrusted ones

You are affected if you have any of the eight listed Autodesk products installed with a version matching the vulnerable ranges and you use the JPG import/link feature.

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 2023.1.7 / 2024.1.7 / 2025.1.2 or later
Fixed in 2023.1.72024.1.72025.1.2
Interim mitigation

Apply vendor-provided patches for affected Autodesk products. Until patches are available, avoid opening or importing JPG files from untrusted sources into vulnerable applications.

Recommended fix High confidence

Upgrade to 2023.1.7, 2024.1.7, or 2025.1.2 (or later) depending on your product version

  1. Identify the exact Autodesk product and version currently installed (e.g., AutoCAD Mechanical 2024.0.1)
  2. Navigate to the Autodesk Account or product download page to obtain the update
  3. Download the update matching your product line: For 2023 products, update to version 2023.1.7 or later; For 2024 products, update to version 2024.1.7 or later; For 2025 products, update to version 2025.1.2 or later
  4. Close all running instances of the affected Autodesk application
  5. Run the installer to apply the update
  6. Restart the application and verify the version reflects the patched release
  7. Alternatively, enable automatic updates in Autodesk Desktop App to receive future security patches
Caveat Standard Autodesk update; review release notes for any workflow changes

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

Fix this in Autocad Mechanical Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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