CVE-2024-9826
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 · uneditedA maliciously crafted 3DM file when parsed in atf_api.dll through Autodesk AutoCAD can force a Use-After-Free 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 · moderate confidenceA Use-After-Free vulnerability exists in atf_api.dll when Autodesk AutoCAD parses maliciously crafted 3DM files. The vulnerability allows a malicious actor to cause a crash, write sensitive data, or execute arbitrary code in the context of the current AutoCAD process.
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>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1>= 2025, < 2025.1.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Autodesk productOpen Windows Settings > Apps > Apps & Features, or use PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like '*AutoCAD*' -or '*Advance Steel*' -or '*Civil 3D*' -or '*Electrical*' -or '*Mechanical*' -or '*MEP*' -or '*Plant 3D*' -or '*Architecture*'}Affected if Any listed product shows version 2025.x (where x is any build before 2025.1.1)
-
Verify atf_api.dll versionLocate atf_api.dll in the AutoCAD installation directory (typically C:\Program Files\Autodesk\AutoCAD 2025\). Right-click the file, select Properties, and check the File Version tab.Affected if The DLL exists and the AutoCAD version is 2025.0.x or 2025.1.0 (prior to 2025.1.1)
-
Confirm 3DM file handling capabilityCheck if the atf_api.dll is loaded in AutoCAD by opening Task Manager while AutoCAD is running, going to the Details tab, and looking for atf_api.dll, or check the bin directory for the presence of atf_api.dllAffected if The DLL is present in the AutoCAD 2025 installation directory
You are affected if any Autodesk AutoCAD 2025-based product (including vertical products like Civil 3D, Architecture, etc.) is installed with a version lower than 2025.1.1 and the atf_api.dll component is present.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2025.1.1
Apply the vendor patch when available, and in the interim, avoid opening untrusted 3DM files from unknown or untrusted sources. Organizations should maintain current AutoCAD installations and monitor Autodesk security advisories.
AutoCAD 2025.1.1 (and corresponding versions for AutoCAD Industry products: Advance Steel, Architecture, Civil 3D, Electrical, Mechanical, MEP, Plant 3D)
- Verify current AutoCAD version by opening the application and navigating to Help > About AutoCAD
- Close all AutoCAD instances and any related services
- Back up custom settings, scripts, and any custom files (LISP, ARX, etc.)
- Download AutoCAD 2025.1.1 or later from the official Autodesk website (www.autodesk.com) or through your Autodesk Account
- Run the installer as an administrator
- Follow the on-screen installation prompts to complete the upgrade
- After installation, restart AutoCAD and verify that the version shows 2025.1.1 or later
- Test critical workflows with 3DM files to ensure normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9826 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-9826 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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