CADChain Blog
2026-11-12 13:18 News

Windchill Vulnerability CVE-2026-126325: PTC Patches the Fourth Critical Windchill and FlexPLM Flaw of 2026. What Engineering Teams Should Do About Their CAD Data | CADChain | CAD DRM & IP

PTC released a patch on 11 November 2026 for CVE-2026-126325, a critical remote code execution flaw in Windchill and FlexPLM, the product lifecycle management systems where many manufacturers keep their CAD models, drawings and bills of materials. The flaw needs no login and no user interaction, and it is the fourth critical code execution flaw PTC has disclosed in the two products this year.
According to the CVE record published by PTC, the flaw can be exploited through the deserialization of untrusted data. It is rated 9.2 (critical) under CVSS 4.0 and 9.0 under CVSS 3.1. Every listed Windchill release from 11.0 M030 up to 13.1.4.0 is affected, as are FlexPLM releases from 11.0 M030 up to 13.1.3.0. PTC says it has already patched the systems it hosts for customers, and it urges everyone running Windchill or FlexPLM on their own servers to apply the patch as soon as possible.
There is no public report that this new flaw has been exploited, and PTC has not said who found it. The urgency comes from the year so far. In June, attackers used a similar Windchill flaw, CVE-2026-12569, to plant web shells on PLM servers, and the Clop extortion group later named more than 40 organisations on its leak site. For companies whose design data lives in Windchill, this is the moment to patch, check for traces of the earlier campaign and ask what happens to their CAD files if the PLM server falls.
TL;DR: patch Windchill and FlexPLM now, then look back

CVE-2026-126325 is a critical, unauthenticated code execution flaw in PTC Windchill and FlexPLM, published and patched on 11 November 2026. PTC-hosted systems are patched; self-hosted ones are not until an administrator installs the fix described in PTC support article CS483249. It follows CVE-2026-4681 (March), CVE-2026-12569 (June, exploited and linked to Clop) and CVE-2026-77645 (August). Lesson for engineering teams: a PLM server is a single place where an attacker can reach thousands of design files at once, so patching speed, internet exposure and file-level protection of the CAD data itself all matter.

What exactly did PTC disclose on 11 November?

PTC published the CVE record at 15:02 UTC on 11 November, one day after reserving the number, and posted an update to its Windchill and FlexPLM Trust Center advisory at 10:30 Eastern time the same day. The update says a new security patch for CVE-2026-126325 is available, that it should be applied by a Windchill administrator, and that environments hosted by PTC have been patched on the customers' behalf, with no action required from them.
The technical description is short. PTC classifies the weakness as improper input validation (CWE-20) and deserialization of untrusted data (CWE-502). In plain terms, the server accepts data from a network request and turns it back into program objects without checking it well enough, which can let a crafted request run code on the server. The CVSS vector says the attack works over the network, needs no privileges and no user interaction, and is automatable. It also rates attack complexity as high, which means some conditions outside the attacker's control have to be met. That lowers the score slightly, but it does not make the flaw safe to leave.
The full list of fixed builds and the installation steps are in PTC support article CS483249, which requires a PTC eSupport login. We did not have access to it, so we do not list patch numbers here. Note one detail in the CVE record: Windchill 13.1.4.0 appears among the affected releases, so running the newest release line does not mean you are covered.

Why is this the fourth critical Windchill flaw of 2026?

