Vulnerability Database

328,411

Total vulnerabilities in the database

Vulnerabilities for products matching "glibc"

Found 2 matching products. Filters apply to all results.

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

gnu / glibc

150 vulnerabilities found
Title Severity Exploit Date Affected Version
Low January 18, 2019 1/18/19
<= 2.28
High December 4, 2018 12/4/18
<= 2.28
High May 18, 2018 5/18/18
>= 2.21 <= 2.27
High May 18, 2018 5/18/18
<= 2.27
High May 18, 2018 5/18/18
<= 2.27
High February 2, 2018 2/2/18
>= 2.24 <= 2.26
High February 1, 2018 2/1/18
<= 2.26
High February 1, 2018 2/1/18
== 2.1.1
Medium February 1, 2018 2/1/18
== 2.5
High January 31, 2018 1/31/18
<= 2.26
High December 18, 2017 12/18/17
== 2.22
== 2.20
== 2.25
== 2.19
== 2.21
== 2.26
== 2.23
Medium December 5, 2017 12/5/17
== 2.26
High October 22, 2017 10/22/17
<= 2.26
High October 20, 2017 10/20/17
<= 2.26
Low October 20, 2017 10/20/17
<= 2.26
Low October 18, 2017 10/18/17
<= 2.14.1
Low September 7, 2017 9/7/17
<= 2.25
Low August 1, 2017 8/1/17
<= 2.25
Medium June 27, 2017 6/27/17
<= 2.24
High June 19, 2017 6/19/17
<= 2.25
High June 12, 2017 6/12/17
<= 2.19
High May 7, 2017 5/7/17
== 2.25
Medium March 20, 2017 3/20/17
<= 2.21
Low March 20, 2017 3/20/17
<= 2.21
Medium March 20, 2017 3/20/17
< 2.28
Medium March 15, 2017 3/15/17
<= 2.20
Low March 2, 2017 3/2/17
<= 2.25
Medium February 17, 2017 2/17/17
<= 2.23
Medium October 7, 2016 10/7/16
<= 2.24
Medium June 10, 2016 6/10/16
< 2.24
High June 10, 2016 6/10/16
< 2.23
Medium June 1, 2016 6/1/16
<= 2.23
Medium June 1, 2016 6/1/16
< 2.24
High April 19, 2016 4/19/16
<= 2.22
Medium April 19, 2016 4/19/16
<= 2.22
High April 19, 2016 4/19/16
<= 2.22
High April 19, 2016 4/19/16
<= 2.22
Medium February 18, 2016 2/18/16
== 2.10
== 2.10.1
== 2.11
== 2.11.1
== 2.11.2
== 2.11.3
== 2.12
== 2.12.1
== 2.12.2
== 2.13
== 2.14
== 2.14.1
== 2.15
== 2.16
== 2.17
== 2.18
== 2.19
== 2.20
== 2.21
== 2.22
== 2.9
Low January 20, 2016 1/20/16
<= 2.22
High December 17, 2015 12/17/15
<= 2.19
Medium September 28, 2015 9/28/15
<= 2.21
Medium August 26, 2015 8/26/15
<= 2.14.1
Medium April 8, 2015 4/8/15
<= 2.20
High April 8, 2015 4/8/15
<= 2.20
Medium March 27, 2015 3/27/15
<= 2.21
High February 24, 2015 2/24/15
<= 2.20
Medium February 24, 2015 2/24/15
< 2.20
High January 28, 2015 1/28/15
>= 2.0 < 2.18
Medium December 5, 2014 12/5/14
== 2.1.2
== 2.11
== 2.0.5
== 2.0.6
== 2.10.1
== 2.1.1
== 2.17
== 2.14
== 2.0.3
== 2.0
== 2.13
== 2.1.1.6
== 2.1
== 2.1.9
== 2.12.1
== 2.0.1
== 2.14.1
== 2.11.2
== 2.0.4
== 2.0.2
== 2.16
<= 2.19
== 2.18
== 2.11.3
== 2.11.1
== 2.1.3
== 2.15
== 2.12
== 2.12.2
Medium December 5, 2014 12/5/14
<= 2.16

Showing vulnerabilities for 2 products matching "glibc". Each product has independent pagination.

Frequently Asked Questions

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.