Threats / PTC / CVE-2026-12569

CVE-2026-12569 · EUVD no mirror located · GCVE no mirror located Verified 2026-08-10

PTC Windchill and FlexPLM vulnerability

PTC Windchill and FlexPLM contains an improper input validation vulnerability allowing an unauthenticated, remote attacker to execute arbitrary code by sending a malicious request to the network.

Verdict

Today item, not a backlog item.

Known-exploited and flagged for ransomware use. If you run an exposed, unpatched instance, assume-breach is the correct posture — not a patch window.

CISA KEV Yes · 2026-06-25⁵Ransomware use Flagged⁵EPSS 0.30198 (verify live)⁶CVSS 9.3³CISA SSVC Exploitation: active · Automatable: yes · Impact: total⁴

Is it exploitable?

— the evidence, ranked above the score

Reported exploitation

9 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.

cisa.gov ↗cyware.com ↗recordedfuture.com ↗ransom-isac.org ↗Confirmed

Exploited in the wild

Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-06-25), flagged for known ransomware use.

CISA KEV ↗Confirmed

Probability (EPSS)

EPSS 0.30198 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.

FIRST EPSS ↗High

Severity / affected

CVSS 9.3 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/AU:Y/R:U/V:C/U:Red) · Affected: PTC, Windchill and FlexPLM. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.

CVE.org ↗Reported

Weakness (CWE)

Mapped to CWE-20 Improper Input Validation, CWE-502 Deserialization of Untrusted Data — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.

CVE.org ↗Reported

CISA SSVC (triage disposition)

Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.

CISA-ADP ↗Reported

Currency of the record

CISA added this to its KEV catalog 7 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.

CISA KEV ↗CVE.org ↗Reported

WeaknessCWE-20 · Improper Input Validation CWE-502 · Deserialization of Untrusted DataInjection

Who’s exploiting it?

— attribution turns risk into urgency

Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

Why it matters

— the attack path, told twice: adversary, then board

Attacker/business narrative framing is pending triage for this record — see Coverage & confidence below. Facts and verdict above are derived deterministically from the public feed.

What to do

— defensible action

Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.¹

Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.

Coverage & confidence

— what we know, and what we don’t

Established (cited)

KEV listing (CISA)

Ransomware-use flag (CISA)

EPSS probability (FIRST)

9 reported-exploitation source(s)

CVSS 9.3 — CNA-assigned (CVE.org)

CISA SSVC triage disposition (CVE.org ADP)

CWE weakness mapping — CNA-assigned (CVE.org)

Catalogued by PTC (CNA)

Coverage gaps — stated, not hidden

No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.

EPSS & exposure are time-varying; verify live at the source.

Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.

No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.

Attacker/business narrative framing pending triage.

Disclosure & credit²

Catalogued by PTCCNA

Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.

Found an error? Propose a correction.

A correction is a cited counter-claim — it must cite a source, gets reviewed by a second human, and is never auto-applied. See the correction convention and our identity npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.

With JavaScript off: publish a signed kind 1111 Nostr event tagging ["r", "https://basicsecurity.net/threat/cve-2026-12569.html"] plus ["src", "<your source URL>"] and ["t", "correction"], per the correction convention. Our identity: npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y. Cite-or-die: an event with no src is a coverage finding, not a proposal.