Vulnerability Database

383,371

Total vulnerabilities in the database

Vulnerabilities for products matching "cli"

Found 28 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
Medium July 26, 2007 7/26/07
<= 1.72.250

cisco / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
Medium August 20, 2007 8/20/07
All versions

cli_project / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
Low May 31, 2018 5/31/18
< 1.0.0

snyk / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
High October 3, 2022 10/3/22
< 1.996.0
Node.js icon

@tinacms / cli

9 vulnerabilities found
Title Severity Exploit Date Affected versions
Medium August 19, 2026 8/19/26
< 2.5.2
High July 1, 2026 7/1/26
< 2.4.3
Critical March 12, 2026 3/12/26
< 2.1.8
High March 12, 2026 3/12/26
< 2.1.8
Medium March 12, 2026 3/12/26
< 2.1.8
High December 18, 2025 12/18/25
< 2.0.4
High September 3, 2024 9/3/24
< 1.6.2
High February 8, 2023 2/8/23
>= 1.0.0, < 1.0.9
Low May 31, 2018 5/31/18
< 1.0.0
Node.js icon

@graphql-mesh / cli

2 vulnerabilities found
Title Severity Exploit Date Affected versions
Medium February 20, 2025 2/20/25
>= 0.78.0, < 0.82.22
Medium February 16, 2023 2/16/23
>= 0.78.0, < 0.82.22
Node.js icon

@saltcorn / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
High July 27, 2023 7/27/23
< 0.8.8-beta.2
Node.js icon

@tauri-apps / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
High October 20, 2023 10/20/23
>= 2.0.0-alpha.0, < 2.0.0-alpha.16
>= 1.0.0, < 1.5.6
Node.js icon

@aws-amplify / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
Critical April 15, 2024 4/15/24
< 12.10.1
Node.js icon

@hoppscotch / cli

2 vulnerabilities found
Title Severity Exploit Date Affected versions
High May 8, 2024 5/8/24
>= 0.5.0, < 0.8.0
High April 22, 2024 4/22/24
>= 0.5.0, < 0.8.0
Node.js icon

@zowe / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
Medium July 17, 2024 7/17/24
>= 7.18.0, < 7.23.5
Node.js icon

@mockoon / cli

3 vulnerabilities found
Title Severity Exploit Date Affected versions
High July 9, 2026 7/9/26
< 9.7.0
Medium July 9, 2026 7/9/26
< 9.7.0
High September 10, 2025 9/10/25
< 9.2.0

github / cli

3 vulnerabilities found
Title Severity Exploit Date Affected versions
High May 29, 2026 5/29/26
< 2.93.0
Low May 15, 2026 5/15/26
>= 1.6.0, < 2.92.0
High November 14, 2024 11/14/24
< 2.62.0
Node.js icon

@react-native-community / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
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
Node.js icon

@capgo / cli

1 vulnerabilities found
Node.js icon

@lightdash / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
Critical April 2, 2026 4/2/26
>= 0.1800.0, < 0.2695.1
Node.js icon

@usebruno / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
Critical April 6, 2026 4/6/26
< 3.2.1

nhost / cli

2 vulnerabilities found
Title Severity Exploit Date Affected versions
Medium July 21, 2026 7/21/26
< 1.46.0
High March 31, 2026 3/31/26
< 1.41.0

bitwarden / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
Critical May 1, 2026 5/1/26
= 2026.4.0
Maven icon

org.jenkins-ci.main / cli

2 vulnerabilities found
Title Severity Exploit Date Affected versions
High December 10, 2025 12/10/25
>= 2.529, < 2.541
< 2.528.3
Critical November 25, 2015 11/25/15
< 1.625.2
>= 1.626, < 1.638
Node.js icon

@apostrophecms / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
Medium June 12, 2026 6/12/26
<= 3.6.0
Node.js icon

@kilocode / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
Low May 17, 2026 5/17/26
<= 7.0.47
Node.js icon

@actual-app / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
Medium July 7, 2026 7/7/26
< 26.6.0
Node.js icon

@wakaru / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
High July 28, 2026 7/28/26
>= 1.0.0, < 1.4.0
Node.js icon

@genql / cli

1 vulnerabilities found
Title Severity Exploit Date Affected versions
High July 16, 2026 7/16/26
< 6.3.4

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