CVE-2021-38406: Delta Electronics DOPSoft 2 · Out-of-bounds Write
Affects Delta Electronics DOPSoft 2Source CVE Database V5
Exploited in the wild · KEV due 15 Sep 2022 · 76% EPSS · end of life, no fix coming : replace or isolate Delta Electronics DOPSoft 2; no fix will be released.
Data as of 25 Oct 2026, 19:02 UTC
- KEV deadline
- US federal agencies must patch by this date; a sensible deadline for everyone else.
- EPSS
- 76.4% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- None coming – the product is end of life
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 17 Sep 2021
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: evidence found.
Listed in CISA KEV 342 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by icscert
, 38 days before disclosure
CVE published
on cve.org
, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
, 342 days after disclosure
KEV remediation due
US federal deadline
, 363 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
No fix will be released: Delta Electronics DOPSoft 2 is end of life. Replace it, or isolate it from untrusted networks until you can.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Delta Electronics DOPSoft 2 | Affected
| Fixed in– |
Description
Delta Electronic DOPSoft 2 (Version 2.00.07 and prior) lacks proper validation of user-supplied data when parsing specific project files. This could result in multiple out-of-bounds write instances. An attacker could leverage this vulnerability to execute code in the context of the current process.