DrayTek Vigor VigorBX 2000 · Version Status

DrayTek Vigor VigorBX 2000 End of Life Date

DrayTek Vigor VigorBX 2000 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

DrayTek Vigor VigorBX 2000 is past end of life. This version no longer receives security patches. 96 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 5, 2026
96 days past EOL
Latest Release
VigorBX 2000
Standard release
Release Date
Feb 4, 2016
DrayTek Vigor VigorBX 2000 series
Lifecycle detail

DrayTek Vigor VigorBX 2000 was released on February 4, 2016 and support ended on June 5, 2026 — a supported lifespan of 10 years and 4 months, longer than the 8 years and 10 months median for DrayTek Vigor releases. It has been without security patches for 3 months. 3 newer DrayTek Vigor releases have shipped since.

← DrayTek Vigor Vigor3220 All DrayTek Vigor versions DrayTek Vigor Vigor2952 →
60 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
30/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
Recommended upgrade path
DrayTek Vigor Vigor2136F Series
Latest release: Vigor2136F Series · EOL: Supported
View full DrayTek Vigor timeline →
Extended Support
Extended DrayTek Vigor VigorBX 2000 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All DrayTek Vigor Versions
VersionLatestEOL DateStatus
VigorSwitch P2500 VigorSwitch P2500 Jan 5, 2025 EOL
VigorSwitch G2500 VigorSwitch G2500 Jan 5, 2025 EOL
VigorAP 710 VigorAP 710 Mar 10, 2025 EOL
Vigor2133 Series Vigor2133 Series Apr 1, 2025 EOL
VigorSwitch P1092 VigorSwitch P1092 Jul 8, 2025 EOL
VigorSwitch P2121 VigorSwitch P2121 Jul 8, 2025 EOL
VigorSwitch P1085 VigorSwitch P1085 Jul 8, 2025 EOL
VigorSwitch G1085 VigorSwitch G1085 Jul 8, 2025 EOL

What does DrayTek Vigor VigorBX 2000 end of life mean?

When DrayTek Vigor VigorBX 2000 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running DrayTek Vigor VigorBX 2000 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to DrayTek Vigor Vigor2136F Series or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does DrayTek Vigor VigorBX 2000 reach end of life?
DrayTek Vigor VigorBX 2000 reached end of life on June 5, 2026. This version is no longer receiving security patches.
Is DrayTek Vigor VigorBX 2000 still supported?
No. DrayTek Vigor VigorBX 2000 reached end of life on June 5, 2026 and is no longer receiving security patches.
What should I upgrade to from DrayTek Vigor VigorBX 2000?
The recommended upgrade from DrayTek Vigor VigorBX 2000 is DrayTek Vigor Vigor2136F Series — the latest actively supported version. Check the DrayTek Vigor full timeline for all supported versions.
What are the security risks of running DrayTek Vigor VigorBX 2000 past EOL?
When DrayTek Vigor VigorBX 2000 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL DrayTek Vigor should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →