CVE-2026-12569: PTC Windchill And FlexPLM

What is CVE-2026-12569?

A critical remote code execution (RCE) vulnerability has been reported in PTC Windchill PDMlink and PTC FlexPLM. The vulnerability may be exploited through the deserialization of untrusted data. * This advisory also applies to all CPS versions * The identified vulnerability also impacts Windchill and FlexPLM releases prior to 11.0 M030

CVSS9.8 NVD 3.1

SeverityCRITICAL

Exploitation In the wild In CISA KEV

EPSS41% · P99

Triage statusActive Exploit

ActionPatch immediately

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWECWE-20

NVD published2026-06-18

NVD last modified2026-08-01

Timeline

2026-06-18Published to the U.S. National Vulnerability Database (NVD)
2026-06-25Added to the CISA Known Exploited Vulnerabilities (KEV) catalog
2026-06-28CISA federal remediation deadline (BOD 22-01)
2026-08-01NVD record last updated

CISA Known Exploited Vulnerability

PTC Windchill and FlexPLM Improper Input Validation Vulnerability

Added to KEV2026-06-25

Federal patch deadline2026-06-28

Known ransomware useKnown

Affected product

PTC Windchill And FlexPLM

NVD also lists CPE entries for: Ptc Flexplm, Ptc Windchill Pdmlink

Remediation Steps

Refer to CISA Known Exploited Vulnerabilities catalog for vendor-specific remediation guidance
Apply patches provided by the affected vendor
Monitor systems for signs of compromise
Verify that systems are no longer vulnerable before returning to production

References

Referenced in our briefings & reports

Vulnerability Priority Report – Week 3 of July 2026 (July 20 – 26)
Vulnerability Priority Report – Week 2 of July 2026 (July 13 – 19)
Vulnerability Priority Report – Week 1 of July 2026 (July 6 – 12)
Vulnerability Priority Report – Week 5 of June 2026 (June 29 – July 5)
Vulnerability Priority Report – Week 4 of June 2026 (June 22 – 28)

Browse all tracked CVEs in the defend.network CVE database →

🤖 This CVE page is generated by defend.network from NVD, CISA KEV, EPSS, and our verified daily briefings. Severity and exploitation data come from official sources; always verify remediation steps against the official vendor advisory before acting in production.