What is CVE-2026-12569?

CVE-2026-12569 is Remote Code Execution (RCE) vulnerability in Windchill PDMlink. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-20 Improper Input Validation; CWE-502 Deserialization of Untrusted Data.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

4 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-12569 using CVSS 9.8, EPSS 30%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Ransomware use: Known. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVRansomwarecriticalRemote Code Execpublic exploit

CVE-2026-12569

Remote Code Execution (RCE) vulnerability in Windchill PDMlink

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2026-12569 in CISA KEV with required action: 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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

Published Jun 18, 2026Updated Aug 1, 2026Sources: NVD, PTC (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Jun 25, 2026

EPSS

30%

ahead of 98% of scored CVEs

Affects

PTC

19 products listed

CVSS base

9.8

critical · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Windchill PDMLink to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

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.

Federal deadline Jun 28, 2026 — passed 54 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
PTC	Windchill PDMLink	0 to <= 11.0 M030	Vulnerable
PTC	Windchill PDMLink	11.1 M020	Vulnerable
PTC	Windchill PDMLink	11.2.1.0	Vulnerable
PTC	Windchill PDMLink	12.0.2.0	Vulnerable
PTC	Windchill PDMLink	12.1.2.0	Vulnerable
PTC	Windchill PDMLink	13.0.2.0	Vulnerable
PTC	Windchill PDMLink	13.1.0.0	Vulnerable
PTC	Windchill PDMLink	13.1.1.0	Vulnerable
PTC	Windchill PDMLink	13.1.2.0	Vulnerable
PTC	Windchill PDMLink	13.1.3.0	Vulnerable
PTC	FlexPLM	0 to <= 11.0 M030	Vulnerable
PTC	FlexPLM	11.1 M020	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.8	CVSS 3.1	critical	3.9	5.9	NVD, GHSA
9.3	CVSS 4.0	critical	—	—	PTC (CNA)

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

Weakness & attack patterns

CWE-20Improper Input Validation
CWE-502Deserialization of Untrusted Data

Inferred from the weakness class — not observed against this CVE.

CAPEC-242 · Code InjectionCAPEC-35 · Leverage Executable Code in Non-Executable Files

T1562.003Impair Defenses: Impair Command History Logging
T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Jun 25, 2026

Federal deadline

Jun 28, 2026

passed 54 days ago

Ransomware use

Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 4 sampled are weaponized

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Windchill PDMLink, FlexPLM.
Monitor for scanner or exploit-pattern traffic after 4 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.8 (AV:N)
Aug 1, 2026 · NVD
Added to CISA KEV catalog
Jun 25, 2026 · CISA
Initial · CVE published
Jun 18, 2026 · NVD
Added · GHSA-f345-wxwr-fxfh published (critical)
Jun 18, 2026 · GitHub Security Advisory

References

6 on the record

www.ptc.com/en/support/article/CS473270
Permissions Required, Vendor Advisory
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-12569
US Government Resource
nvd.nist.gov/vuln/detail/CVE-2026-12569
NVD, Vendor Advisory
github.com/advisories/GHSA-f345-wxwr-fxfh
Exploit, Third Party Advisory
www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
US Government Resource
www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
US Government Resource

Elsewhere on this site

PTCevery CVE for this vendor
June 2026what else CISA listed
Remote Code Execsame class
CWE-20other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-12569 is Remote Code Execution (RCE) vulnerability in Windchill PDMlink, a critical vulnerability affecting Windchill PDMLink, FlexPLM from PTC. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 4 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 30% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.