SonicWall SonicWave / SonicPoint access points (hardware) G · Version Status
SonicWall SonicWave / SonicPoint access points (hardware) G End of Life Date
SonicWall SonicWave / SonicPoint access points (hardware) G end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (sonicwall.com); the source of each date is on the product page.
⚠
SonicWall SonicWave / SonicPoint access points (hardware) G is past end of life. This version no longer receives security patches. 5337 days past EOL — migrate to a supported version immediately.
EOL Date
Mar 1, 2012
5337 days past EOL
Latest Release
SonicPoint G
Standard release
Release Date
—
SonicWall SonicWave / SonicPoint access points (hardware) G series
Lifecycle detail
It has been without security patches for 14 years and 8 months.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in 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 →
Extended Support
Extended SonicWall SonicWave / SonicPoint access points (hardware) G support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All SonicWall SonicWave / SonicPoint access points (hardware) Versions
| Version | Latest | EOL Date | Status |
|---|
| → G |
SonicPoint G |
Mar 1, 2012 |
EOL |
| A/B/G |
SonicPoint A/B/G |
Mar 1, 2012 |
EOL |
| N Dual-Band |
SonicPoint N Dual-Band |
Sep 1, 2013 |
EOL |
| N Dual Radio |
SonicPoint N Dual Radio |
Jan 1, 2020 |
EOL |
| Ni |
SonicPoint Ni |
Mar 1, 2020 |
EOL |
| Ne |
SonicPoint Ne |
Oct 1, 2020 |
EOL |
| ACe/ACi |
SonicPoint ACe/ACi |
Jul 31, 2022 |
EOL |
| N2 |
SonicPoint N2 |
Jul 31, 2022 |
EOL |
What does SonicWall SonicWave / SonicPoint access points (hardware) G end of life mean?
When SonicWall SonicWave / SonicPoint access points (hardware) G 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running SonicWall SonicWave / SonicPoint access points (hardware) G past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to SonicWall SonicWave / SonicPoint access points (hardware) 224w or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does SonicWall SonicWave / SonicPoint access points (hardware) G reach end of life?
SonicWall SonicWave / SonicPoint access points (hardware) G reached end of life on March 1, 2012. This version is no longer receiving security patches.
Is SonicWall SonicWave / SonicPoint access points (hardware) G still supported?
No. SonicWall SonicWave / SonicPoint access points (hardware) G reached end of life on March 1, 2012 and is no longer receiving security patches.
What should I upgrade to from SonicWall SonicWave / SonicPoint access points (hardware) G?
What are the security risks of running SonicWall SonicWave / SonicPoint access points (hardware) G past EOL?
When SonicWall SonicWave / SonicPoint access points (hardware) G reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL SonicWall SonicWave / SonicPoint access points (hardware) should migrate immediately or implement compensating controls.