Critical RCE in widely deployed PTC PLM products (Windchill, FlexPLM) can lead to full server compromise across manufacturing and engineering infrastructures; high-impact for many enterprises.
CVE-2026-77645
Critical RCE in PTC Windchill and FlexPLM via deserialization.
Is CVE-2026-77645 being exploited?
Not confirmed. CVE-2026-77645 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-77645?
CVE-2026-77645 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-77645?
Not known from our data. No patch reference has been recorded for CVE-2026-77645, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-77645 affect?
CVE-2026-77645 affects PTC Windchill, PTC FlexPLM. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-77645?
Isolate PLM from public networks, apply vendor patch/mitigations when available, restrict access and monitor logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution enabling full server compromise, data theft, and lateral movement from network-exposed PLM instances.
Immediate action required
- affected11.0 M030
- affected11.1 M020
- affected11.2.1.0
- affected12.0.0.0
- affected12.0.2.0
- affected12.0.3.0
- affected12.1.2.0
- affected12.1.3.0
- affected13.0.2.0
- affected13.0.3.0
- affected11.0 M030
- affected11.1 M020
- affected11.2.1.0
- affected12.0.2.0
- affected12.1.2.0
- affected13.0.2.0
- affected13.1.0.0
- affected13.1.1.0
- affected13.1.2.0
- affected13.1.3.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.