CVE-2025-1274

RCS File Parsing Out-of-Bounds Write Vulnerability

HIGH
7.8
CVSS Score
Published: April 15, 2025 at 08:58 PM UTC
Updated: June 17, 2026 at 08:38 AM UTC
11 products affected across 1 vendorAutoCADAutoCAD ElectricalCivil 3D

Using Revit by Autodesk?

Get instant alerts when new vulnerabilities affect Revit - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2023 ≤ v < 2023.1.82024 ≤ v < 2024.1.82025 ≤ v < 2025.1.3202320242025
Affected range stops below 2023.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.3, so it looks safe — our inference, not a vendor statement
2023 ≤ v < 2023.1.82024 ≤ v < 2024.1.82025 ≤ v < 2025.1.3202320242025
Affected range stops below 2023.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.3, so it looks safe — our inference, not a vendor statement
2023 ≤ v < 2023.1.82024 ≤ v < 2024.1.82025 ≤ v < 2025.1.3202320242025
Affected range stops below 2023.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.3, so it looks safe — our inference, not a vendor statement
2023 ≤ v < 2023.1.82024 ≤ v < 2024.1.82025 ≤ v < 2025.1.3202320242025
Affected range stops below 2023.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.3, so it looks safe — our inference, not a vendor statement
2023 ≤ v < 2023.1.82024 ≤ v < 2024.1.82025 ≤ v < 2025.1.3202320242025
Affected range stops below 2023.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.3, so it looks safe — our inference, not a vendor statement
2023 ≤ v < 2023.1.82024 ≤ v < 2024.1.82025 ≤ v < 2025.1.3202320242025
Affected range stops below 2023.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.3, so it looks safe — our inference, not a vendor statement
2023 ≤ v < 2023.1.82024 ≤ v < 2024.1.82025 ≤ v < 2025.1.3202320242025
Affected range stops below 2023.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.3, so it looks safe — our inference, not a vendor statement
2023 ≤ v < 2023.1.82024 ≤ v < 2024.1.82025 ≤ v < 2025.1.3202320242025
Affected range stops below 2023.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.3, so it looks safe — our inference, not a vendor statement
2023 ≤ v < 2023.1.82024 ≤ v < 2024.1.82025 ≤ v < 2025.1.3202320242025
Affected range stops below 2023.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.3, so it looks safe — our inference, not a vendor statement
2023 ≤ v < 2023.1.82024 ≤ v < 2024.1.82025 ≤ v < 2025.1.3202320242025
Affected range stops below 2023.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2025.1.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHautodesk
Attack Vector
LOCAL
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card