# CVE-2026-14255: IFC File Parsing Uncontrolled Recursion in Certain Autodesk Products

> Attackers can cause application crashes by tricking users into opening maliciously crafted IFC files in Autodesk products.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-3v2g-r42x-pw7h

## What is CVE-2026-14255?

CVE-2026-14255 is a medium-severity denial of service vulnerability in Autodesk Revit, published on 2 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A maliciously crafted IFC file, when parsed through certain Autodesk products, can trigger an Uncontrolled Recursion vulnerability. A malicious actor may leverage this vulnerability to cause the application to terminate unexpectedly, resulting in a denial-of-service. Exploitation requires a user to open a specially crafted IFC file.

Weakness: CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2026-14255?


## How do I fix CVE-2026-14255?

No fix has been published for CVE-2026-14255 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14255 being exploited?

There is no known exploitation of CVE-2026-14255 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14255 and fix it if it is affected.

What it is: CVE-2026-14255 is a medium-severity denial of service vulnerability in Autodesk Revit, published on 2 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-14255 in the wild and no public exploit code.

Affected product: Autodesk Revit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14255/ (Markdown: https://insights.sbomify.com/CVE-2026-14255/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14255
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14255
- OSV: https://osv.dev/vulnerability/CVE-2026-14255

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14255/
Summaries are generated and may contain mistakes; the official description above is the record.