CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Called exploited 7 days after disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listing7d
- Last sighting2mo
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Jun 25, 2026
- EUVDENISA, European Unionlisted Jun 25, 2026
- VulnCheck KEVcommercial researchlisted Jun 25, 2026
- CIRCLaggregator, mirrors the abovelisted Jun 25, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationwebflow.sysdig.com/blog/security-briefing-august-2026
- reported exploitationresearch.checkpoint.com/2026/24th-august-threat-intelligence
- reported exploitationreliaquest.com/blog/clop-returns-with-custom-implant-in-mass
- reported exploitationforesiet.com/blog/cl0p-windchill-flexplm-cve-2026-12569/
- reported exploitationwww.recordedfuture.com/blog/july-2026-cve-landscape
- reported exploitationcydome.io/maritime-cybersecurity-bulletin-july-31st-2026/
13 public reports collected from VulnCheck and CIRCL, first on Jun 25, 2026. Each links to its original source. We have not verified them.
Description
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
Required action (CISA)
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
