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.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "python"

Found 3 matching products. Filters apply to all results.

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

python / python

130 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2019-18348	Medium	October 23, 2019 10/23/19	>= 2.0 <= 2.7.17 >= 3.8.0 < 3.8.3 >= 3.0 < 3.5.10 >= 3.6.0 < 3.6.11 >= 3.7.0 < 3.7.8
CVE-2019-17514	High	October 12, 2019 10/12/19	== 3.8.0 == 3.6.0 == 3.7.0
CVE-2019-16935	Medium	September 28, 2019 9/28/19	>= 2.7.0 < 2.7.17 >= 3.7.0 < 3.7.5 >= 3.6.0 < 3.6.10 >= 3.0.0 < 3.5.8
CVE-2019-16056	High	September 6, 2019 9/6/19	<= 2.7.16 >= 3.5.0 <= 3.5.7 >= 3.6.0 <= 3.6.9 >= 3.7.0 <= 3.7.4 >= 3.0.0 <= 3.0.1 >= 3.1.0 <= 3.1.5 >= 3.2.0 <= 3.2.6 >= 3.3.0 <= 3.3.7 >= 3.4.0 <= 3.4.10
CVE-2019-15903	High	September 4, 2019 9/4/19	>= 3.5.0 < 3.5.8 >= 2.7.0 < 2.7.17 >= 3.7.0 < 3.7.5 >= 3.6.0 < 3.6.10
CVE-2018-20852	Medium	July 13, 2019 7/13/19	>= 2.0 <= 2.7.16 >= 3.7.0 < 3.7.3 >= 3.6.0 < 3.6.9 >= 3.5.0 < 3.5.7 >= 3.0.0 < 3.4.10
CVE-2019-13404	High	July 8, 2019 7/8/19	<= 2.7.16 >= 3.0.0 < 3.5.0
CVE-2019-12900	Critical	June 19, 2019 6/19/19	>= 3.10.0 < 3.10.3 >= 3.9.0 < 3.9.11 >= 3.8.0 < 3.8.13 >= 3.7.0 < 3.7.13
CVE-2019-10160	Critical	June 7, 2019 6/7/19	>= 3.6.0 < 3.6.9 >= 3.7.0 < 3.7.4 >= 3.5.0 < 3.5.8 >= 2.7.0 < 2.7.17 == 3.8.0-alpha4 == 3.8.0-beta1
CVE-2019-9947	Medium	March 23, 2019 3/23/19	>= 3.6.0 < 3.6.9 >= 3.7.0 < 3.7.4 >= 3.5.0 < 3.5.8 >= 2.7.0 < 2.7.17
CVE-2019-9948	Critical	March 23, 2019 3/23/19	>= 3.6.0 < 3.6.9 >= 3.7.0 < 3.7.4 >= 3.5.0 < 3.5.8 >= 2.0 < 2.7.17
CVE-2019-9740	Medium	March 13, 2019 3/13/19	>= 3.6.0 < 3.6.9 >= 3.7.0 < 3.7.4 >= 3.5.0 < 3.5.8 >= 2.0 < 2.7.17
CVE-2019-9636	Critical	March 8, 2019 3/8/19	>= 3.7.0 < 3.7.3 >= 3.6.0 < 3.6.9 >= 3.5.0 < 3.5.7 >= 3.0.0 < 3.4.10 >= 2.7.0 < 2.7.17
CVE-2018-20406	Medium	December 23, 2018 12/23/18	>= 3.4.0 < 3.7.1
CVE-2018-14647	High	September 25, 2018 9/25/18	>= 3.5.0 <= 3.5.6 >= 2.7.0 <= 2.7.15 == 3.7.0 >= 3.4.0 <= 3.4.9 >= 3.6.0 <= 3.6.6
CVE-2018-1000802	Critical	September 18, 2018 9/18/18	>= 2.7.0 < 2.7.16
CVE-2018-1061	Medium	June 19, 2018 6/19/18	< 2.7.15 >= 3.0 < 3.4.9 >= 3.6 <= 3.6.4 >= 3.5.0 <= 3.5.5 == 3.7.0-alpha1 == 3.7.0-alpha2 == 3.7.0-alpha3 == 3.7.0-alpha4 == 3.7.0-beta1 == 3.7.0-beta2 == 3.7.0-beta3 == 3.7.0-beta4 == 3.7.0-beta5 == 3.7.0-rc1
CVE-2018-1060	High	June 18, 2018 6/18/18	>= 2.7.0 < 2.7.15 >= 3.5.0 < 3.5.6 >= 3.0.0 < 3.4.9 >= 3.6.0.x < 3.6.5
CVE-2016-9063	Critical	June 11, 2018 6/11/18	>= 3.6.0 < 3.6.2 >= 3.5.0 < 3.5.4 >= 3.4.0 < 3.4.7 >= 3.3.0 < 3.3.7 >= 2.7.0 < 2.7.15
CVE-2018-1000117	Medium	March 7, 2018 3/7/18	>= 3.2.0 < 3.4.9 >= 3.5.0 < 3.5.6 >= 3.6.0 < 3.6.5 == 3.7.0-beta1 == 3.7.0-beta2 == 3.7.0-beta3 == 3.7.0-beta4 == 3.7.0-beta5
CVE-2017-18207	Low	March 1, 2018 3/1/18	<= 3.6.4
CVE-2018-1000030	Low	February 8, 2018 2/8/18	<= 2.7.14
CVE-2017-17522	Medium	December 14, 2017 12/14/17	<= 3.6.3
CVE-2017-1000158	Critical	November 17, 2017 11/17/17	< 2.7.15 >= 3.5.0 < 3.5.5 >= 3.4.0 < 3.4.8
CVE-2014-4616	Medium	August 24, 2017 8/24/17	>= 3.3.0 < 3.3.6 >= 2.7.0 < 2.7.7 >= 3.0.0 < 3.2.6 >= 3.4.0 < 3.4.1
CVE-2017-9233	High	July 25, 2017 7/25/17	>= 3.6.0 < 3.6.2 >= 3.5.0 < 3.5.4 >= 3.4.0 < 3.4.7 >= 3.3.0 < 3.3.7 >= 2.7.0 < 2.7.15
CVE-2016-5699	Low	September 2, 2016 9/2/16	<= 2.7.9 == 3.1.1 == 3.3.2 == 3.0 == 3.0.1 == 3.2.2 == 3.1.0 == 3.2.5 == 3.1.5 == 3.3.6 == 3.4.0 == 3.2.1 == 3.2.0 == 3.3.1 == 3.4.3 == 3.1.2 == 3.3.4 == 3.3.5 == 3.2.3 == 3.2.6 == 3.3.0 == 3.4.2 == 3.3.3 == 3.2.4 == 3.4.1 == 3.1.3 == 3.1.4
CVE-2016-5636	High	September 2, 2016 9/2/16	== 3.1.1 == 3.3.2 == 3.0 == 3.0.1 == 3.2.2 == 3.1.0 == 3.2.5 == 3.1.5 == 3.3.6 == 3.4.0 == 3.2.1 == 3.2.0 == 3.3.1 == 3.4.3 == 3.4.4 == 3.1.2 == 3.3.4 == 3.3.5 == 3.2.3 == 3.2.6 == 3.3.0 == 3.4.2 == 3.3.3 == 3.2.4 == 3.4.1 == 3.1.3 == 3.1.4 <= 2.7.11 == 3.5.0 == 3.5.1
CVE-2016-0772	Medium	September 2, 2016 9/2/16	== 3.5.0 == 3.5.1 == 3.1.1 == 3.3.2 == 3.0 == 3.0.1 == 3.2.2 == 3.1.0 == 3.2.5 == 3.1.5 == 3.3.6 == 3.4.0 == 3.2.1 == 3.2.0 == 3.3.1 == 3.4.3 == 3.4.4 == 3.1.2 == 3.3.4 == 3.3.5 == 3.2.3 == 3.2.6 == 3.3.0 == 3.4.2 == 3.3.3 == 3.2.4 == 3.4.1 == 3.1.3 == 3.1.4 <= 2.7.11
CVE-2016-2183	High	September 1, 2016 9/1/16	>= 3.4.0 < 3.4.7 >= 3.5.0 < 3.5.3 >= 2.7.0 < 2.7.13
CVE-2016-4472	High	June 30, 2016 6/30/16	>= 3.6.0 < 3.6.2 >= 3.5.0 < 3.5.4 >= 3.4.0 < 3.4.7 >= 3.3.0 < 3.3.7 >= 2.7.0 < 2.7.15
CVE-2016-3189	Medium	June 30, 2016 6/30/16	>= 3.10.0 < 3.10.3 >= 3.9.0 < 3.9.11 >= 3.8.0 < 3.8.13 >= 3.7.0 < 3.7.13
CVE-2013-7440	Low	June 7, 2016 6/7/16	<= 2.7.8 == 3.1 == 3.1.1 == 3.3.2 == 3.0 == 3.3.1-rc1 == 3.0.1 == 3.2.2 == 3.3 == 3.2.5 == 3.1.5 == 3.2.2150 == 3.2.1 == 3.2.0 == 3.3.1 == 3.1.2150 == 3.1.2 == 3.2.3 == 3.2.6 == 3.2 == 3.3.0 == 3.2.4 == 3.2-alpha == 3.3-beta2 == 3.1.3 == 3.1.4
CVE-2016-0718	Critical	May 26, 2016 5/26/16	>= 3.6.0 < 3.6.2 >= 3.5.0 < 3.5.4 >= 3.4.0 < 3.4.7 >= 3.3.0 < 3.3.7 >= 2.7.0 < 2.7.15
CVE-2015-5652	High	October 6, 2015 10/6/15	<= 3.5.0
CVE-2015-1283	Medium	July 23, 2015 7/23/15	>= 3.3.0 < 3.3.7 >= 3.5.0 < 3.5.2 >= 3.4.0 < 3.4.5 >= 2.7.0 < 2.7.12
CVE-2014-9365	Medium	December 12, 2014 12/12/14	== 2.7.6 == 2.4.2 == 3.3.5 == 3.1 == 3.3.3-rc2 == 3.1.1 == 3.3.2 == 2.7.8 == 2.5.1 == 2.3.4 == 3.0 == 3.3.1-rc1 == 2.6.6 == 3.0.1 == 2.1 == 2.0.1 == 3.2.2 == 2.7.1150 == 3.3 == 2.6.1 == 2.3.1 == 3.2.5 == 2.1.2 == 3.1.5 == 3.2.2150 == 3.3.4-rc1 == 2.7.4 == 2.2.1 == 3.4.0 == 3.2.1 == 2.5.4 == 3.2.0 == 3.3.1 == 2.6.3 == 2.2.2 == 2.1.1 == 3.3.3-rc1 == 2.6.2150 == 2.3.3 == 2.7.1 == 3.1.2150 == 2.3.2 == 3.1.2 == 2.6.8 == 2.6.7 == 2.4.6 == 2.7.3 == 2.7.1-rc1 == 2.0 == 2.2.3 == 3.3.4 == 2.5.2 == 2.3.7 == 3.3.6-rc1 == 3.2.3 == 2.6.4 == 3.3.5-rc2 == 2.7.2-rc1 == 2.6.6150 == 2.7.7 == 3.3.5-rc1 == 2.5.3 == 3.2.6 == 3.2 == 2.7.5 == 2.4.4 == 3.3.0 == 2.5.150 == 2.2 == 3.4.2 == 2.6.2 == 2.5.6 == 3.3.3 == 2.3.5 == 3.4-alpha1 == 3.2.4 == 2.7.2150 == 2.1.3 == 3.4.1 == 3.2-alpha == 2.4.1 == 2.4.3 == 3.3-beta2 == 2.6.5 == 3.1.3 == 3.1.4
CVE-2014-2667	Low	November 16, 2014 11/16/14	== 3.3.2 == 3.2.2 == 3.2.5 == 3.3.6 == 3.4.0 == 3.2.1 == 3.2.0 == 3.3.1 == 3.3.4 == 3.3.5 == 3.2.3 == 3.2.6 == 3.3.0 == 3.4.2 == 3.3.3 == 3.2.4 == 3.4.1
CVE-2014-7185	Medium	October 8, 2014 10/8/14	== 2.7.6 <= 2.7.7 == 2.7.1150 == 2.7.4 == 2.7.1 == 2.7.3 == 2.7.1-rc1 == 2.7.2-rc1 == 2.7.5 == 2.7.2150
CVE-2014-0224	High	June 5, 2014 6/5/14	>= 2.7.0 < 2.7.8 >= 3.4.0 < 3.4.2
CVE-2013-7040	Low	May 19, 2014 5/19/14	== 2.7.6 == 3.3.5 == 3.1 == 3.3.3-rc2 == 3.1.1 == 3.3.2 == 3.0 == 3.3.1-rc1 == 3.0.1 == 3.2.2 == 3.3 == 3.2.5 == 3.1.5 == 3.2.2150 == 3.3.4-rc1 == 2.7.4 == 3.2.1 == 3.2.0 == 3.3.1 == 3.3.3-rc1 == 2.7.1 == 3.1.2 == 2.7.1150 == 2.7.3 == 2.7.1-rc1 == 3.3.4 == 3.2.3 == 3.3.5-rc2 == 2.7.2-rc1 == 2.7.7 == 3.3.5-rc1 == 3.2 == 2.7.5 == 3.3.0 == 3.3.3 == 3.2.4 == 2.7.2150 == 3.2-alpha == 3.3-beta2 == 3.1.3 == 3.1.4
CVE-2013-7338	High	April 22, 2014 4/22/14	== 3.3.3-rc2 == 3.3.2 == 3.3.1-rc1 == 3.3.3-rc1 == 3.3.3 == 3.3.0 == 3.3.0-alpha1 == 3.3.0-alpha2 == 3.3.0-alpha3 == 3.3.0-alpha4 == 3.3.0-beta1 == 3.3.0-beta2 == 3.3.0-rc1 == 3.3.0-rc2 == 3.3.0-rc3 == 3.3.1
CVE-2014-1912	High	March 1, 2014 3/1/14	== 2.7.6 == 2.5.1 == 2.6.6 == 2.7.1150 == 2.6.1 == 2.7.4 == 2.5.4 == 2.6.3 == 2.6.2150 == 2.7.1 == 2.6.8 == 2.6.7 == 2.7.3 == 2.7.1-rc1 == 2.5.2 == 2.6.4 == 2.7.2-rc1 == 2.6.6150 == 2.5.3 == 2.7.5 == 2.5.150 == 2.6.2 == 2.5.6 == 2.7.2150 == 2.6.5 == 3.1 == 3.1.1 == 3.3.2 == 3.0 == 3.0.1 == 3.2.2 == 3.3 == 3.2.5 == 3.1.5 == 3.2.2150 == 3.2.1 == 3.2.0 == 3.3.1 == 3.1.2150 == 3.1.2 == 3.2.3 == 3.2 == 3.3.0 == 3.3.3 == 3.4-alpha1 == 3.2.4 == 3.2-alpha == 3.3-beta2 == 3.1.3 == 3.1.4
CVE-2013-0340	Medium	January 21, 2014 1/21/14	>= 3.8.0 < 3.8.12 >= 3.9.0 < 3.9.7 >= 3.7.0 < 3.7.12 >= 3.6.0 < 3.6.15
CVE-2013-2099	Low	October 9, 2013 10/9/13	== 3.3.2 == 3.2.2 == 3.2.5 == 3.2.1 == 3.2.0 == 3.3.1 == 3.2.3 == 3.3.0 == 3.2.4
CVE-2013-4238	Low	August 18, 2013 8/18/13	== 3.1 == 3.1.1 == 3.0 == 2.6.6 == 3.0.1 == 2.7.1150 == 3.3 == 2.6.1 == 3.1.5 == 3.2.2150 == 2.6.3 == 2.6.2150 == 2.7.1 == 3.1.2150 == 3.1.2 == 2.6.8 == 2.6.7 == 2.7.3 == 2.7.1-rc1 == 3.2.3 == 2.6.4 == 2.7.2-rc1 == 2.6.6150 == 3.2 == 2.6.2 == 3.4-alpha1 == 2.7.2150 == 3.2-alpha == 3.3-beta2 == 2.6.5 == 3.1.3 == 3.1.4
CVE-2012-0845	Medium	October 5, 2012 10/5/12	== 2.4.2 == 2.5.1 == 2.3.4 == 2.6.6 == 2.1 == 2.0.1 == 2.6.1 == 2.3.1 == 0.9.1 == 2.1.2 == 0.9.0 == 1.6.1 == 2.2.1 == 2.5.4 == 1.3 == 2.6.3 == 2.2.2 == 2.1.1 == 1.5.2 == 2.6.2150 == 2.3.3 == 2.3.2 == 1.6 == 1.2 == 2.4.6 == 2.0 == 2.2.3 <= 2.6.7 == 2.5.2 == 2.3.7 == 2.6.4 == 2.6.6150 == 2.5.3 == 2.4.4 == 2.5.150 == 2.2 == 2.6.2 == 2.5.6 == 2.3.5 == 2.1.3 == 2.4.1 == 2.4.3 == 2.6.5 == 2.7.1 == 2.7.1150 == 2.7.1-rc1 == 2.7.2-rc1 == 2.7.2150 == 3.1 == 3.1.1 == 3.0 == 3.0.1 == 3.1.2 == 3.1.3 == 3.1.4 == 3.2.2150 == 3.2 == 3.2-alpha
CVE-2012-1150	Medium	October 5, 2012 10/5/12	== 2.4.2 == 2.5.1 == 2.3.4 == 2.6.6 == 2.1 == 2.0.1 == 2.6.1 == 2.3.1 == 0.9.1 == 2.1.2 == 0.9.0 == 1.6.1 == 2.2.1 == 2.5.4 == 1.3 == 2.6.3 == 2.2.2 == 2.1.1 == 1.5.2 == 2.6.2150 == 2.3.3 == 2.3.2 == 1.6 == 1.2 == 2.4.6 == 2.0 == 2.2.3 <= 2.6.7 == 2.5.2 == 2.3.7 == 2.6.4 == 2.6.6150 == 2.5.3 == 2.4.4 == 2.5.150 == 2.2 == 2.6.2 == 2.5.6 == 2.3.5 == 2.1.3 == 2.4.1 == 2.4.3 == 2.6.5 == 2.7.1 == 2.7.1150 == 2.7.1-rc1 == 2.7.2-rc1 == 2.7.2150 == 3.1 == 3.1.1 == 3.0 == 3.0.1 == 3.1.2 == 3.1.3 == 3.1.4 == 3.2.2150 == 3.2 == 3.2-alpha
CVE-2011-4944	Low	August 27, 2012 8/27/12	== 3.1 == 3.1.1 == 3.0 == 2.6.6 == 3.0.1 == 2.7.1150 == 2.6.1 == 3.1.5 == 2.6.3 == 2.6.2150 == 2.7.1 == 3.1.2150 == 3.1.2 == 2.6.8 == 2.6.7 == 2.7.3 == 2.7.1-rc1 == 2.6.4 == 2.7.2-rc1 == 2.6.6150 == 3.2 == 2.6.2 == 2.7.2150 == 3.2-alpha == 2.6.5 == 3.1.3 == 3.1.4
CVE-2012-2135	Medium	August 14, 2012 8/14/12	>= 3.3.0 < 3.3.3 >= 3.2.0 < 3.2.4 >= 2.7.0 < 2.7.4

Showing vulnerabilities for 3 products matching "python". 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.