PTC has now published four critical remote code execution flaws in Windchill and FlexPLM in under eight months, all involving deserialization of untrusted data. Only one of them is known to have been exploited, but that one was exploited at scale.
FlawPublishedSeverity (CVSS 3.1 / 4.0)Exploited?What PTC told customers
CVE-2026-468123 March 202610.0 / 9.3No confirmed exploitation, PTC said on 26 MarchApache and IIS rule blocking a publishing servlet, also on file and replica servers
CVE-2026-1256918 June 2026Critical / 9.3Yes: in CISA's exploited list since 25 June, ransomware use knownRemediation steps in June, patches on 14 July, repeated lists of attack indicators
CVE-2026-77645 (with SSRF flaw CVE-2026-77646)20 August 20269.0 / 9.2 (SSRF: 8.6 / 7.7)No exploitation reported by CISA in AugustListed in the same Trust Center advisory, details via PTC support
CVE-2026-12632511 November 20269.0 / 9.2No public report as of 12 November; not in CISA's exploited listPatch available, hosted systems already patched, self-hosted to patch now
The June case is the one to remember. On 25 June PTC told customers it had received "continued reports of heightened threat activity", and the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-12569 to its Known Exploited Vulnerabilities catalogue the same day, giving federal agencies three days to act. PTC's advisory then listed the attacker's command server, web shells dropped as JSP files in the Windchill login folder, a custom request header and a file called flst.txt that shows the attacker had listed files on the server.
From 12 August, Clop began naming victims it linked to the campaign, more than 40 organisations according to SecurityWeek, including Shell and Philips. Philips said an attempted attack on a specific company server was under control. In October, Dutch broadcaster BNR reported that Clop had published stolen data that included technical drawings of Philips MRI scanners. BORIS Inventor covered what that meant for engineering vaults in its article on the Clop PLM data leak.

Why is a PLM server such an attractive target?

A PLM system is built to be the single source of truth for product data. That makes it efficient for engineers and equally efficient for an attacker. One compromised server can give access to native CAD models, released drawings, bills of materials, change orders, supplier packages and the metadata that explains how everything fits together. Our report on ransomware gangs targeting design drawings and PDM data shows that extortion groups now advertise exactly this kind of data.
The June campaign also showed that the damage does not stop at files. Researchers at ReliaQuest, quoted by SecurityWeek in August, described web shells that mapped vault data and decrypted credentials stored on the Windchill server. Stolen service accounts can then open doors to directory services, ERP systems and file shares that trust the PLM server.
Windchill is not alone. In October Oracle shipped 43 fixes for its Agile PLM family, which we covered in our article on Oracle Agile PLM vulnerabilities, and a CVSS 10 flaw hit GitLab, where many teams keep design repositories. Engineering data platforms are now a mainstream target, not a niche one.
Keep CAD files protected even when a server is compromised. CADChain encrypts CAD files at file level, lets you grant and revoke access per user, logs every access and records ownership on a blockchain, so a stolen file stays locked and you can prove what is yours.

👉 See how CADChain protects CAD files

What does this mean for companies in the EU?

Several EU rules apply at once when a PLM server is breached. Under NIS2, many manufacturers of machinery, vehicles, electronics and other products are important entities. They must manage cyber risk and report significant incidents to their national CSIRT or authority, with an early warning within 24 hours. A compromised PLM server that leaks or disrupts product data can meet that threshold.
The Cyber Resilience Act matters on the vendor side. Since 11 September 2026, manufacturers of products with digital elements must report actively exploited vulnerabilities in their products, as we explained in Cyber Resilience Act reporting is live. For PLM customers, that means more and faster vendor notices, and a reason to make sure someone in your company actually reads them.
Then there is trade secret law. Under the EU Trade Secrets Directive, information only counts as a trade secret if its holder took reasonable steps to keep it secret. Leaving a known critical flaw unpatched on an internet-facing server that holds your design data is hard to defend as a reasonable step. Our trade secrets guide for deep tech startups explains the test, and tamper-proof audit trails help you show what you did and when.
One more change sits in the background: Schneider Electric agreed in October to buy PTC, as covered in our article on the Schneider Electric and PTC deal. The deal does not change today's advice, but during any ownership transition it is worth checking that the right people in your company still receive PTC's security notices.

