Google Chrome 9
Google Chrome 9
The Google Chrome 9 reached end of service life on Mar 8, 2011. Third-party maintenance keeps it supported — 24/7 engineering support and same-day replacement parts — at 40-70% below OEM renewal pricing.
Specifications
- product
- chrome
- release
- 9
- product Label
- Google Chrome
- release Label
- 9
- codename
- lts
- latest Version
- release Date
- 2011-01-25
- maintained
- source Url
- https://endoflife.date/chrome
Lifecycle Dates
- End of Service Life
- Mar 8, 2011
- Last OEM Support
- Mar 8, 2011
OEM vs. 3rd Party Support
See how 3rd party maintenance compares to traditional OEM support for your Google Chrome 9. Get the same level of service at a fraction of the cost.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| 24/7/365 Support | ||
| Same-Day Parts Replacement | Limited | |
| Mixed-Vendor Support | ||
| Flexible Contract Terms | Annual Only | Month-to-Month Available |
| Asset Lifecycle Extension | ||
| OEM-Trained Engineers |
Why Choose 3rd Party Support for Google Chrome 9?
Save 40-70%
Dramatically reduce your maintenance costs while maintaining the same level of support coverage.
Extend Asset Life
Continue using your Google Chrome 9 well beyond the OEM end-of-life date.
24/7 Expert Support
OEM-trained engineers available around the clock with same-day parts replacement.
Google Chrome 9 Support: Frequently Asked Questions
Is the Google Chrome 9 still supported?
Google ended support for the Google Chrome 9 on Mar 8, 2011. Third-party maintenance remains available and keeps the Google Chrome 9 supported with 24/7 engineering support and same-day replacement parts.
When is the Google Chrome 9 end of service life (EOSL) date?
Google lists the end of service life for the Google Chrome 9 as Mar 8, 2011.
Can I keep using the Google Chrome 9 after its EOSL date?
Yes. EOSL means Google stops selling support contracts and issuing updates — the equipment itself keeps working. Third-party maintenance provides engineering support and replacement parts for as long as you choose to run it.
How much does third-party support for the Google Chrome 9 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Google Chrome 9
5809 published CVEs affect the Google Chrome 9, including 3313 rated critical or high severity. Google no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2026-13782 | CRITICAL | 10.0 | Jun 30, 2026 | Use after free in Browser in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical) |
| CVE-2026-79152 | CRITICAL | 9.8 | Aug 25, 2026 | Incorrect authorization in CustomTabs in Google Chrome on on Android prior to 152.0.7977.65 allowed a local attacker to bypass web origin policy via a co-installed app. (Chromium security severity: Low) |
| CVE-2026-14121 | CRITICAL | 9.8 | Jun 30, 2026 | Use after free in Chromoting in Google Chrome on Linux prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code via malicious network traffic. (Chromium security severity: Low) |
| CVE-2026-14104 | CRITICAL | 9.8 | Jun 30, 2026 | Insufficient validation of untrusted input in WebAppInstalls in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: Low) |
| CVE-2026-13776 | CRITICAL | 9.8 | Jun 30, 2026 | Type Confusion in Dawn in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical) |
| CVE-2026-13775 | CRITICAL | 9.8 | Jun 30, 2026 | Use after free in GPU in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical) |
| CVE-2026-5902 | CRITICAL | 9.8 | Apr 8, 2026 | Race in Media in Google Chrome on Android prior to 147.0.7727.55 allowed a remote attacker who had compromised the renderer process to corrupt media stream metadata via a crafted HTML page. (Chromium security severity: Low) |
| CVE-2026-3062 | CRITICAL | 9.8 | Feb 23, 2026 | Out of bounds read and write in Tint in Google Chrome on Mac prior to 145.0.7632.116 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High) |
| CVE-2026-0907 | CRITICAL | 9.8 | Jan 20, 2026 | Incorrect security UI in Split View in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low) |
| CVE-2026-0906 | CRITICAL | 9.8 | Jan 20, 2026 | Incorrect security UI in Google Chrome on Android prior to 144.0.7559.59 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page. (Chromium security severity: Low) |
| CVE-2026-0905 | CRITICAL | 9.8 | Jan 20, 2026 | Insufficient policy enforcement in Network in Google Chrome prior to 144.0.7559.59 allowed an attack who obtained a network log file to potentially obtain potentially sensitive information via a network log file. (Chromium security severity: Medium) |
| CVE-2025-10585 | CRITICAL | 9.8 | Sep 24, 2025 | Type confusion in V8 in Google Chrome prior to 140.0.7339.185 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High) |
| CVE-2025-4052 | CRITICAL | 9.8 | May 5, 2025 | Inappropriate implementation in DevTools in Google Chrome prior to 136.0.7103.59 allowed a remote attacker who convinced a user to engage in specific UI gestures to bypass discretionary access control via a crafted HTML page. (Chromium security severity: Low) |
| CVE-2024-1284 | CRITICAL | 9.8 | Feb 7, 2024 | Use after free in Mojo in Google Chrome prior to 121.0.6167.160 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High) |
| CVE-2024-1283 | CRITICAL | 9.8 | Feb 7, 2024 | Heap buffer overflow in Skia in Google Chrome prior to 121.0.6167.160 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High) |
| CVE-2024-0808 | CRITICAL | 9.8 | Jan 24, 2024 | Integer underflow in WebUI in Google Chrome prior to 121.0.6167.85 allowed a remote attacker to potentially exploit heap corruption via a malicious file. (Chromium security severity: High) |
| CVE-2023-1529 | CRITICAL | 9.8 | Mar 21, 2023 | Out of bounds memory access in WebHID in Google Chrome prior to 111.0.5563.110 allowed a remote attacker to potentially exploit heap corruption via a malicious HID device. (Chromium security severity: High) |
| CVE-2022-2587 | CRITICAL | 9.8 | Aug 12, 2022 | Out of bounds write in Chrome OS Audio Server in Google Chrome on Chrome OS prior to 102.0.5005.125 allowed a remote attacker to potentially exploit heap corruption via crafted audio metadata. |
| CVE-2020-15993 | CRITICAL | 9.8 | Nov 3, 2020 | Use after free in printing in Google Chrome prior to 86.0.4240.99 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. |
| CVE-2019-5866 | CRITICAL | 9.8 | Nov 25, 2019 | Out of bounds memory access in JavaScript in Google Chrome prior to 75.0.3770.142 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. |
Showing the 20 most severe of 5809 known CVEs.
Get Third Party Support