CVE Finder
Fetch CVEs per application from NVD (National Vulnerability Database) API 2.0.
Installation
pip3 install cve-finder-cli
Or install from source (editable):
pip install -e .
Or from the directory:
python -m pip install .
Usage
After installation, use the cve-finder command:
# Using CPE (exact match)
cve-finder --cpe "cpe:2.3:a:gitlab:gitlab:16.7:*:*:*:*:*:*:*" --json output.json
# Using keyword search
cve-finder --app "nginx" --version "1.24.0" --csv nginx.csv
# Filter by severity and date (case-insensitive)
cve-finder --app "openssl" --severity critical --since 2024-01-01 --max 50
# Multiple severities (repeat flag or comma-separated)
cve-finder --app "jira" --severity CRITICAL --severity MEDIUM
cve-finder --app "jira" --severity CRITICAL,MEDIUM
# Print to console (no file output)
cve-finder --app "tomcat" --version "9.0.0"
Direct script usage
You can also run the entry script directly:
# Best (exact): use a CPE name
python main.py --cpe "cpe:2.3:a:nginx:nginx:1.24.0:*:*:*:*:*:*:*" --csv nginx_1.24.0.csv
# Keyword search (fuzzier)
python main.py --app "nginx" --version "1.24.0" --json out.json
# Keyword search, no version
python main.py --app "openssl" --since 2024-01-01 --max 200 --csv openssl.csv
Options
--cpe- Exact CPE name for precise matching--app- Application name for keyword search--version- Optional version (with --app)--since- Filter CVEs published since date (YYYY-MM-DD)--until- End date for published window--severity- Filter by severity (case-insensitive). Repeat flag or use comma-separated list (LOW, MEDIUM, HIGH, CRITICAL)--max- Maximum CVEs to fetch (default: 1000)--page-size- Results per page (max 200)--timeout- HTTP timeout seconds--json- Save results to JSON file--csv- Save results to CSV file--format- Output format to stdout: json or csv
API Key
Set NVD_API_KEY environment variable to reduce rate limiting:
export NVD_API_KEY="your_key_here"
Get your API key at: https://nvd.nist.gov/developers/request-an-api-key
Metadata
Release files for cve-finder-cli 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cve_finder_cli-1.0.1.tar.gz | 12.9 kB | Without provenance | Details for cve_finder_cli-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cve_finder_cli-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for cve_finder_cli-1.0.1-py3-none-any.whl |
Total release size: 29.7 kB
Release files / cve_finder_cli-1.0.1.tar.gz
| Download URL | cve_finder_cli-1.0.1.tar.gz |
|---|---|
| Size | 12.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b3835a184bf5bcff38538bcad50efb2d3fcf1783e898683939e52855c5418986
|
|
BLAKE2b-256 checksum How to use checksums |
97c3c970b87af7462c6a9f4ba78206c4128e1a3f7a4105e289db19e2c15c509c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / cve_finder_cli-1.0.1-py3-none-any.whl
| Download URL | cve_finder_cli-1.0.1-py3-none-any.whl |
|---|---|
| Size | 16.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1b8e4607992c7810fb4c7c23cd83ffa00d3967f284a88d9d51597de60264fef7
|
|
BLAKE2b-256 checksum How to use checksums |
ccc0f4cf9864d59928f09fefdd66d8eb50d3722a28775f4aef0b1345c492896a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for cve-finder-cli 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.