Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
UnratedCISA KEVExploited in the wildPublic exploit

RCE in PTC Windchill PDMlink and PTC FlexPLM

IdentifiersCVE-2026-12569CWE-502

CVE-2026-12569 is a critical remote code execution vulnerability affecting PTC Windchill PDMlink and PTC FlexPLM, including all CPS versions and Windchill/FlexPLM releases prior to 11.0 M030. The flaw is described as improper input validation and is specifically exploitable through deserialization of untrusted data. A remote attacker can send a specially crafted malicious network request that triggers unsafe deserialization behavior and results in arbitrary code execution on the target system. Reporting cited by CISA indicates the vulnerability has been actively exploited in the wild, with attackers deploying JSP web shells on compromised systems.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary code execution on affected Windchill and FlexPLM systems. In observed attacks, threat actors deployed JSP web shells, enabling persistent remote access, follow-on command execution, and likely data access or exfiltration from the compromised application environment. Given the network-reachable, unauthenticated nature of the flaw and the high confidentiality, integrity, and availability impact described in the source material, compromise can result in full application-server takeover and broader enterprise risk.

Mitigation

If you can’t patch tonight, do this now.

Where immediate patching is not possible, reduce exposure of the Windchill login endpoint from the internet where operationally feasible. Implement perimeter blocking for known attacker infrastructure identified by PTC, including 5.180.41.35, and monitor or block additional reported IOC IPs as appropriate. Add WAF or IDS detections to block requests containing the header X-windchill-req:. Conduct filesystem and log-based hunting for JSP web shells under /Windchill/login/ and suspicious POST activity targeting login-path JSP files. These measures are compensating controls only and do not replace patching.

Remediation

Patch, then assume compromise.

Apply PTC's vendor-supplied security patches immediately. Upgrade affected Windchill and FlexPLM releases to 11.0 M030 or later, including applicable CPS updates, as releases prior to 11.0 M030 are impacted. Because active exploitation has been reported, remediation should also include incident-response validation: review PTC-published indicators of compromise, inspect HTTP access logs for suspicious POST requests to /Windchill/login/*.jsp, scan for JSP files matching /Windchill/login/[0-9a-f]{16}.jsp, and investigate suspicious files such as those matching the published hash and the presence of flst.txt in /tmp or the Windchill working directory.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
PtcFlexplmapplication
PtcWindchillapplication
PtcWindchill Pdmlinkapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware2

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity27

Community discussion across Reddit, Mastodon, and other social sources.