idmycve - Advanced CVE Search and Reporting Tool
Table of Contents
- About
- Features
- Installation
- Usage
- Configuration
- Output Formats
- Custom Templates
- Performance Optimizations
- Contributing
- License
About
idmycve is a powerful and versatile command-line tool designed for efficient searching, filtering, and reporting of Common Vulnerabilities and Exposures (CVEs) from the National Vulnerability Database (NVD). It integrates with various external data sources like EPSS and Exploit-DB to provide a comprehensive overview of vulnerabilities. Built with a focus on speed and user experience, idmycve offers flexible input options, multiple output formats, and customizable reporting to streamline your vulnerability management workflows.
Features
- Comprehensive CVE Data: Fetches on-demand CVE ID, Description, Affected Products/Versions, CVSS Score (v3.1 and v2.0), CVSS Vector (v3.1 and v2.0), CWE IDs, Last Modified Date, Source Identifier, References, and Publication Date.
- EPSS Integration: Retrieves and displays Exploit Prediction Scoring System (EPSS) scores and percentiles to prioritize vulnerabilities based on exploitability likelihood.
- Exploit Availability: Checks Exploit-DB for known public exploits, providing direct links when available.
- Vulnerability Lifecycle Metrics: Calculates and presents derived metrics such as the age of the vulnerability, days since its last modification, and days between its publication and last modification.
- Flexible Input Options:
- Search for recent CVEs within a specified number of days.
- Query specific CVE IDs provided directly as space-separated arguments.
- Load CVE IDs from various file formats: plain text (
.txt), Excel spreadsheets (.xlsx), JSON files (.json), and XML files (.xml).
- Granular Filtering:
- Filter CVEs by severity level: Critical (
c), High (h), Medium (m), Low (l). - Apply precise filters based on Common Platform Enumeration (CPE) patterns (e.g.,
apache:http_server,microsoft:windows:10). - Filter by a minimum EPSS score (0.0 to 1.0).
- Filter to show only CVEs with known exploits available.
- Filter CVEs by severity level: Critical (
- Multiple Output Formats: Generate reports in Markdown, JSON, HTML, plain text, CSV, XLSX, and XML formats.
- Customizable Output Templates: Utilize Jinja2 templates to create highly tailored and branded reports.
- Interactive Mode: A user-friendly, prompt-based interface for guided searches and report generation.
- Configuration Management: Supports
config.inifor API keys and default search parameters, with an option to generate a sample configuration file. - Performance Optimizations:
- Batch EPSS API Calls: Reduces HTTP requests by querying multiple EPSS scores in a single batch.
- Batch
cve_searchsploitCalls: Minimizes subprocess overhead by checking exploit availability for multiple CVEs in one go. - Parallel Processing for API Calls: Leverages
concurrent.futures.ThreadPoolExecutorto fetch CVE details concurrently, significantly speeding up operations. - Exponential Backoff for NVD API: Enhances robustness and reliability by automatically retrying failed NVD API requests with increasing delays.
- Enhanced User Experience:
- Colorized Severity Indicators: Visually distinguishes severity levels in console and markdown outputs:
CRITICAL: Bold RedHIGH: Bold MagentaMEDIUM: Bold YellowLOW: Bold GreenNONE/N/A: Bold Cyan
- Dynamic Console Output: Features a randomly colored ASCII banner and clear, informative messages.
- Colorized Severity Indicators: Visually distinguishes severity levels in console and markdown outputs:
Installation
PyPI Installation
You can install idmycve directly from PyPI using pip:
pip install idmycve
Development Installation (From Source)
-
Clone the repository:
git clone https://github.com/ghostescript/idmycve cd idmycve
-
Create and activate a virtual environment:
python3 -m venv .venv source .venv/bin/activate
-
Install dependencies:
pip install -e .
Note: The
-e .flag installs the package in editable mode, which is useful for development. -
Install
cve_searchsploit(optional, for exploit availability checks):idmycveintegrates withcve_searchsploitfor exploit availability. If you don't have it, you can install it via pip:pip install cve-searchsploit
Note: Ensure
cve_searchsploitis accessible in your PATH or virtual environment.
Usage
Command-Line Interface (CLI)
python3 idmycve.py --help
Example Commands:
-
Search for recent high-severity CVEs from the last 7 days:
python3 idmycve.py -d 7 -s h
-
Get details for specific CVEs and save as a JSON report:
python3 idmycve.py -i CVE-2024-24919 CVE-2021-44228 -r my_cve_report.json
-
Filter CVEs by CPE (e.g., Apache Log4j):
python3 idmycve.py -i CVE-2021-44228 --cpe-filter "apache:log4j" -r log4j_cpe_report.md
-
Generate a report using a custom Jinja2 template:
python3 idmycve.py -d 14 --template my_custom_template.j2 -r custom_report.txt
-
Generate a sample configuration file:
python3 idmycve.py --generate-config
-
Generate a sample Jinja2 template file:
python3 idmycve.py --generate-template my_custom_template.j2
Interactive Mode
Run the script without any arguments to enter interactive mode:
python3 idmycve.py
Follow the on-screen prompts to perform searches, apply filters, and generate reports.
Configuration
idmycve can use a config.ini file for API keys and default settings. A sample file can be generated using --generate-config.
Example config.ini:
[NVD]
api_key = YOUR_NVD_API_KEY_HERE
[DefaultSearch]
days_ago = 7
severity =
count =
[Output]
default_format = md
Output Formats
Supported output formats include:
- Markdown (
.md) - JSON (
.json) - HTML (
.html) - Plain Text (
.txt) - CSV (
.csv) - Excel (
.xlsx) - XML (
.xml)
Custom Templates
You can provide your own Jinja2 template file using the --template argument. The template will receive a cves variable, which is a list of dictionaries, each representing an extracted CVE with all its details and calculated lifecycle metrics.
Performance Optimizations
The tool incorporates several optimizations to ensure speed without compromising accuracy:
- Batch EPSS API Calls: Multiple EPSS scores are fetched in a single API request.
- Batch
cve_searchsploitCalls: Exploit availability for multiple CVEs is checked with a single subprocess call. - Parallel Processing: Utilizes
concurrent.futures.ThreadPoolExecutorfor concurrent fetching of CVE details from the NVD API. - Exponential Backoff: Implemented for NVD API calls to gracefully handle rate limits and transient network issues.
Contributing
Contributions are welcome! Please feel free to submit pull requests or open issues on the GitHub repository.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Updated On
Dec 18, 2025
Metadata
Release files for idmycve 0.2.6
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 |
|---|---|---|---|---|
| idmycve-0.2.6.tar.gz | 23.2 kB | Without provenance | Details for idmycve-0.2.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| idmycve-0.2.6-py3-none-any.whl | Python 3 | none | any | Details for idmycve-0.2.6-py3-none-any.whl |
Total release size: 43.9 kB
Release files / idmycve-0.2.6.tar.gz
| Download URL | idmycve-0.2.6.tar.gz |
|---|---|
| Size | 23.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dac898073f83cdea2aa40d2ecd472e29165153631aabeb7ce022a67698a01d56
|
|
BLAKE2b-256 checksum How to use checksums |
6308178cb942948eb692d9937a1850e6986d430862ccb55c67998129109d7902
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Release files / idmycve-0.2.6-py3-none-any.whl
| Download URL | idmycve-0.2.6-py3-none-any.whl |
|---|---|
| Size | 20.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e1c403b1da900f9d5b13dcfe9335885819e3e71102a10901b42d0aaa340af88
|
|
BLAKE2b-256 checksum How to use checksums |
ae69221946f33a21b54d5588f450e32449a49e3d93f4b1c53a56ff329a5c6345
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Security for idmycve 0.2.6
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.