Teamcenter Visualization
Siemens- Product type
- Other
- Catalog vulnerabilities
- 93
Severity across 93 analyzed records
en
Verify to analyze this security profile
As of 09/13/2026, within CyStack's analyzed data, Teamcenter Visualization has 0 security vulnerabilities published in the last 90 days. Of these, 0 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of Teamcenter Visualization and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2023-7066Siemens Teamcenter Visualization and JT2Go Out-of-bounds Read | Exploitation statusNot known exploited | FixYes | Published08/12/2024 | SeverityHigh |
CVE-2021-38405Siemens Solid Edge, JT2Go, and Teamcenter Visualization Improper Restriction of Operations within the Bounds of a Memory Buffer | Exploitation statusNot confirmed | FixYes | Published11/21/2023 | SeverityHigh |
CVE-2023-1709Datalogics Library APDFL Stack-based Buffer Overflow | Exploitation statusNot known exploited | FixYes | Published06/07/2023 | SeverityHigh |
CVE-2021-44017 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-44015 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-44013 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-44012 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-44011 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-44010 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-44009 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-44008 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-44007 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-44006 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-44005 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-44004 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-44003 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-44001 | Exploitation statusNot confirmed | FixNot confirmed | Published12/14/2021 | SeverityUnknown |
CVE-2021-33738 | Exploitation statusNot confirmed | FixNot confirmed | Published08/10/2021 | SeverityUnknown |
CVE-2021-33717 | Exploitation statusNot confirmed | FixNot confirmed | Published08/10/2021 | SeverityUnknown |
CVE-2021-34333 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34332 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34331 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34330 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34329 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34328 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34327 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34326 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34325 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34324 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34323 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34322 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34321 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34320 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34319 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34318 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34317 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34316 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34315 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34314 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34313 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34312 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34311 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34310 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34309 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34308 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34307 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34306 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34305 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34304 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34303 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34302 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34301 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34300 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34299 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34298 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34297 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34296 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34295 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34294 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34293 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34292 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-34291 | Exploitation statusNot confirmed | FixNot confirmed | Published07/13/2021 | SeverityUnknown |
CVE-2021-27390 | Exploitation statusNot confirmed | FixNot confirmed | Published06/08/2021 | SeverityUnknown |
CVE-2020-27008 | Exploitation statusNot confirmed | FixNot confirmed | Published02/09/2021 | SeverityUnknown |
CVE-2020-27007 | Exploitation statusNot confirmed | FixNot confirmed | Published02/09/2021 | SeverityUnknown |
CVE-2020-28394 | Exploitation statusNot confirmed | FixNot confirmed | Published02/09/2021 | SeverityUnknown |
CVE-2020-26999 | Exploitation statusNot confirmed | FixNot confirmed | Published02/09/2021 | SeverityUnknown |
CVE-2020-27000 | Exploitation statusNot confirmed | FixNot confirmed | Published02/09/2021 | SeverityUnknown |
CVE-2020-27006 | Exploitation statusNot confirmed | FixNot confirmed | Published02/09/2021 | SeverityUnknown |
CVE-2020-27001 | Exploitation statusNot confirmed | FixNot confirmed | Published02/09/2021 | SeverityUnknown |
CVE-2020-27003 | Exploitation statusNot confirmed | FixNot confirmed | Published02/09/2021 | SeverityUnknown |
CVE-2020-27005 | Exploitation statusNot confirmed | FixNot confirmed | Published02/09/2021 | SeverityUnknown |
CVE-2020-27004 | Exploitation statusNot confirmed | FixNot confirmed | Published02/09/2021 | SeverityUnknown |
CVE-2020-26998 | Exploitation statusNot confirmed | FixNot confirmed | Published02/09/2021 | SeverityUnknown |
CVE-2020-27002 | Exploitation statusNot confirmed | FixNot confirmed | Published02/09/2021 | SeverityUnknown |
CVE-2020-26996 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26994 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26993 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26995 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26992 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-28383 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26982 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26991 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26990 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26987 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26983 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26988 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26984 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26985 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26986 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26989 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26981 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CVE-2020-26980 | Exploitation statusNot confirmed | FixNot confirmed | Published01/12/2021 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan