CVE-2024-11608: A maliciously crafted SKP file, when linked or imported into Autodesk Revit, can be used to cause a Heap-based Overflow.
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A maliciously crafted SKP file, when linked or imported into Autodesk Revit, can be used to cause a Heap-based Overflow. 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.
- Published
- Dec 9, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- CWE-122
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · autodesk
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| autodesk | revit | cpe:2.3:a:autodesk:revit |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (autodesk). Independent of NVD's CPE analysis and usually ahead of it.
Autodesk Revit
- 2025 and later · before 2025.4affected
- 2024 and later · before 2024.3.2affected
- 2023 and later · before 2023.1.7affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- autodesk revit2023 and later · before 2023.1.7
- autodesk revit2024 and later · before 2024.3.2
- autodesk revit2025 and later · before 2025.4
Same product
autodesk: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-8325PDF File Parsing Vulnerabilities in Certain Autodesk Desktop Products31Monitor
- CVE-2026-1289PDF File Parsing Vulnerabilities in Certain Autodesk Desktop Products31Monitor
- CVE-2026-11803PDF File Parsing Vulnerabilities in Certain Autodesk Desktop Products31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-11268Dec 9, 2024 · PDF File Parsing Vulnerability in Autodesk Revit22Monitor
- ← EarlierCVE-2024-11454Dec 9, 2024 · Untrusted Search Path vulnerability in Autodesk Revit31Monitor
- Later →CVE-2025-1273Apr 15, 2025 · PDF File Parsing Heap-Based Overflow Vulnerability31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-1273127 days apartPDF File Parsing Heap-Based Overflow Vulnerability31Monitor
- CVE-2025-1656127 days apartPDF File Parsing Heap-based Overflow Vulnerability31Monitor
- CVE-2025-2497127 days apartDWG File Parsing Stack-Based Buffer Vulnerability31Monitor
- CVE-2025-5040213 days apartRTE File Parsing Heap-Based Overflow Vulnerability31Monitor
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-122 · Heap-based Buffer OverflowCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.