NVIDIA GPU Mobile Professional Maxwell (GMxxx) · Version Status
NVIDIA GPU Mobile Professional Maxwell (GMxxx) End of Life Date
NVIDIA GPU Mobile Professional Maxwell (GMxxx) 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.
✓
NVIDIA GPU Mobile Professional Maxwell (GMxxx) is actively supported. EOL date: October 31, 2028.
📅 Get reminded before NVIDIA GPU Mobile Professional Maxwell (GMxxx) reaches EOL on October 31, 2028 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Oct 31, 2028
769 days remaining
Latest Release
—
Standard release
Release Date
Aug 18, 2015
NVIDIA GPU Mobile Professional Maxwell (GMxxx) series
Lifecycle detail
NVIDIA GPU mobile-professional-maxwell was released on August 18, 2015 and support is scheduled to end on October 31, 2028 — a planned supported lifespan of 13 years and 3 months, in line with the 11 years and 6 months median for NVIDIA GPU releases.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
10/10 None 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 →
| Version | Latest | EOL Date | Status |
|---|
| Consumer Fahrenheit (NVx) |
— |
Mar 11, 2005 |
EOL |
| Consumer Celsius (NV1x) |
— |
Apr 14, 2005 |
EOL |
| Consumer Kelvin (NV1x, NV2x) |
— |
Nov 2, 2006 |
EOL |
| Consumer Rankine (NV3x) |
— |
Jun 23, 2008 |
EOL |
| Consumer Curie (NV4x, G7x) |
— |
Feb 24, 2015 |
EOL |
| Consumer Tesla (Cxx, G8x, G9x, GT2xx, ION) |
— |
Dec 14, 2016 |
EOL |
| Consumer Fermi (GF1xx)* |
— |
Mar 10, 2018 |
EOL |
| Professional Fermi (GF1xx)** |
— |
Dec 31, 2022 |
EOL |
What does NVIDIA GPU Mobile Professional Maxwell (GMxxx) end of life mean?
When NVIDIA GPU Mobile Professional Maxwell (GMxxx) 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 NVIDIA GPU Mobile Professional Maxwell (GMxxx) past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to NVIDIA GPU Mobile Professional Blackwell (GB20x) or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does NVIDIA GPU Mobile Professional Maxwell (GMxxx) reach end of life?
NVIDIA GPU Mobile Professional Maxwell (GMxxx) reached end of life on October 31, 2028. That is 769 days remaining.
Is NVIDIA GPU Mobile Professional Maxwell (GMxxx) still supported?
Yes, NVIDIA GPU Mobile Professional Maxwell (GMxxx) is currently supported. The EOL date is October 31, 2028.
What should I upgrade to from NVIDIA GPU Mobile Professional Maxwell (GMxxx)?
The recommended upgrade from NVIDIA GPU Mobile Professional Maxwell (GMxxx) is
NVIDIA GPU Mobile Professional Blackwell (GB20x) — the latest actively supported version. Check the
NVIDIA GPU full timeline for all supported versions.
What are the security risks of running NVIDIA GPU Mobile Professional Maxwell (GMxxx) past EOL?
When NVIDIA GPU Mobile Professional Maxwell (GMxxx) 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 NVIDIA GPU should migrate immediately or implement compensating controls.