dbcve.org
RevitApplication · Autodesk

CVE-2026-1288

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to 2024.3.5 / 2025.4.5 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 RFA file, when converted to FormIt via “Convert RFA to FormIt” in Autodesk Revit, can force a NULL Pointer Dereference vulnerability. Successful exploitation may cause the application to crash, leading to a denial-of-service condition.

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 NULL pointer dereference vulnerability exists in Autodesk Revit's 'Convert RFA to FormIt' feature. When processing a maliciously crafted RFA file, the conversion process attempts to dereference a NULL pointer, causing the application to crash and resulting in a denial-of-service condition.

MitigationUsers should avoid opening or converting untrusted RFA files until Autodesk releases an official patch. Apply vendor-supplied security updates promptly when available.

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.5>= 2025, < 2025.4.5>= 2026, < 2026.4.1>= 2027, < 2027.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
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, go to Help > About Autodesk Revit, or check Add/Remove Programs to find the installed version number
    Affected if version falls within any of these ranges: 2024.x before 2024.3.5, 2025.x before 2025.4.5, 2026.x before 2026.4.1, or 2027.x before 2027.1
  2. Verify 'Convert RFA to FormIt' feature availability
    Locate the Convert RFA to FormIt feature in the Revit interface (typically under Add-Ins or the FormIt plugin menu). Check if the feature ribbon/button is present and accessible
    Affected if the Convert RFA to FormIt feature exists and is accessible in the installed version
  3. Confirm FormIt plugin integration
    Check if the Autodesk FormIt plugin is installed and enabled within Revit (look for FormIt-related entries in the Add-Ins ribbon tab or plugin manager)
    Affected if FormIt plugin integration is present, enabling the conversion workflow that triggers the vulnerability
  4. Assess RFA file processing exposure
    Review recent conversion history or logs to determine if the Convert RFA to FormIt feature has been used, or check for presence of RFA files from untrusted sources in project directories
    Affected if the Convert RFA to FormIt feature has been used, or users process RFA files from untrusted or external sources

A user is affected if they have Revit version 2024.x before 2024.3.5, 2025.x before 2025.4.5, 2026.x before 2026.4.1, or 2027.x before 2027.1, AND the Convert RFA to FormIt feature is accessible and has been or could be used to process RFA 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.5 / 2025.4.5 / 2026.4.1 or later
Fixed in 2024.3.52025.4.52026.4.1
Interim mitigation

Users should avoid opening or converting untrusted RFA files until Autodesk releases an official patch. Apply vendor-supplied security updates promptly when available.

Recommended fix High confidence

Revit 2024.3.5, 2025.4.5, 2026.4.1, or 2027.1 (depending on your current release line)

  1. Back up all Revit projects and user settings before proceeding with the upgrade
  2. Navigate to Autodesk Account or the official Autodesk support page to download the appropriate update
  3. Download the fixed version matching your current release line (2024.3.5, 2025.4.5, 2026.4.1, or 2027.1)
  4. Run the installer with administrator privileges
  5. Follow the on-screen installation prompts to complete the update
  6. Restart the workstation after installation completes
  7. Launch Revit and verify the application starts without errors
  8. Test the "Convert RFA to FormIt" functionality with a known-good RFA file to confirm the vulnerability is resolved
Caveat Minor version updates typically include backward-compatible fixes; however, always review Autodesk release notes for any migration considerations before upgrading production environments

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

Fix this in Revit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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