A vulnerability has been identified in JT2Go (All versions < V13.1.0.1), Teamcenter Visualization (All versions < V13.1.0.1).

published 2021-02-09 5 y ago modified 2026-06-17 4 mo ago also EUVD-2020-19529

cvss: 7.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits: 0; none known

A vulnerability has been identified in JT2Go (All versions < V13.1.0.1), Teamcenter Visualization (All versions < V13.1.0.1). Affected applications lack proper validation of user-supplied data when parsing of TGA files. This could result in an out of bounds write past the end of an allocated structure. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-12178)

Patch / fix

fixed in 2

siemens jt2go 13.1.0.1
siemens teamcenter_visualization 13.1.0.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-21-047-01 updated 2025-05-06 cvss 7.8

Open Design Alliance Drawings SDK (Update A)

Siemens JT2Go <V13.1.0.1
affected: fixed in V13.1.0.1, mitigation plm.automation.siemens.com
Siemens Teamcenter Visualization <V13.1.0.1
affected: fixed in V13.1.0.1, mitigation

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

Exploit prediction

0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.8	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	4.6	AV:L/AC:L/Au:N/C:P/I:P/A:P

Affected products

Siemens JT2Go
Siemens Teamcenter Visualization

Classification

Weakness

CWE-787 Out-of-bounds Write

References

cert-portal.siemens.com /productcert/pdf/ssa-663999.pdf
vendor-advisory
zerodayinitiative.com /advisories/ZDI-21-231/
third-party-advisory, vdb-entry

Sources

CVE List CVE-2020-27005
NVD CVE-2020-27005

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary