dbcve.org
AutocadApplication · Autodesk

CVE-2024-8591

HIGH · 7.8 CVSS v3.1 Published 2024-10-29
Fix available
A fix is available. Upgrade to 2025.1.1 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 3DM file when parsed in AcTranslators.exe through Autodesk AutoCAD can force a Heap-Based Buffer Overflow vulnerability. A malicious actor can leverage this vulnerability to cause a crash, write 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 · high confidence

Heap-based buffer overflow vulnerability in AcTranslators.exe when parsing maliciously crafted 3DM files in Autodesk AutoCAD, allowing arbitrary code execution in the current process context.

MitigationApply Autodesk's security patch for AutoCAD; avoid opening untrusted 3DM files from unknown or unverified 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
AutocadApplication
Affected:>= 2025, < 2025.1.1
Autocad Advance SteelApplication
Affected:>= 2025, < 2025.1.1
Autocad ArchitectureApplication
Affected:>= 2025, < 2025.1.1
Autocad Civil 3dApplication
Affected:>= 2025, < 2025.1.1
Autocad ElectricalApplication
Affected:>= 2025, < 2025.1.1
Autocad MechanicalApplication
Affected:>= 2025, < 2025.1.1
Autocad MepApplication
Affected:>= 2025, < 2025.1.1
Autocad Plant 3dApplication
Affected:>= 2025, < 2025.1.1

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 AutoCAD product and version
    Open AutoCAD, go to Help > About, or run the command 'VER' or 'ABOUT' in the command line to display the version number. Alternatively, check the Windows Programs and Features list for the installed Autodesk AutoCAD version.
    Affected if The version shown is 2025.x (where x is any build before 2025.1.1) or the product name contains '2025' without the 2025.1.1 update applied.
  2. Confirm AcTranslators.exe component is present
    Navigate to the AutoCAD installation directory (typically C:\Program Files\Autodesk\AutoCAD 2025\) and verify that AcTranslators.exe exists. This is the component that processes 3DM file imports.
    Affected if The file AcTranslators.exe exists in the AutoCAD 2025 installation folder, indicating the vulnerable component is present.
  3. Check if 3DM import functionality is enabled
    In AutoCAD, go to Options (OP command) > Files tab > Printer Support File Path > or check the Translators settings. Alternatively, attempt to import a 3DM file using the IIMPORT command or by using INSERT with 3DM filter to verify the translator is available.
    Affected if 3DM file import/translation capability is accessible in the AutoCAD environment, meaning the vulnerable code path can be triggered.
  4. Verify the patch state of the installation
    Check Windows Update history for Autodesk updates, or in AutoCAD go to Help > Check for Updates, or review the Autodesk Account portal for installed updates. Look specifically for an update referenced as 2025.1.1 or later.
    Affected if No 2025.1.1 or later security update has been applied, leaving the vulnerability unpatched.

If AutoCAD 2025 (or any variant like AutoCAD Architecture, Civil 3D, Electrical, etc.) is installed with a version lower than 2025.1.1 and the AcTranslators.exe component is present and 3DM file handling is enabled, the environment is affected by this vulnerability.

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 2025.1.1 or later
Fixed in 2025.1.1
Interim mitigation

Apply Autodesk's security patch for AutoCAD; avoid opening untrusted 3DM files from unknown or unverified sources.

Recommended fix High confidence

AutoCAD 2025.1.1 (and corresponding 2025.1.1 releases for AutoCAD Architecture, Civil 3D, Electrical, Mechanical, MEP, Plant 3D, and Advance Steel)

  1. Identify the specific Autodesk AutoCAD 2025 product installed (e.g., AutoCAD, AutoCAD Architecture, AutoCAD Civil 3D, etc.)
  2. Open the application and navigate to Help > About AutoCAD to verify the current version number
  3. Ensure all running AutoCAD instances are closed
  4. Download AutoCAD 2025.1.1 or the corresponding update for your specific product from the Autodesk Account or support site (www.autodesk.com)
  5. Run the installer or apply the update following Autodesk's standard upgrade procedure
  6. Restart the application and confirm the version shows 2025.1.1 or later
  7. Test with the previously vulnerable 3DM file workflow to confirm the vulnerability is resolved
Caveat Minor point release upgrade within 2025 product line; should have minimal breaking changes but verify critical custom scripts or plugins remain compatible

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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