Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 28 Jun 2026.Known ransomware use
In the wildRansomwareRemotely reachableNo privilegesZero-click
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited
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
In the news
Third-party coverage
Trending covered by 3 outlets this week · latest 3w ago
Surfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidence
A critical deserialization vulnerability in PTC Windchill PDMlink and PTC FlexPLM allows unauthenticated remote code execution through the processing of untrusted serialized data. The vulnerability affects all CPS versions and Windchill/FlexPLM releases prior to version 11.0 M030.
MitigationUpgrade PTC Windchill and FlexPLM to version 11.0 M030 or later to address the deserialization vulnerability. Apply any available PTC patches for CPS versions immediately and consider network segmentation as a compensating control until the upgrade can be completed.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checks
Work through these to decide whether this CVE applies to you.
Identify installed PTC product
Locate the Windchill or FlexPLM installation directory and check for version information files (typically in the product's bin or config directory, or check the About dialog/license information)
Affected if The installed product is PTC Windchill PDMlink or PTC FlexPLM
Determine the exact version number
Run the product's version command or check the release information file (commonly found in the Windchill or FlexPLM installation root, or use the product's info/managment console)
Affected if The version matches any of the listed affected versions: for FlexPLM: <= 11.0m030, 11.1m020, 11.2.1.0, 12.0.0.0, 12.0.2.0, 12.1.3.0, 13.0.2.0, 13.0.3.0; for Windchill PDMlink: < 11.0m030, 11.0m030, 11.1m020, 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
Verify the web application is exposed
Check if the Windchill or FlexPLM web interface (typically on ports 80/443 or custom ports like 8080/8443) is accessible from network locations. Use netstat or check the application server configuration.
Affected if The PLM web services are accessible from untrusted networks
Check for deserialization endpoints
Review the application's exposed HTTP endpoints and web services that handle serialized data (often found in SOAP/RMI interfaces or custom serialization handlers). Examine the application's web.xml or equivalent configuration.
Affected if The application exposes endpoints that accept serialized Java objects without authentication
You are affected if you have Windchill PDMlink or FlexPLM installed and its version matches the affected list AND the product's web interface is network-accessible, allowing external deserialization calls.
Generated from the published advisory. Verify against your own configuration.
Check your environment
Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.
AI-assisted, checked against the advisory. Informational, not a guarantee.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped
Upgrade availableUpgrade to 11.0m030 or later
Fixed in11.0m030
Interim mitigation
Upgrade PTC Windchill and FlexPLM to version 11.0 M030 or later to address the deserialization vulnerability. Apply any available PTC patches for CPS versions immediately and consider network segmentation as a compensating control until the upgrade can be completed.
Recommended fixModerate confidence
PTC recommends upgrading to the latest available release for FlexPLM and Windchill PDMLink (versions greater than 12.0.0.0) or the latest patch level for your current major version
1. Identify the exact current version of PTC FlexPLM or Windchill PDMLink installed in your environment
2. Review PTC Support Portal (support.ptc.com) for the latest security bulletins related to CVE-2026-12569
3. Download and test the latest available patch or service pack for your product line in a non-production environment
4. Apply the patch following PTC's standard patch installation procedures
5. Verify the fix by confirming the patched version number and running any provided validation scripts
6. Deploy the patched version to production after successful validation
Caveat Review PTC release notes for potential impacts; major version upgrades may require configuration adjustments or compatibility testing with integrations
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Flexplm
Exploited in the wild — priority engagement
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,576.
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2026-12569 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Peer-ranked notes from engineers who’ve handled CVE-2026-12569 in production — separate from our analysis above.
Know something about CVE-2026-12569?
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon
CVE-2026-12569 is a critical deserialization RCE affecting PTC's FlexPLM and Windchill platforms across all CPS versions prior to 11.0 M030. With a 9.8 CVSS and confirmed active exploitation (CISA KEV), this is a live incident — the 30% EPSS probability reflects weapons-grade activity in the wild, not theoretical risk.
The most consequential question for defenders is authentication. If exploitation requires valid credentials, network segmentation and WAF rules become partially effective at best — you're defending against credential compromise from phishing, insider threat, or service account takeover. PLM systems typically run under service accounts with broad privileges across CAD and ERP integrations, and those accounts often lack the monitoring applied to human users. Treat this as a credential hygiene problem, not a perimeter problem.
If the pathway is unauthenticated, the blast radius expands dramatically — but either way, patch priority doesn't change. The 'all CPS versions' language reveals something uncomfortable: this vulnerability predates PTC's formal vulnerability management process, meaning it survived years of internal review cycles. The 2017 advisory PSRT-17-045 addressed unsafe deserialization in their dependency chain, but this specific pathway survived that audit — a pattern where vendors patch reported handlers without auditing for structurally identical attack surfaces elsewhere.
For organizations on pre-M030 releases: demand from PTC whether M030 represents a targeted patch to this handler or an architectural change addressing the serialization pattern across modules. If it's targeted, expect a sibling CVE in adjacent modules within 18 months. Your immediate containment options are limited — prioritize credential isolation, service account review, and upgrade planning.
What this is
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
What belongs here
Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data