dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2026-1283

HIGH · 7.8 CVSS v3.1 Published 2026-01-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A heap-based buffer overflow vulnerability exists in the EPRT file reading procedure of SOLIDWORKS eDrawings versions 2025-2026. When parsing specially crafted EPRT files, the application fails to properly validate buffer boundaries, allowing an attacker to overwrite heap memory and potentially execute arbitrary code.

MitigationAvoid opening EPRT files from untrusted or unknown sources. Apply vendor-provided patches for SOLIDWORKS eDrawings 2025 and 2026 when released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed eDrawings version
    Open eDrawings and navigate to Help > About eDrawings, or locate the installation directory and check file properties of the main executable (typically named eDrawings.exe)
    Affected if The version displayed falls within the 2025 to 2026 range, meaning the application is potentially vulnerable when processing EPRT files
  2. Verify EPRT file association
    Check if .eprt files are associated with eDrawings by right-clicking any EPRT file and viewing the 'Opens with' program, or check File > Open dialog filters in eDrawings
    Affected if EPRT files are configured to open with eDrawings versions 2025-2026, exposing the application to the vulnerable code path
  3. Inspect for recent crash logs
    Look for crash dump files or error logs in the eDrawings application data folder (typically under %APPDATA%\SOLIDWORKS\eDrawings\ or installation logs)
    Affected if Crash logs or dump files exist from recent EPRT file openings, which may indicate exploitation attempts or successful triggering of the buffer overflow

A user is affected if they have eDrawings version 2025 or 2026 installed and routinely open EPRT files from any source, as the vulnerability triggers during EPRT file parsing without additional user-configurable conditions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid opening EPRT files from untrusted or unknown sources. Apply vendor-provided patches for SOLIDWORKS eDrawings 2025 and 2026 when released.

Recommended fix Moderate confidence

SOLIDWORKS Desktop latest release (newer than 2026)

  1. 1. Verify the current installed version of SOLIDWORKS eDrawings by opening the application and navigating to Help > About SOLIDWORKS eDrawings.
  2. 2. Since the vulnerability affects SOLIDWORKS Desktop 2025 and 2026, obtain the latest available release of SOLIDWORKS Desktop from the official 3DS.com customer portal or through your organization's software distribution channel.
  3. 3. Download the installer for the most recent SOLIDWORKS Desktop release that includes the security fix for CVE-2026-1283.
  4. 4. Close all SOLIDWORKS applications and eDrawings instances before running the installer.
  5. 5. Run the installer with administrator privileges and follow the on-screen prompts to complete the upgrade.
  6. 6. After installation, verify the new version by checking Help > About SOLIDWORKS eDrawings.
  7. 7. Test that EPRT files open correctly in the updated version.
  8. 8. Distribute the updated software to all affected users within the organization.
Caveat Minor: Verify compatibility with existing workflows and any custom eDrawings API integrations after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1283 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1283 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data