CVE-2024-26276

MEDIUM
5.5
CVSS Score
Published: April 9, 2024 at 08:34 AM UTC
Updated: June 17, 2026 at 07:17 AM UTC
3 products affected across 1 vendorTeamcenter VisualizationJT2GoParasolid

Using JT2Go by Siemens?

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

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

Description

A vulnerability has been identified in JT2Go (All versions < V2312.0004), Parasolid V35.1 (All versions < V35.1.254), Parasolid V36.0 (All versions < V36.0.207), Parasolid V36.1 (All versions < V36.1.147), Teamcenter Visualization V14.2 (All versions < V14.2.0.12), Teamcenter Visualization V14.3 (All versions < V14.3.0.9), Teamcenter Visualization V2312 (All versions < V2312.0004). The affected application contains a stack exhaustion vulnerability while parsing a specially crafted X_T file. This could allow an attacker to cause denial of service condition.

Affected

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

v < 2312.0004v < V2312.0004
Affected range stops below V2312.0004, so it looks safe — our inference, not a vendor statement
v < V35.1.254v < V36.0.207v < V36.1.14735.1 ≤ v < 35.1.25436.0 ≤ v < 36.0.20736.1 ≤ v < 36.1.14735.136.036.1
Affected range stops below 35.1.254, so it looks safe — our inference, not a vendor statement
Affected range stops below 36.0.207, so it looks safe — our inference, not a vendor statement
Affected range stops below 36.1.147, so it looks safe — our inference, not a vendor statement
Affected range stops below V35.1.254, so it looks safe — our inference, not a vendor statement
Affected range stops below V36.0.207, so it looks safe — our inference, not a vendor statement
Affected range stops below V36.1.147, so it looks safe — our inference, not a vendor statement
v < V14.2.0.12v < V14.3.0.9v < V2312.000414.2 ≤ v < 14.2.0.1214.3 ≤ v < 14.3.0.92312.0 ≤ v < 2312.0004
Affected range stops below V14.2.0.12, so it looks safe — our inference, not a vendor statement
Affected range stops below V14.3.0.9, so it looks safe — our inference, not a vendor statement
Affected range stops below V2312.0004, 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 automatablePartial impact

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

CVSS

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

Quick Info

StatusANALYZED
CWE
CWE-770

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