Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend crafted HTTP request with serialized payload
-
DeliveryApplication deserializes untrusted input without validation
-
ExploitDeserialization gadget triggers outbound SSRF request
-
ExecutionServer queries internal network resource or cloud metadata endpoint
-
ImpactAttacker retrieves response containing internal credentials or topology data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) indicates no authentication, no special attack conditions, and no user interaction are required - the vulnerable deserialization endpoint must simply be reachable over the network. The description specifies exploitation occurs through submission of untrusted data for deserialization, meaning the attacker must reach a network-accessible endpoint that accepts and processes serialized input. Exploitation is limited by: (1) network reachability - deployments behind a VPN or internal-only firewall reduce external attack surface significantly; (2) knowledge of the specific deserialization endpoint URL and expected data format; (3) the SSRF impact is bounded by the server's outbound network policy - environments with strict egress controls will experience reduced downstream impact even if the SSRF fires. No non-default configuration is stated as a prerequisite; the vulnerability appears present in standard deployments of the affected products. |
| Impact | The CVSS 4.0 score of 7.7 with AV:N/AC:L/PR:N/UI:N reflects a straightforward, unauthenticated network-reachable attack with low complexity - an attacker needs only to reach the application endpoint and submit a crafted payload. The SC:H subsequent-system confidentiality impact aligns with SSRF's typical capability to probe and exfiltrate data from internal services (metadata APIs, internal REST endpoints, LDAP, database management interfaces) not otherwise exposed to the internet. Because PLM platforms like Windchill are commonly deployed behind corporate VPNs or in segmented DMZs, internet-exposed instances may be fewer in number, but internal-network attackers or those who have achieved a foothold represent a realistic threat class. No EPSS data was provided, and the absence of a KEV listing or known POC means exploitation likelihood cannot be quantified precisely - this is inferred risk, not confirmed active exploitation. The deserialization-as-SSRF-trigger pattern is well-documented in the Java ecosystem, meaning skilled attackers familiar with PLM platform internals could develop working exploits without novel research. Even a moderately resourced attacker targeting manufacturing supply-chain environments should be assumed capable of exploiting this class of vulnerability once an exposed endpoint is identified. |
| Exploit ScenarioDerived | An unauthenticated remote attacker submits an HTTP request to a Windchill PDMLink deserialization endpoint containing a crafted serialized payload embedding a URL fetch gadget chain. The application deserializes the payload, triggering an outbound HTTP request from the Windchill server to an internal resource - such as a cloud instance metadata endpoint or an internal microservice - and the response content is surfaced back to the attacker, exposing credentials, internal network topology, or sensitive configuration data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 20, 2026
Server-Side Request Forgery in PTC Windchill PDMLink and PTC FlexPLM allows unauthenticated remote attackers to induce the server to issue arbitrary internal network requests by submitting maliciously crafted serialized data for deserialization. The underlying root cause is CWE-502 (Deserialization of Untrusted Data), where the deserialization process itself is the vector that triggers the SSRF condition, enabling lateral movement toward backend infrastructure. No public exploit code or CISA KEV listing has been identified at time of analysis, but the combination of network accessibility and no authentication requirement elevates practical risk for internet-exposed deployments.
RemediationAI
Consult the PTC vendor advisory at https://www.ptc.com/en/support/article/CS474826 for patch or hotfix details; no exact fix version was present in the available intelligence data so a specific patched release cannot be independently confirmed here. As an immediate compensating control, restrict network access to Windchill and FlexPLM endpoints at the perimeter or WAF layer to trusted internal networks and authenticated VPN clients, reducing the attack surface for unauthenticated exploitation. Implement outbound egress filtering on the Windchill/FlexPLM application servers to prevent the server from making arbitrary outbound connections to internal RFC-1918 address ranges or cloud metadata endpoints (e.g., 169.254.169.254), which limits SSRF impact even if the deserialization trigger fires. Note that egress filtering may affect legitimate PLM integrations with internal CAD or ERP systems and should be validated in a staging environment before production deployment. Where deserialization endpoints can be identified, consider deploying a Java serialization filter (JEP 290 or equivalent) to whitelist permissible classes.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
PTC Windchill PDMLink is a Product Lifecycle Management (PLM) platform used in manufacturing and engineering environments to manage product data, CAD files, and engineering workflows. PTC FlexPLM is PTC's fashion and retail PLM offering. Both platforms expose server-side endpoints that process serialized data. CWE-502 (Deserialization of Untrusted Data) describes a root cause class where an application reconstructs objects from attacker-supplied byte streams without first validating the content, allowing the deserialization machinery itself to trigger unintended behavior - in this case, outbound HTTP or network requests (SSRF). The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms the attack surface is network-reachable with no authentication or special configuration required. The SC:H metric indicates the primary impact is on subsequent systems - internal services reachable from the PDMLink/FlexPLM host - rather than on the vulnerable application itself (VC:N/VI:N/VA:N). This pattern is consistent with Java or XML deserialization gadget chains that invoke URL fetch primitives as a side effect of object reconstruction.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/AU:Y/R:U/V:D/RE:M/U:Red
Network-accessible, unauthenticated, no user interaction; scope changes to subsequent internal systems with high confidentiality impact via SSRF; no integrity or availability impact on the vulnerable system itself.
Primary rating from Vendor (0b655efc-079c-4cb9-9e8d-164871239f4e).
CVSS VectorVendor: 0b655efc-079c-4cb9-9e8d-164871239f4e
DescriptionCVE.org
A Server-Side Request Forgery (SSRF) vulnerability has been reported in PTC Windchill PDMLink and PTC FlexPLM. The vulnerability may be exploited through the deserialization of untrusted data.
Executive ViewAI
PTC Windchill PDMLink and PTC FlexPLM contain a critical Server-Side Request Forgery (SSRF) vulnerability enabling unauthenticated remote attackers to force these systems to issue arbitrary internal network requests, exposing backend infrastructure to lateral movement and data compromise. No public exploit identified at time of analysis, but the absence of authentication requirements combined with typical internet-facing deployments creates substantial practical risk. Organizations relying on these product lifecycle management platforms face threats to data confidentiality, backend service integrity, and supply chain security.
No vendor-released patch identified at time of analysis. Interim mitigations: enforce firewall rules restricting outbound connections from PDM/FlexPLM servers to authorized backend systems only; disable Java deserialization features where application functionality permits; deploy Web Application Firewall signatures to block malicious serialized payloads; implement egress monitoring and alerting for unexpected internal network access attempts; network-isolate affected systems on separate VLANs with strict access controls; require authentication proxies for any internet-facing PDM/FlexPLM access points.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
EUVD-2026-63756
GHSA-2698-qwmx-3r6f
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB