Skip to main content
No exploitation reportedFix available

CVE-2020-26999

No exploitation reported by the sources we read.

  • Published2021-02-09
  • Fixed in13.1.0.2
  • WeaknessCWE-125

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A vulnerability has been identified in JT2Go (All versions < V13.1.0.2), Teamcenter Visualization (All versions < V13.1.0.2). Affected applications lack proper validation of user-supplied data when parsing of PAR files. This could result in a memory access past the end of an allocated buffer. An attacker could leverage this vulnerability to leak information. (ZDI-CAN-12042)

Timeline

dates in UTC
  1. 2021-02-0917:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-26999?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-26999?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Siemens jt2go
BranchAffectedFixed in
13.1< 13.1.0.213.1.0.2
Siemens teamcenter visualization
BranchAffectedFixed in
13.1< 13.1.0.213.1.0.2

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • ICSA-21-147-04 CISA2 known affected

    Siemens JT2Go and Teamcenter Visualization

    JT2Go · Teamcenter Visualization

  • ICSA-21-040-06 CISA2 known affected

    ICSA-21-040-06_Siemens JT2Go and Teamcenter Visualization (Update A)

    JT2Go · Teamcenter Visualization

Full record on NVD

Fix

  1. Update Siemens jt2go to 13.1.0.2
  2. Vendor fix CISA ICSA-21-147-04 · 1 productUpdate to V13.1.0.2 or later version
  3. Mitigation from the vendor CISA ICSA-21-147-04 · 2 productsAvoid to open untrusted files from unknown sources in JT2Go and Teamcenter Visualization
  4. Mitigation from the vendor CISA ICSA-21-147-04 · 2 productsAs a general security measure, Siemens strongly recommends to protect network access to devices with appropriate mechanisms. In order to operate the devices in a protected IT environment, Siemens recommends to configure the environment according to Siemens' operational guidelines for Industrial Sec…

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.17.8read 2026-10-23
  • NVDCVSS 2.04.6read 2026-10-23
  • CNAweakness (CWE)CWE-125read 2026-10-23
  • NVDweakness (CWE)CWE-125read 2026-10-23
  • FIRST EPSSEPSS score0.7 %2026-10-22

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2021-02-09
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2020-26999?

A vulnerability has been identified in JT2Go (All versions < V13.1.0.2), Teamcenter Visualization (All versions < V13.1.0.2). Affected applications lack proper validation of user-supplied data when parsing of PAR files. This could result in a memory access past the end of an allocated buffer. An attacker could leverage this vulnerability to leak information. (ZDI-CAN-12042)

Is CVE-2020-26999 actively exploited?

Active exploitation of CVE-2020-26999 has not been confirmed. Its EPSS score was 0.7% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-26999?

CVE-2020-26999 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running JT2Go (All versions < V13.1.0.2)? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month