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.

413,619

Total vulnerabilities in the database

Vulnerabilities for products matching "cli"

Found 30 matching products. Filters apply to all results.

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

areca / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2007-4027	Medium		July 26, 2007 7/26/07	`<= 1.72.250`

cisco / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2007-4430	Medium		August 20, 2007 8/20/07	`All versions`

cli_project / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2016-10538	Low		May 31, 2018 5/31/18	`< 1.0.0`

snyk / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2022-40764	High		October 3, 2022 10/3/22	`< 1.996.0`

@tinacms / cli

10 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2026-108259	High	October 9, 2026 10/9/26	`< 3.0.0`
CVE-2026-63123	Medium	August 19, 2026 8/19/26	`< 2.5.2`
CVE-2026-54074	High	June 19, 2026 6/19/26	`< 2.4.3`
CVE-2026-29066	Medium	March 12, 2026 3/12/26	`< 2.1.8`
CVE-2026-28793	High	March 12, 2026 3/12/26	`< 2.1.8`
CVE-2026-28792	Critical	March 12, 2026 3/12/26	`< 2.1.8`
CVE-2025-68278	High	December 18, 2025 12/18/25	`< 2.0.4`
CVE-2024-45391	High	September 3, 2024 9/3/24	`< 1.6.2`
CVE-2023-25164	High	February 8, 2023 2/8/23	`>= 1.0.0, < 1.0.9`
CVE-2016-10538	Low	May 31, 2018 5/31/18	`< 1.0.0`

@graphql-mesh / cli

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
Unwanted access to the entire file system vulnerability due to a missing check in `staticFiles` HTTP handler	Medium		February 16, 2023 2/16/23	`>= 0.78.0, < 0.82.22`
CVE-2025-27098	Medium		February 16, 2023 2/16/23	`>= 0.78.0, < 0.82.22`

@saltcorn / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
Unsafe plugins can be installed via pack import by tenant admins	High		July 27, 2023 7/27/23	`< 0.8.8-beta.2`

@tauri-apps / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2023-46115	High		October 20, 2023 10/20/23	`>= 2.0.0-alpha.0, < 2.0.0-alpha.16` `>= 1.0.0, < 1.5.6`

@aws-amplify / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2024-28056	Critical		April 15, 2024 4/15/24	`< 12.10.1`

@hoppscotch / cli

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
@hoppscotch/cli affected by Sandbox Escape in @hoppscotch/js-sandbox leads to RCE	High		April 22, 2024 4/22/24	`>= 0.5.0, < 0.8.0`
CVE-2024-34347	High		April 22, 2024 4/22/24	`>= 0.5.0, < 0.8.0`

@zowe / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2024-6833	Medium		July 17, 2024 7/17/24	`>= 7.18.0, < 7.23.5`

@mockoon / cli

3 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2026-59148	High	September 11, 2026 9/11/26	`< 9.7.0`
CVE-2026-59149	Medium	September 11, 2026 9/11/26	`< 9.7.0`
CVE-2025-59049	High	March 11, 2025 3/11/25	`< 9.2.0`

github / cli

3 vulnerabilities found

Title	Severity	Date	Affected versions
CVE-2026-48501	High	May 29, 2026 5/29/26	`< 2.93.0`
CVE-2026-45803	Low	May 19, 2026 5/19/26	`>= 1.6.0, < 2.92.0`
CVE-2024-52308	High	November 14, 2024 11/14/24	`< 2.62.0`

@react-native-community / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2025-11953	Critical		November 3, 2025 11/3/25	`>= 20.0.0-alpha.0, < 20.0.0` `>= 19.0.0-alpha.0, < 19.1.2` `>= 18.0.0, < 18.0.1`

@capgo / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
Capgo CLI: symlink-following local secret writes enable arbitrary file overwrite + world-readable credentials (0600 missing)	High		March 18, 2026 3/18/26	`< 7.84.6`

@lightdash / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
Axios supply chain attack - dependency in @lightdash/cli may resolve to compromised axios versions	Critical		April 2, 2026 4/2/26	`>= 0.1800.0, < 0.2695.1`

@usebruno / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2026-34841	Critical		April 2, 2026 4/2/26	`< 3.2.1`

nhost / cli

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2026-47671	Medium		June 4, 2026 6/4/26	`< 1.46.0`
CVE-2026-34200	High		March 31, 2026 3/31/26	`< 1.41.0`

bitwarden / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2026-42994	Critical		May 1, 2026 5/1/26	`= 2026.4.0`

org.jenkins-ci.main / cli

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2025-67635	High		December 10, 2025 12/10/25	`>= 2.529, < 2.541` `< 2.528.3`
CVE-2015-8103	Critical		November 25, 2015 11/25/15	`< 1.625.2` `>= 1.626, < 1.638`

@apostrophecms / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2026-42853	Medium		May 14, 2026 5/14/26	`<= 3.6.0`

@kilocode / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2026-8766	Low		May 18, 2026 5/18/26	`<= 7.0.47`

@actual-app / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2026-46672	Medium		June 22, 2026 6/22/26	`< 26.6.0`

@wakaru / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2026-54545	High		July 28, 2026 7/28/26	`>= 1.0.0, < 1.4.0`

@genql / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2026-63397	High		July 16, 2026 7/16/26	`< 6.3.4`

@redocly / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2026-63225	Medium		September 17, 2026 9/17/26	`< 1.34.17` `>= 2.0.0, < 2.33.2`

@quasar / cli

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected versions
CVE-2026-106105	High		October 7, 2026 10/7/26	`< 5.0.4`

Showing vulnerabilities for 30 products matching "cli". Each product has independent pagination.

Running cli on internet-facing hosts?

Knowing a product's CVEs is half the job; the other half is knowing every place it is exposed. Attack surface management continuously maps your external assets and the software they run.

What is attack surface management? →

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.