Skip to main content
No exploitation reportedFix available

CVE-2021-44014

No exploitation reported by the sources we read.

  • Published2021-12-14
  • Fixed in11.1.1.0
  • WeaknessCWE-416

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 JT Open (All versions < V11.1.1.0), JT Utilities (All versions < V13.1.1.0), Solid Edge (All versions < V2023). The Jt1001.dll contains a use-after-free vulnerability that could be triggered while parsing specially crafted JT files. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-15057, ZDI-CAN-19081)

Timeline

dates in UTC
  1. 2021-12-1412:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 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-2021-44014?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2021-44014?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Siemens jt open toolkit
BranchAffectedFixed in
11.1< 11.1.1.011.1.1.0
Siemens jt utilities
BranchAffectedFixed in
13.1< 13.1.1.013.1.1.0
Siemens jt2go
BranchAffectedFixed in
13.2< 13.2.0.513.2.0.5

2 more products in the sources.

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-350-10 CISA2 known affected

    Siemens JT2Go and Teamcenter Visualization

    JT2Go · Teamcenter Visualization

Full record on NVD

Fix

  1. Update Siemens jt open toolkit to 11.1.1.0
  2. Vendor fix CISA ICSA-21-350-10 · 1 productUpdate to V13.2.0.5 or later version
  3. Mitigation from the vendor CISA ICSA-21-350-10 · 2 productsAvoid to open untrusted files from unknown sources in JT2Go and Teamcenter Visualization

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

  • CNACVSS 3.17.8read 2026-10-23
  • NVDCVSS 3.17.8read 2026-10-23
  • NVDCVSS 2.06.8read 2026-10-23
  • CNAweakness (CWE)CWE-416read 2026-10-23
  • NVDweakness (CWE)CWE-416read 2026-10-23
  • FIRST EPSSEPSS score1.6 %2026-10-23

Technical details

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

Frequently asked questions

What is CVE-2021-44014?

A vulnerability has been identified in JT Open (All versions < V11.1.1.0), JT Utilities (All versions < V13.1.1.0), Solid Edge (All versions < V2023). The Jt1001.dll contains a use-after-free vulnerability that could be triggered while parsing specially crafted JT files. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-15057, ZDI-CAN-19081)

Is CVE-2021-44014 actively exploited?

Active exploitation of CVE-2021-44014 has not been confirmed. Its EPSS score was 1.6% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2021-44014?

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

Running JT Open (All versions <? 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