CVE-2025-10547: DrayTek Vigor1000B · Missing Initialization of a Variable
Affects DrayTek Vigor1000BSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% 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:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Oct 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| DrayTek Corporation Vigor1000B | Affected
| Fixed in– |
AI-suggested
Given the absence of official patches, European organizations should immediately implement the following mitigations: 1) Disable remote HTTP management interfaces on Vigor1000B routers to reduce exposure to external attackers. 2) Restrict management access to trusted internal networks or VPNs only. 3) Employ network segmentation to isolate vulnerable routers from critical systems and sensitive data environments. 4) Monitor network traffic for anomalous HTTP CGI requests indicative of exploitation attempts. 5) Deploy intrusion detection/prevention systems (IDS/IPS) with signatures targeting suspicious memory corruption or RCE patterns related to DrayTek devices. 6) Maintain up-to-date asset inventories to identify all affected devices and prioritize remediation. 7) Engage with DrayTek support channels for early patch notifications and test updates in controlled environments before deployment. 8) Prepare incident response plans specific to router compromise scenarios. These steps go beyond generic advice by focusing on reducing attack surface, early detection, and containment tailored to this vulnerability’s characteristics.
Description
An uninitialized variable in the HTTP CGI request arguments processing component of Vigor Routers running DrayOS may allow an attacker the ability to perform RCE on the appliance through memory corruption.