Skip to main content
VulnerabilityPublished

CVE-2026-11803: A maliciously crafted PDF file, when parsed through Autodesk Revit, can force an Out-of-Bounds Read

Source GCVE Database

0
Authoritative record:CVE-2026-11803· High 7.8

Not known to be exploited · CVSS 7.8 High · fixed in 2027.2.0 : patch Revit soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2027.2.0, 2026.5.0, 2025.4.6 +5
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Revit to 2027.2.0, 2026.5.0, 2025.4.6 or 2024.3.6; AutoCAD and AutoCAD LT and DWG TrueView to 2027.1.0, 2026.1.2, 2025.1.4 or 2024.1.9.

Affected software

ProductAffectedFixed in
AutodeskRevitAffected
  • >=2027.0.0 <2027.2.0
Fixed in
  • 2027.2.0
AutodeskRevitAffected
  • >=2026.0.0 <2026.5.0
Fixed in
  • 2026.5.0
AutodeskRevitAffected
  • >=2025.0.0 <2025.4.6
Fixed in
  • 2025.4.6
AutodeskRevitAffected
  • >=2024.0.0 <2024.3.6
Fixed in
  • 2024.3.6
AutodeskAutoCADAffected
  • >=2027.0.0 <2027.1.0
Fixed in
  • 2027.1.0
AutodeskAutoCADAffected
  • >=2026.0.0 <2026.1.2
Fixed in
  • 2026.1.2

Description

A maliciously crafted PDF file, when parsed through Autodesk Revit, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.

References

Community reviews

Loading reviews…