What should engineering teams do now?

  1. Find every instance. List all Windchill and FlexPLM servers, including test systems, file servers and replica servers. PTC's March advisory reminded customers that mitigations must also cover file and replica servers.
  2. Patch from the vendor source. Install the fix for CVE-2026-126325 from PTC article CS483249, and confirm the earlier June, July and August patches are in place. If you rely on a reseller or managed service provider, ask them for written confirmation and the date.
  3. Hunt for the June campaign. PTC's indicators include POST requests to randomly named JSP files under /Windchill/login/, the X-windchill-req request header, a file called flst.txt and large responses from JSP files. A patched server can still carry a web shell planted months ago.
  4. Rotate credentials. If you find anything suspicious, or cannot rule it out, change service accounts, directory bind accounts and keystore secrets used by Windchill, and review what those accounts can reach.
  5. Remove direct internet exposure. Put Windchill behind a VPN or zero trust access gateway. Our guide to a zero trust model for CAD file distribution explains how to give suppliers access without opening the server.
  6. Watch bulk downloads. Alert on unusual export volumes and access patterns. See how to audit CAD file access.
  7. Protect the files, not just the server. Encrypt native CAD files at file level so a copy taken from the vault cannot be opened. Our guide to CAD encryption covers where each method stops.
  8. Plan the incident and the paperwork. Decide in advance who reports to the CSIRT under NIS2, who tells customers whose data you hold, and how you will prove which design files were yours and when.

How does this fit the bigger picture?

Our sister sites covered other routes into engineering data this week:
The common thread is that design data now lives in many connected systems, from PLM servers to repositories and asset libraries. Our complete guide to CAD file security brings these layers together.

Conclusion

CVE-2026-126325 has no known exploitation yet, and PTC shipped a patch on the day it was disclosed. That is the good news. The less comfortable news is the pattern: four critical, unauthenticated code execution flaws in one PLM platform in eight months, one of which led to a mass data theft campaign against manufacturers.
Patching quickly is the minimum. Engineering teams also need to assume that a server holding their design data can be breached one day, and make sure the CAD files themselves stay protected, traceable and provably theirs when that happens.
Make stolen CAD files useless and your ownership provable. CADChain gives every CAD file a verifiable ownership record, file-level encryption, granular permissions you can revoke at any time and a full access log, across CAD and PLM systems.

👉 Protect your CAD files with CADChain

FAQ: Windchill vulnerability CVE-2026-126325

What is CVE-2026-126325?

It is a critical remote code execution vulnerability in PTC Windchill and FlexPLM, published on 11 November 2026. It can be exploited through deserialization of untrusted data, needs no login or user interaction, and is rated 9.2 under CVSS 4.0 and 9.0 under CVSS 3.1.

Which versions are affected?

The CVE record lists Windchill 11.0 M030, 11.1 M020, 11.2.1.0, 12.0.2.0, 12.1.2.0, 13.0.2.0 and 13.1.0.0 to 13.1.4.0, and FlexPLM 11.0 M030 to 13.1.3.0. Check PTC support article CS483249 for the exact fixed builds.

Is there a patch?

Yes. PTC announced the patch on 11 November 2026. Systems hosted by PTC have been patched for customers. Self-hosted Windchill and FlexPLM systems need a Windchill administrator to install it.

Is CVE-2026-126325 being exploited?

We found no public report of exploitation as of 12 November 2026, and it was not in CISA's Known Exploited Vulnerabilities catalogue. The earlier flaw CVE-2026-12569 was exploited in June 2026 and is linked to Clop's data theft campaign.

Is this the same flaw Clop used?

No. Clop's campaign used CVE-2026-12569, disclosed in June 2026. CVE-2026-126325 is a separate flaw with its own patch, although both involve deserialization of untrusted data in Windchill and FlexPLM.

Are other PLM or CAD systems affected?

This CVE only lists PTC Windchill and FlexPLM. Other PLM systems have their own advisories, such as Oracle's October 2026 fixes for Agile PLM, so check each vendor's security notices.

Does patching remove an existing compromise?

No. A patch closes the hole but does not remove web shells or stolen credentials. Hunt for PTC's published indicators from the June campaign and rotate credentials if you cannot rule out a breach.

How does CADChain help if a PLM server is breached?

CADChain encrypts CAD files at file level, so a file copied from a vault cannot be opened without permission. It also logs every access and records ownership on a blockchain, which helps you prove what was yours. It works alongside patching and network security, not instead of them.