dbcve.org
RevitApplication · Autodesk

CVE-2024-11268

MEDIUM · 5.5 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 2024.3.1 / 2025.4 or later.
See remediation →
58/100
Remediation priority · Elevated
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 PDF file, when parsed through Autodesk Revit, can force an Out-of-Bounds Read. A malicious actor can leverage this vulnerability to cause a crash or could lead to an arbitrary memory leak.

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 vulnerability in Autodesk Revit's PDF parsing functionality allows specially crafted PDF files to trigger an out-of-bounds memory read. This memory access violation can cause the application to crash or leak arbitrary memory contents, potentially exposing sensitive information or enabling further exploitation.

MitigationRestrict or disable PDF file handling in Autodesk Revit until the vendor releases an official patch. Avoid opening PDF files from untrusted or unknown sources within the application.

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
RevitApplication
Affected:>= 2024, < 2024.3.1>= 2025, < 2025.4

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 Revit version
    Open Autodesk Revit, then navigate to Help > About Autodesk Revit to view the exact version and build number. Alternatively, open Windows Control Panel > Programs and Features and locate Autodesk Revit in the list to see the installed version.
    Affected if The version is 2024.x (prior to 2024.3.1) or 2025.x (prior to 2025.4), placing it within the affected ranges of >=2024,<2024.3.1 or >=2025,<2025.4
  2. Confirm PDF import capability is present
    In the Autodesk Revit interface, go to the Insert tab on the ribbon and look for PDF-related options under the Import or Link categories. Check if PDF files can be inserted or linked into the model.
    Affected if PDF import or link functionality is visible and accessible in the application, indicating the vulnerable PDF parsing component is present and enabled
  3. Check for PDF-related binaries
    Navigate to the Revit installation directory (typically C:\Program Files\Autodesk\Revit <Version\) and search for DLL files related to PDF handling, such as those containing 'PDF' in the filename.
    Affected if PDF-handling DLL files exist in the Revit installation directory, confirming the parsing component is present on the system
  4. Identify active PDF import usage
    Review recent Revit projects or the current open model to determine if PDF files have been imported or linked. Check the Manage > Project Files panel or the Project Browser for any imported PDFs.
    Affected if PDF files have been imported, linked, or attached within any Revit project, indicating the vulnerable code path has been exercised

The environment is affected if Autodesk Revit version 2024.0-2024.3.0 or 2025.0-2025.3 is installed AND the PDF import/parsing functionality is available or has been used to handle PDF 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 2024.3.1 / 2025.4 or later
Fixed in 2024.3.12025.4
Interim mitigation

Restrict or disable PDF file handling in Autodesk Revit until the vendor releases an official patch. Avoid opening PDF files from untrusted or unknown sources within the application.

Recommended fix High confidence

Revit 2024.3.1 or later; Revit 2025.4 or later

  1. Navigate to the Autodesk Account portal or the official Autodesk support website
  2. Locate the Downloads section for Autodesk Revit
  3. Download Autodesk Revit version 2024.3.1 or later (for 2024.x users)
  4. Download Autodesk Revit version 2025.4 or later (for 2025.x users)
  5. Run the installer and follow the prompts to install the updated version
  6. Restart the application after installation completes
  7. Verify the installed version matches the fixed release

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

Fix this in Revit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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