CVE-2026-12569

Senserva AI Opinion for CVE-2026-12569

This is a pre-authentication remote code execution flaw in the Windchill PDMLink component that also ships in FlexPLM, so no valid credentials are needed. PTC first warned customers on June 17, 2026, and confirmed in-the-wild exploitation on June 18. Attackers exploit it through deserialization of untrusted data (CWE-20 combined with CWE-502) and are planting persistent JSP webshells under /Windchill/login/ using a hex naming pattern such as [0-9a-f]{16}.jsp, then staging engineering and design data. Reporting ties this to Cl0p ransomware affiliates who appear to have used it as a zero-day in early June 2026, chaining it with a separate pre-auth information-disclosure defect in the FlexPLM WSDL endpoint. This is the first PTC product ever added to the CISA KEV catalog, added June 25, 2026 with a federal remediation deadline of June 28 under BOD 26-04. The 2 percent EPSS figure understates real risk here because exploitation is already confirmed and automated at scale; the KEV listing and ransomware flag are the deciding signals, not the score.

Do this: Identify every Windchill and FlexPLM instance, prioritizing internet-facing ones, and confirm each is on 11.0 M030 or the specific patched release for its branch per PTC article CS473270; note that all CPS versions are in scope. Because exploitation predates patching, assume possible compromise on any instance exposed before you patched: hunt for JSP files matching /Windchill/login/[0-9a-f]{16}.jsp, check for the file flst.txt used in filesystem enumeration, review outbound connections against PTC's published IoCs including C2 IP 5.180.41.35, and run PTC's forensic triage guidance. Restrict the PLM tier to VPN-only access and place a WAF or proxy in front to block Java serialized payloads until patched. If a webshell or staged data is found, treat it as active intrusion and open incident response, since Cl0p activity here involves data theft and extortion rather than encryption alone.

AI-generated from public data, 2026-07-25. Verify against the vendor advisory before acting.

Full tracking and change history for CVE-2026-12569

Published

2026-06-25

Last revised

2026-06-25

Changes tracked

2

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

CISA required action

Federal (BOD 22-01) remediation due date: 2026-06-28 (past due).

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.

Common questions about CVE-2026-12569

Is CVE-2026-12569 actively exploited?

Yes. CVE-2026-12569 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-06-25, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 30%. CISA also reports it is known to be used in ransomware campaigns.

What is the CISA deadline and required action for CVE-2026-12569?

CISA set the federal (BOD 22-01) remediation due date at 2026-06-28, which has passed; treat any unremediated system as overdue. The verbatim 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.

What fixes CVE-2026-12569?

Check the vendor's security advisory for the patched Windchill and FlexPLM versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-12569?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-12569's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Scope and sources

Authoritative references

CVE recordNVD detailCISA KEV catalogFIRST.org EPSS