v1.0.9910.2 MB
MIT
strict
core24
CVE Scanner CLI
CVE Scanner CLI is a command-line security CVE lookup utility designed to help developers, system administrators, and security researchers quickly search and analyze known vulnerabilities from public CVE databases.
CVE (Common Vulnerabilities and Exposures) identifiers are widely used in cybersecurity to track and reference security flaws in software and systems. This tool simplifies the process of looking up those vulnerabilities directly from the terminal without needing to visit multiple websites or dashboards.
The tool supports two primary search modes:
• CVE ID Search
You can directly query a specific vulnerability using its CVE identifier (for example: CVE-2024-XXXX). The tool fetches structured information such as description, publication date, last modified date, severity scores, and external references.
• Keyword Search
You can search vulnerabilities based on software names, technologies, or general keywords. This is useful when you are exploring potential security issues in a system or library.
The results are displayed in a clean, color-formatted terminal interface using the Rich library, making it easier to read and understand security data at a glance.
Internally, the tool integrates with public vulnerability data sources such as CIRCL and NVD APIs to retrieve up-to-date CVE information. It processes and formats the raw API responses into a structured and human-readable output.
This CLI is designed to be lightweight, fast, and easy to use. It can be executed in interactive mode or via direct command-line arguments, making it suitable for both quick lookups and scripting workflows.
CVE Scanner CLI is especially useful for:
- Developers checking dependency vulnerabilities
- Security analysts performing quick CVE lookups
- DevOps engineers integrating vulnerability checks into workflows
- Students learning about cybersecurity and CVE tracking systems
The goal of this tool is to make vulnerability information more accessible directly from the terminal, reducing the need for external tools or manual searches while improving workflow efficiency.
CVE (Common Vulnerabilities and Exposures) identifiers are widely used in cybersecurity to track and reference security flaws in software and systems. This tool simplifies the process of looking up those vulnerabilities directly from the terminal without needing to visit multiple websites or dashboards.
The tool supports two primary search modes:
• CVE ID Search
You can directly query a specific vulnerability using its CVE identifier (for example: CVE-2024-XXXX). The tool fetches structured information such as description, publication date, last modified date, severity scores, and external references.
• Keyword Search
You can search vulnerabilities based on software names, technologies, or general keywords. This is useful when you are exploring potential security issues in a system or library.
The results are displayed in a clean, color-formatted terminal interface using the Rich library, making it easier to read and understand security data at a glance.
Internally, the tool integrates with public vulnerability data sources such as CIRCL and NVD APIs to retrieve up-to-date CVE information. It processes and formats the raw API responses into a structured and human-readable output.
This CLI is designed to be lightweight, fast, and easy to use. It can be executed in interactive mode or via direct command-line arguments, making it suitable for both quick lookups and scripting workflows.
CVE Scanner CLI is especially useful for:
- Developers checking dependency vulnerabilities
- Security analysts performing quick CVE lookups
- DevOps engineers integrating vulnerability checks into workflows
- Students learning about cybersecurity and CVE tracking systems
The goal of this tool is to make vulnerability information more accessible directly from the terminal, reducing the need for external tools or manual searches while improving workflow efficiency.
Update History
v1.0.8 (8) → v1.0.9 (9)18 Apr 2026, 13:15 UTC
v1.0.7 (7) → v1.0.8 (8)17 Apr 2026, 08:45 UTC
v1.0.6 (6) → v1.0.7 (7)11 Apr 2026, 11:29 UTC
v1.0.3+git1.310a39e (4) → v1.0.6 (6)11 Apr 2026, 10:45 UTC
v1.0.0+git1.b1b32a5 (1) → v1.0.3+git1.310a39e (4)10 Apr 2026, 08:29 UTC
v1.0.2+git1.100c5f4 (3) → v1.0.0+git1.b1b32a5 (1)10 Apr 2026, 08:25 UTC
10 Apr 2026, 07:17 UTC
18 Apr 2026, 13:11 UTC
10 Apr 2026, 07:29 UTC

