CVE-2025-40820: Siemens SIDOOR ATD430W · Improper Verification of Source of a Communication Channel
Affects Siemens SIDOOR ATD430WSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Siemens SIDOOR ATD430W | Affected
| Fixed in– |
AI-suggested
- Implement strict ingress and egress filtering on network devices to block IP packets with spoofed source addresses, reducing the attacker's ability to inject spoofed TCP packets.
- Deploy network intrusion detection and prevention systems (IDS/IPS) tuned to detect anomalous TCP sequence number patterns or unusual connection resets targeting Siemens SIDOOR ATD430W devices.
- Segment OT and IT networks to limit exposure of vulnerable devices to untrusted networks and reduce the attack surface.
- Monitor device logs and network traffic for signs of repeated TCP connection disruptions or suspicious timing patterns indicative of exploitation attempts.
- Engage with Siemens support channels to obtain early access to patches or firmware updates once available and plan for timely deployment.
- Where feasible, implement redundant communication paths and failover mechanisms to maintain availability during potential DoS incidents.
- Educate network administrators and security teams about this specific vulnerability to enhance detection and response capabilities.
- Consider temporary disabling or restricting TCP-based services on affected devices if operationally possible until patches are applied.
Description
Affected products do not properly enforce TCP sequence number validation in specific scenarios but accept values within a broad range. This could allow an unauthenticated remote attacker e.g.to interfere with connection setup, potentially leading to a denial of service. The attack succeeds only if an attacker can inject IP packets with spoofed addresses at precisely timed moments, and it affects only TCP-based services.