DrayTek Vigor Vigor2960 · Version Status

DrayTek Vigor Vigor2960 End of Life Date

DrayTek Vigor Vigor2960 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 Vigor2960 reaches end of life on December 9, 2026. Plan your migration now — 91 days remaining.
📅 Get reminded before DrayTek Vigor Vigor2960 reaches EOL on December 9, 2026 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
EOL Date
Dec 9, 2026
91 days remaining
Latest Release
Vigor2960
Standard release
Release Date
Aug 1, 2012
DrayTek Vigor Vigor2960 series
Lifecycle detail

DrayTek Vigor Vigor2960 was released on August 1, 2012 and support is scheduled to end on December 9, 2026 — a planned supported lifespan of 14 years and 4 months, longer than the 8 years and 10 months median for DrayTek Vigor releases.

← DrayTek Vigor Vigor300B All DrayTek Vigor versions DrayTek Vigor VigorAP 810 →
38 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
8/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 Vigor2960 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 Vigor2960 end of life mean?

When DrayTek Vigor Vigor2960 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 Vigor2960 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 Vigor2960 reach end of life?
DrayTek Vigor Vigor2960 reached end of life on December 9, 2026. That is 91 days remaining.
Is DrayTek Vigor Vigor2960 still supported?
DrayTek Vigor Vigor2960 is still supported but approaching end of life on December 9, 2026. Begin planning your migration now.
What should I upgrade to from DrayTek Vigor Vigor2960?
The recommended upgrade from DrayTek Vigor Vigor2960 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 Vigor2960 past EOL?
When DrayTek Vigor Vigor2960 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 →