LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1283: Heap-based Buffer Overflow vulnerability affecting the EPRT file reading procedure in SOLIDWORKS eDrawings from Release SOLIDWORKS Desktop 2025 through Release SOLIDWORKS Desktop 2026

A Heap-based Buffer Overflow vulnerability affecting the EPRT file reading procedure in SOLIDWORKS eDrawings from Release SOLIDWORKS Desktop 2025 through Release SOLIDWORKS Desktop 2026 could allow an attacker to execute arbitrary code while opening a specially crafted EPRT file.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-1283 is a high-severity flaw in SOLIDWORKS eDrawings. If a user opens a malicious EPRT file, an attacker could run code on that user’s workstation. The main business risk is compromise of engineering workstations and sensitive design data through file-based social engineering.

Executive priority

Treat as a priority workstation risk for engineering environments. It is not described as remotely exploitable without user action, but a successful lure could compromise valuable design systems and data.

Technical view

The issue is a heap-based buffer overflow in the EPRT file reading procedure of Dassault Systèmes SOLIDWORKS eDrawings. CVSS 3.1 is 7.8, with local attack vector, low complexity, no privileges required, and user interaction required. Successful exploitation could affect confidentiality, integrity, and availability.

Likely exposure

Organizations using SOLIDWORKS eDrawings in SOLIDWORKS Desktop 2025 or 2026 should review exposure, especially teams receiving EPRT files from external parties. The provided affected list specifically names Release SOLIDWORKS Desktop 2025 SP0 and 2026 SP0, with default status otherwise marked unaffected.

Exploitation context

The attack requires convincing a user to open a specially crafted EPRT file. The source bundle does not indicate active exploitation, public exploit availability, or inclusion in CISA KEV.

Researcher notes

Evidence is limited to the CVE record and Dassault advisory reference in the source bundle. Do not assume affected builds beyond the named SOLIDWORKS Desktop 2025/2026 eDrawings scope. No source in the bundle confirms exploitation in the wild or a specific patch level.

Mitigation direction

  • Check Dassault Systèmes’ advisory for fixed versions or vendor-recommended mitigations.
  • Restrict opening EPRT files from untrusted or unexpected sources.
  • Prioritize updates for engineering workstations handling external design files.
  • Use endpoint controls to limit impact of code execution from user applications.

Validation and detection

  • Inventory SOLIDWORKS eDrawings installations and versions across workstations.
  • Identify systems running SOLIDWORKS Desktop 2025 SP0 or 2026 SP0.
  • Review file-handling workflows for externally supplied EPRT files.
  • Confirm remediation status against Dassault Systèmes’ published advisory.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1283 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-1283Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Dassault SystèmesSOLIDWORKS eDrawingsRelease SOLIDWORKS Desktop 2025 SP0, Release SOLIDWORKS Desktop 2026 SP0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.