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.

325,773

Total vulnerabilities in the database

Vulnerabilities for products matching "tar"

Found 7 matching products. Filters apply to all results.

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

gnu / tar

17 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2025-45582	Low	July 11, 2025 7/11/25	< 1.35
CVE-2023-39804	Medium	March 27, 2024 3/27/24	< 1.35
CVE-2022-48303	Medium	January 30, 2023 1/30/23	<= 1.34
CVE-2021-20193	Low	March 26, 2021 3/26/21	<= 1.33
CVE-2019-9923	High	March 22, 2019 3/22/19	< 1.32
CVE-2018-20482	Low	December 26, 2018 12/26/18	<= 1.30
CVE-2016-6321	High	December 9, 2016 12/9/16	== 1.26 == 1.27.1 == 1.23 == 1.29 == 1.25 == 1.22 == 1.18 == 1.19 == 1.20 == 1.17 == 1.27 == 1.15.90 == 1.16 == 1.28 == 1.14 == 1.24 == 1.15.91 == 1.15 == 1.15.1 == 1.21 == 1.16.1
CVE-2010-0624	Medium	March 15, 2010 3/15/10	== 1.14.1 == 1.13.17 == 1.13.25 <= 1.22 == 1.13 == 1.13.5 == 1.18 == 1.13.18 == 1.19 == 1.20 == 1.17 == 1.15.90 == 1.16 == 1.14 == 1.13.14 == 1.15.91 == 1.13.19 == 1.14.90 == 1.15 == 1.13.11 == 1.15.1 == 1.13.16 == 1.21 == 1.16.1
CVE-2007-4476	High	September 5, 2007 9/5/07	< 1.19
CVE-2007-4131	Medium	August 25, 2007 8/25/07	== 1.13 == 1.13.5 == 1.13.11 == 1.13.14 == 1.13.16 == 1.13.17 == 1.13.18 == 1.13.19 == 1.13.25 == 1.14 == 1.14.90 == 1.15 == 1.15.1 == 1.15.90 == 1.15.91 == 1.16
CVE-2006-6097	Low	November 24, 2006 11/24/06	== 1.16 == 1.15.1
CVE-2006-0300	Medium	February 24, 2006 2/24/06	== 1.14.1 == 1.15.90 == 1.14 == 1.15 == 1.15.1
CVE-2005-1918	Low	December 31, 2005 12/31/05	== 1.13.25
CVE-2005-2541	High	August 10, 2005 8/10/05	== 1.15.1
CVE-2002-1216	Medium	October 28, 2002 10/28/02	== 1.13.19 <= 1.13.25
CVE-2002-0399	Medium	October 10, 2002 10/10/02	== 1.13.25
CVE-2001-1267	Low	July 12, 2001 7/12/01	<= 1.13.19

tar_project / tar

4 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2021-38511	High	August 10, 2021 8/10/21	< 0.4.36
CVE-2021-32803	High	August 3, 2021 8/3/21	>= 5.0.0 < 5.0.7 < 3.2.3 >= 4.0.0 < 4.4.15 >= 6.0.0 < 6.1.2
CVE-2021-32804	High	August 3, 2021 8/3/21	>= 5.0.0 < 5.0.6 < 3.2.2 >= 4.0.0 < 4.4.14 >= 6.0.0 < 6.1.1
CVE-2018-20990	Medium	August 26, 2019 8/26/19	< 0.4.16

npmjs / tar

3 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2021-37712	High	August 31, 2021 8/31/21	<= 4.4.17 >= 5.0.0 <= 5.0.9 >= 6.0.0 <= 6.1.8
CVE-2021-37713	High	August 31, 2021 8/31/21	< 4.4.18 >= 5.0.0 < 5.0.10 >= 6.0.0 < 6.1.9
CVE-2021-37701	High	August 31, 2021 8/31/21	< 4.4.16 >= 5.0.0 < 5.0.8 >= 6.0.0 < 6.1.7

tar

13 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2026-26960	High	February 18, 2026 2/18/26	< 7.5.8
CVE-2026-24842	High	January 28, 2026 1/28/26	< 7.5.7
CVE-2026-23950	High	January 21, 2026 1/21/26	< 7.5.4
CVE-2026-23745	High	January 16, 2026 1/16/26	< 7.5.3
CVE-2025-64118	Medium	October 30, 2025 10/30/25	== 7.5.1 >= 7.5.1 < 7.5.2
CVE-2024-28863	Medium	March 21, 2024 3/21/24	< 6.2.1
CVE-2021-37713	High	August 31, 2021 8/31/21	< 4.4.18 >= 5.0.0 < 5.0.10 >= 6.0.0 < 6.1.9
CVE-2021-37712	High	August 31, 2021 8/31/21	< 4.4.18 >= 5.0.0 < 5.0.10 >= 6.0.0 < 6.1.9
CVE-2021-37701	High	August 31, 2021 8/31/21	< 4.4.16 >= 5.0.0 < 5.0.8 >= 6.0.0 < 6.1.7
CVE-2021-32804	High	August 3, 2021 8/3/21	< 3.2.2 >= 4.0.0 < 4.4.14 >= 5.0.0 < 5.0.6 >= 6.0.0 < 6.1.1
CVE-2021-32803	High	August 3, 2021 8/3/21	< 3.2.3 >= 4.0.0 < 4.4.15 >= 5.0.0 < 5.0.7 >= 6.0.0 < 6.1.2
CVE-2018-20834	Medium	April 30, 2019 4/30/19	>= 3.0.0 < 4.4.2 < 2.2.2
CVE-2015-8860	Medium	January 23, 2017 1/23/17	< 2.0.0

tar

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2021-38511	High		August 10, 2021 8/10/21	< 0.4.36
CVE-2018-20990	Medium		August 26, 2019 8/26/19	< 0.4.16

isaacs / tar

6 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2026-26960	High	February 18, 2026 2/18/26	< 7.5.8
CVE-2026-24842	High	January 28, 2026 1/28/26	< 7.5.7
CVE-2026-23950	High	January 21, 2026 1/21/26	< 7.5.4
CVE-2026-23745	High	January 16, 2026 1/16/26	< 7.5.3
CVE-2024-28863	Medium	March 21, 2024 3/21/24	< 6.2.1
CVE-2018-20834	Medium	April 30, 2019 4/30/19	< 2.2.2 >= 3.0.0 < 4.4.2

@vltpkg / tar

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2026-24909	Medium		January 28, 2026 1/28/26	< 1.0.0-rc.10

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