How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

327,921

Total vulnerabilities in the database

Vulnerabilities for products matching "chrome"

Found 5 matching products. Filters apply to all results.

You can search for specific versions with /product/chrome/1.2.3

google / chrome

707 vulnerabilities found (with exploits)

Title	Severity	Date	Affected Version
CVE-2019-5825	Medium	November 25, 2019 11/25/19	< 73.0.3683.86
CVE-2019-13720	High	November 25, 2019 11/25/19	< 78.0.3904.87
CVE-2019-5827	High	June 27, 2019 6/27/19	< 74.0.3729.131
CVE-2019-5786	Medium	June 27, 2019 6/27/19	< 72.0.3626.121
CVE-2018-20346	Medium	December 21, 2018 12/21/18	< 71.0.3578.80
CVE-2018-17480	High	December 11, 2018 12/11/18	< 71.0.3578.80
CVE-2018-6065	High	November 14, 2018 11/14/18	< 65.0.3325.146
CVE-2018-17463	High	November 14, 2018 11/14/18	< 70.0.3538.67
CVE-2017-1000460	Low	January 3, 2018 1/3/18	<= 56.0.2924
CVE-2017-5070	High	October 27, 2017 10/27/17	< 59.0.3071.86 < 59.0.3071.92
CVE-2017-5030	High	April 24, 2017 4/24/17	< 57.0.2987.108 < 57.0.2987.98
CVE-2016-5198	High	January 19, 2017 1/19/17	< 54.0.2840.85 < 54.0.2840.87 < 54.0.2840.90
CVE-2016-1646	High	March 29, 2016 3/29/16	< 49.0.2623.108
CVE-2015-3336	Low	April 19, 2015 4/19/15	<= 42.0.2311.60
CVE-2015-3335	High	April 19, 2015 4/19/15	<= 42.0.2311.60
CVE-2015-3334	Low	April 19, 2015 4/19/15	<= 42.0.2311.60
CVE-2015-1241	Low	April 19, 2015 4/19/15	< 42.0.2311.90
CVE-2014-3803	Low	May 21, 2014 5/21/14	<= 35.0.1916.113 == 35.0.1916.99 == 35.0.1916.57 == 35.0.1916.3 == 35.0.1916.38 == 35.0.1916.105 == 35.0.1916.95 == 35.0.1916.52 == 35.0.1916.82 == 35.0.1916.42 == 35.0.1916.36 == 35.0.1916.111 == 35.0.1916.61 == 35.0.1916.98 == 35.0.1916.47 == 35.0.1916.110 == 35.0.1916.10 == 35.0.1916.20 == 35.0.1916.85 == 35.0.1916.9 == 35.0.1916.92 == 35.0.1916.23 == 35.0.1916.49 == 35.0.1916.54 == 35.0.1916.106 == 35.0.1916.35 == 35.0.1916.33 == 35.0.1916.5 == 35.0.1916.11 == 35.0.1916.86 == 35.0.1916.17 == 35.0.1916.13 == 35.0.1916.72 == 35.0.1916.109 == 35.0.1916.77 == 35.0.1916.88 == 35.0.1916.59 == 35.0.1916.44 == 35.0.1916.108 == 35.0.1916.74 == 35.0.1916.45 == 35.0.1916.18 == 35.0.1916.107 == 35.0.1916.21 == 35.0.1916.6 == 35.0.1916.71 == 35.0.1916.41 == 35.0.1916.8 == 35.0.1916.4 == 35.0.1916.19 == 35.0.1916.0 == 35.0.1916.40 == 35.0.1916.101 == 35.0.1916.32 == 35.0.1916.51 == 35.0.1916.80 == 35.0.1916.39 == 35.0.1916.43 == 35.0.1916.93 == 35.0.1916.34 == 35.0.1916.37 == 35.0.1916.103 == 35.0.1916.90 == 35.0.1916.68 == 35.0.1916.1 == 35.0.1916.112 == 35.0.1916.27 == 35.0.1916.7 == 35.0.1916.84 == 35.0.1916.46 == 35.0.1916.104 == 35.0.1916.22 == 35.0.1916.69 == 35.0.1916.15 == 35.0.1916.31 == 35.0.1916.96 == 35.0.1916.14 == 35.0.1916.56 == 35.0.1916.2 == 35.0.1916.48
CVE-2013-6650	High	January 28, 2014 1/28/14	== 32.0.1700.6 == 32.0.1700.56 == 32.0.1700.51 == 32.0.1700.68 == 32.0.1700.12 == 32.0.1700.99 <= 32.0.1700.101 == 32.0.1700.69 == 32.0.1700.29 == 32.0.1700.98 == 32.0.1700.4 == 32.0.1700.66 == 32.0.1700.16 == 32.0.1700.63 == 32.0.1700.96 == 32.0.1700.39 == 32.0.1700.54 == 32.0.1700.94 == 32.0.1700.57 == 32.0.1700.74 == 32.0.1700.22 == 32.0.1700.18 == 32.0.1700.3 == 32.0.1700.0 == 32.0.1700.21 == 32.0.1700.19 == 32.0.1700.72 == 32.0.1700.34 == 32.0.1700.71 == 32.0.1700.35 == 32.0.1700.27 == 32.0.1700.67 == 32.0.1700.97 == 32.0.1700.64 == 32.0.1700.58 == 32.0.1700.15 == 32.0.1700.13 == 32.0.1700.38 == 32.0.1700.59 == 32.0.1700.14 == 32.0.1700.9 == 32.0.1700.30 == 32.0.1700.55 == 32.0.1700.10 == 32.0.1700.24 == 32.0.1700.75 == 32.0.1700.52 == 32.0.1700.65 == 32.0.1700.77 == 32.0.1700.32 == 32.0.1700.7 == 32.0.1700.33 == 32.0.1700.26 == 32.0.1700.23 == 32.0.1700.5 == 32.0.1700.53 == 32.0.1700.76 == 32.0.1700.8 == 32.0.1700.50 == 32.0.1700.70 == 32.0.1700.100 == 32.0.1700.62 == 32.0.1700.2 == 32.0.1700.95 == 32.0.1700.31 == 32.0.1700.41 == 32.0.1700.17 == 32.0.1700.28 == 32.0.1700.11
CVE-2013-6649	High	January 28, 2014 1/28/14	== 32.0.1700.6 == 32.0.1700.56 == 32.0.1700.51 == 32.0.1700.68 == 32.0.1700.12 == 32.0.1700.99 <= 32.0.1700.101 == 32.0.1700.69 == 32.0.1700.29 == 32.0.1700.98 == 32.0.1700.4 == 32.0.1700.66 == 32.0.1700.16 == 32.0.1700.63 == 32.0.1700.96 == 32.0.1700.39 == 32.0.1700.54 == 32.0.1700.94 == 32.0.1700.57 == 32.0.1700.74 == 32.0.1700.22 == 32.0.1700.18 == 32.0.1700.3 == 32.0.1700.0 == 32.0.1700.21 == 32.0.1700.19 == 32.0.1700.72 == 32.0.1700.34 == 32.0.1700.71 == 32.0.1700.35 == 32.0.1700.27 == 32.0.1700.67 == 32.0.1700.97 == 32.0.1700.64 == 32.0.1700.58 == 32.0.1700.15 == 32.0.1700.13 == 32.0.1700.38 == 32.0.1700.59 == 32.0.1700.14 == 32.0.1700.9 == 32.0.1700.30 == 32.0.1700.55 == 32.0.1700.10 == 32.0.1700.24 == 32.0.1700.75 == 32.0.1700.52 == 32.0.1700.65 == 32.0.1700.77 == 32.0.1700.32 == 32.0.1700.7 == 32.0.1700.33 == 32.0.1700.26 == 32.0.1700.23 == 32.0.1700.5 == 32.0.1700.53 == 32.0.1700.76 == 32.0.1700.8 == 32.0.1700.50 == 32.0.1700.70 == 32.0.1700.100 == 32.0.1700.62 == 32.0.1700.2 == 32.0.1700.95 == 32.0.1700.31 == 32.0.1700.41 == 32.0.1700.17 == 32.0.1700.28 == 32.0.1700.11
CVE-2013-6641	High	January 16, 2014 1/16/14	< 32.0.1700.76 < 32.0.1700.77
CVE-2013-6643	High	January 16, 2014 1/16/14	< 32.0.1700.76 < 32.0.1700.77
CVE-2013-6644	High	January 16, 2014 1/16/14	< 32.0.1700.76 < 32.0.1700.77
CVE-2013-6645	Medium	January 16, 2014 1/16/14	< 32.0.1700.76 < 32.0.1700.77
CVE-2013-6646	High	January 16, 2014 1/16/14	< 32.0.1700.76 < 32.0.1700.77
CVE-2013-6621	High	November 13, 2013 11/13/13	== 31.0.1650.22 == 31.0.1650.45 == 31.0.1650.11 == 31.0.1650.33 == 31.0.1650.32 == 31.0.1650.31 == 31.0.1650.28 == 31.0.1650.26 == 31.0.1650.4 == 31.0.1650.2 == 31.0.1650.16 == 31.0.1650.39 == 31.0.1650.41 == 31.0.1650.38 == 31.0.1650.5 <= 31.0.1650.47 == 31.0.1650.36 == 31.0.1650.43 == 31.0.1650.34 == 31.0.1650.13 == 31.0.1650.44 == 31.0.1650.23 == 31.0.1650.17 == 31.0.1650.19 == 31.0.1650.20 == 31.0.1650.14 == 31.0.1650.10 == 31.0.1650.46 == 31.0.1650.7 == 31.0.1650.37 == 31.0.1650.29 == 31.0.1650.8 == 31.0.1650.25 == 31.0.1650.9 == 31.0.1650.3 == 31.0.1650.12 == 31.0.1650.15 == 31.0.1650.30 == 31.0.1650.35 == 31.0.1650.27 == 31.0.1650.42 == 31.0.1650.6 == 31.0.1650.0 == 31.0.1650.18
CVE-2013-2632	Medium	March 21, 2013 3/21/13	<= 27.0.1444.0
CVE-2012-5851	Low	November 15, 2012 11/15/12	== 22.0.1229.23 == 22.0.1229.63 == 22.0.1229.18 == 22.0.1229.33 == 22.0.1229.9 == 22.0.1229.57 == 22.0.1229.32 == 22.0.1229.54 == 22.0.1229.16 == 22.0.1229.4 == 22.0.1229.21 == 22.0.1229.95 == 22.0.1229.78 == 22.0.1229.12 == 22.0.1229.31 == 22.0.1229.92 == 22.0.1229.89 == 22.0.1229.10 == 22.0.1229.2 == 22.0.1229.22 == 22.0.1229.35 == 22.0.1229.50 == 22.0.1229.36 == 22.0.1229.60 == 22.0.1229.62 == 22.0.1229.25 == 22.0.1229.51 == 22.0.1229.0 == 22.0.1229.1 == 22.0.1229.7 == 22.0.1229.17 == 22.0.1229.20 == 22.0.1229.26 == 22.0.1229.65 == 22.0.1229.8 == 22.0.1229.59 == 22.0.1229.37 == 22.0.1229.52 == 22.0.1229.49 == 22.0.1229.55 == 22.0.1229.64 == 22.0.1229.27 == 22.0.1229.28 == 22.0.1229.76 == 22.0.1229.56 == 22.0.1229.48 == 22.0.1229.67 == 22.0.1229.29 == 22.0.1229.14 == 22.0.1229.79 == 22.0.1229.11 == 22.0.1229.6 == 22.0.1229.24 == 22.0.1229.3 <= 22.0.1229.96 == 22.0.1229.94 == 22.0.1229.58 == 22.0.1229.39 == 22.0.1229.53 == 22.0.1229.91
CVE-2011-3078	Medium	May 1, 2012 5/1/12	< 18.0.1025.168
CVE-2011-3081	High	May 1, 2012 5/1/12	< 18.0.1025.168
CVE-2012-1521	Medium	May 1, 2012 5/1/12	< 18.0.1025.168
CVE-2011-3076	Medium	April 5, 2012 4/5/12	< 18.0.1025.151
CVE-2011-3077	Medium	April 5, 2012 4/5/12	< 18.0.1025.151
CVE-2011-3067	Medium	April 5, 2012 4/5/12	< 18.0.1025.151
CVE-2011-3069	Medium	April 5, 2012 4/5/12	< 18.0.1025.151
CVE-2011-3070	Medium	April 5, 2012 4/5/12	< 18.0.1025.151
CVE-2011-3071	Medium	April 5, 2012 4/5/12	< 18.0.1025.151
CVE-2011-3072	Medium	April 5, 2012 4/5/12	< 18.0.1025.151
CVE-2011-3073	Medium	April 5, 2012 4/5/12	< 18.0.1025.151
CVE-2011-3074	Medium	April 5, 2012 4/5/12	< 18.0.1025.151
CVE-2011-3075	Medium	April 5, 2012 4/5/12	< 18.0.1025.151
CVE-2011-3058	Low	March 30, 2012 3/30/12	< 18.0.1025.142
CVE-2011-3060	Medium	March 30, 2012 3/30/12	< 18.0.1025.142
CVE-2011-3061	Medium	March 30, 2012 3/30/12	< 18.0.1025.142
CVE-2011-3065	Medium	March 30, 2012 3/30/12	< 18.0.1025.142
CVE-2011-3050	Medium	March 22, 2012 3/22/12	< 17.0.963.83
CVE-2011-3052	Medium	March 22, 2012 3/22/12	< 18.0.1025.142
CVE-2011-3055	Low	March 22, 2012 3/22/12	< 17.0.963.83
CVE-2011-3031	Medium	March 5, 2012 3/5/12	< 17.0.963.65
CVE-2011-3026	Medium	February 16, 2012 2/16/12	< 17.0.963.56

Showing vulnerabilities for 5 products matching "chrome". Each product has independent pagination.

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.