Affects widely deployed PTC Windchill PDMLink and FlexPLM; critical RCE via deserialization could disrupt manufacturing workflows.
CVE-2026-4681
RCE via untrusted data deserialization in PTC Windchill/FlexPLM.
Is CVE-2026-4681 being exploited?
Not confirmed. CVE-2026-4681 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.76% probability of exploitation in the next 30 days.
How severe is CVE-2026-4681?
CVE-2026-4681 is rated Critical with a CVSS score of 9.3. 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-4681?
Yes. A fix has been recorded for CVE-2026-4681. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-4681 affect?
CVE-2026-4681 affects PTC Windchill PDMLink (versions: 11.0 M030, 11.1 M020, 11.2.1.0, 12.0.2.0, 12.1.2.0, 13.0.2.0, 13.1.0.0, 13.1.1.0, 13.1.2.0, 13.1.3.0), PTC FlexPLM (versions: 11.0 M030, 11.1 M020, 11.2.1.0, 12.0.0.0, 12.0.2.0, 12.0.3.0, 12.1.2.0, 12.1.3.0, 13.0.2.0, 13.0.3.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-4681?
Patch when available; validate/limit serialized data.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via crafted serialized object on Windchill/FlexPLM servers.
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.