CVE-2020-26995
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: jt2go 13.1.0; teamcenter visualization 13.1.0 upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
A vulnerability has been identified in JT2Go (All versions < V13.1.0), Teamcenter Visualization (All versions < V13.1.0). Affected applications lack proper validation of user-supplied data when parsing of SGI and RGB 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-11992)
- weakness
- CWE-787: Out-of-bounds Write
- affected
- Siemens JT2Go; Siemens Teamcenter Visualization
- published ranges
- siemens jt2go < 13.1.0; siemens teamcenter visualization < 13.1.0
- first unaffected version, by branch
- jt2go 13.1.0; teamcenter visualization 13.1.0
- assigned by
- siemens
- published
- 2021-01-12
check us cert-portal.siemens.com zerodayinitiative.com zerodayinitiative.com zerodayinitiative.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 14 Apr 2021 | 0.01819 | |
| 6 Jan 2022 | 0.07673 | |
| 4 Feb 2022 | 0.23331 | crossed 0.10 |
| 1 Apr 2022 | 0.02509 | crossed 0.10 |
| 7 Mar 2023 | 0.01696 | scoring model v2023.03.01 |
| 17 Mar 2025 | 0.02532 | scoring model v2025.03.14 |
| 30 Mar 2025 | 0.02532 | |
| 14 May 2026 | 0.02583 | |
| 15 Jun 2026 | 0.03492 | scoring model v2026.06.15 |
| 7 Oct 2026 | 0.03644 |
22 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.04 on 2026-10-07 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: jt2go 13.1.0; teamcenter visualization 13.1.0. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2020-26995', '2026-11-01T23:59:59.999999Z', now());