Modern CLI for exploring vulnerability data with powerful search, filtering, and analysis capabilities
vulnx is the next generation of cvemap - we recommend upgrading to vulnx for the latest features and improvements.
⚠️ Important: cvemap uses an older API version that will be discontinued on August 1, 2025.
# 1. Get vulnx go install github.com/projectdiscovery/cvemap/cmd/vulnx@latest # 2. Explore commands vulnx --help vulnx search --help # 3. Start exploring vulnerabilities (no API key required) vulnx filters # See all available search fields vulnx search apache # Basic search (subject to rate limits) # 4. Set up your API key (recommended to avoid rate limits) vulnx auth # Get free API key at https://cloud.projectdiscovery.io # 5. Enhanced exploration with higher limits vulnx search apache # No rate limits vulnx id CVE-2021-44228 # Faster responsesSearch vulnerabilities with precision:
vulnx search "severity:critical && is_remote:true" vulnx search "apache || nginx" --limit 20 vulnx search "cvss_score:>8.0 && cve_created_at:2024"Get detailed vulnerability info:
vulnx id CVE-2021-44228 vulnx id CVE-2024-1234 --jsonAnalyze vulnerability patterns:
vulnx analyze --fields severity vulnx analyze --fields affected_products.vendor| Command | Purpose | Example |
|---|---|---|
search | Find vulnerabilities with advanced filters | vulnx search "apache && severity:high" |
id | Get details for specific CVE | vulnx id CVE-2021-44228 |
filters | List all available search fields and filters | vulnx filters |
analyze | Aggregate data by fields | vulnx analyze -f severity |
auth | Configure API access | vulnx auth |
version | Show version info and check for updates | vulnx version |
update | Update vulnx to latest version | vulnx update |
healthcheck | Test connectivity | vulnx healthcheck |
Output formats:
vulnx search "apache" --json # Machine-readable JSON vulnx search "apache" --output results.json # Save to file vulnx search "apache" --silent # Quiet outputSearch control:
vulnx search "apache" --limit 50 # Get 50 results vulnx search "apache" --sort-desc cvss_score # Sort by CVSS score vulnx search "apache" --fields cve_id,severity # Specific fields onlyAdvanced search:
vulnx search --term-facets severity=5,tags=10 "apache" vulnx search --range-facets numeric:cvss_score:high:8:10 "remote" vulnx search --highlight "apache" # Enable search highlighting vulnx search --facet-size 20 "nginx" # More facet buckets vulnx search --detailed "xss" # Detailed output like 'id' commandExplore what you can search on:
vulnx filters # Show all available search fields vulnx filters --json # Machine-readable field list vulnx filters --output fields.json # Save field info to fileThe filters command shows detailed information about all searchable fields including:
- Field names and data types
- Descriptions and examples
- Whether fields support sorting and faceting
- Available enum values for specific fields
- Search analyzer types
Example output:
Field: severity Data Type: string Description: Vulnerability severity level (e.g., critical, high, medium, low, info) Can Sort: Yes Facet Possible: Yes Search Analyzer: keyword-lower Examples: severity:critical, severity:high Enum Values: critical, high, medium, low, info, unknown Total: 69 filters available Use this command to discover new search possibilities and understand field syntax before building complex queries.
Find high-risk vulnerabilities:
vulnx search "severity:critical && is_remote:true && is_kev:true" vulnx search "cvss_score:>8.0 && cve_created_at:>=2024" # High CVSS from 2024 vulnx search "is_kev:true && age_in_days:<90" # Recent KEV exploitsSearch by technology:
vulnx search "apache" # Apache vulnerabilities vulnx search "apache || nginx" # Multiple technologies vulnx search "affected_products.vendor:microsoft" # By vendorFilter by severity and scores:
vulnx search "severity:high" # High severity vulnx search "cvss_score:>7.0" # CVSS score above 7 vulnx search "epss_score:>0.8" # High EPSS scoreTime-based searches:
vulnx search "cve_created_at:>=2024" # Published in 2024 or later vulnx search "cve_created_at:>=2024-01-01 && cve_created_at:<2024-07-01" # First half of 2024 vulnx search "age_in_days:<30" # Recent vulnerabilities (last 30 days)Find exploitable vulnerabilities:
vulnx search "is_poc:true" # Has proof of concept vulnx search "is_kev:true" # Known exploited vulns vulnx search "is_template:true" # Has Nuclei templates vulnx search --detailed "log4j" # Detailed analysis of specific vuln| Flag | Short | Description | Example |
|---|---|---|---|
--product | -p | Filter by products | --product apache,nginx |
--vendor | Filter by vendors | --vendor microsoft,oracle | |
--severity | -s | Filter by severity | --severity critical,high |
--tags | Filter by tags | --tags rce,injection | |
--cvss-score | Filter by CVSS score | --cvss-score ">8.0" | |
--epss-score | Filter by EPSS score | --epss-score ">0.8" | |
--vuln-age | -a | Filter by age | --vuln-age "<30" |
--vuln-type | Filter by vulnerability type | --vuln-type sql_injection | |
--kev | KEV vulnerabilities only | --kev | |
--template | -t | Has Nuclei templates | --template |
--poc | Has proof of concept | --poc | |
--hackerone | HackerOne reported | --hackerone | |
--remote-exploit | Remotely exploitable | --remote-exploit | |
--vuln-status | Filter by vuln status | --vuln-status confirmed |
| Flag | Short | Description | Example |
|---|---|---|---|
--detailed | Detailed output like 'id' | --detailed | |
--highlight | Enable search highlighting | --highlight | |
--limit | -n | Number of results | --limit 50 |
--offset | Pagination offset | --offset 100 | |
--sort-asc | Sort ascending | --sort-asc cvss_score | |
--sort-desc | Sort descending | --sort-desc cve_created_at | |
--fields | Select specific fields | --fields cve_id,severity | |
--term-facets | Calculate term facets | --term-facets severity=5 | |
--range-facets | Calculate range facets | --range-facets numeric:cvss_score:high:8:10 | |
--facet-size | Facet bucket count | --facet-size 20 |
Product and vendor filtering:
vulnx search --product apache,nginx # Filter by products (searches both vendor and product fields) vulnx search --vendor microsoft,oracle # Filter by vendors only vulnx search "NOT apache" # Exclude products using query syntax vulnx search "NOT affected_products.vendor:microsoft" # Exclude vendors using query syntaxSeverity and scoring:
vulnx search --severity critical,high # Filter by severity vulnx search "NOT severity:low" # Exclude severities using query syntax vulnx search --cvss-score ">8.0" # Filter by CVSS score vulnx search --epss-score ">0.8" # Filter by EPSS score vulnx search --vuln-status confirmed # Filter by status vulnx search --vuln-age "<30" # Recent vulnerabilitiesExploit characteristics:
vulnx search --kev # KEV vulnerabilities only vulnx search --template # Has Nuclei templates vulnx search --poc # Has proof of concept vulnx search --hackerone # HackerOne reported vulnx search --remote-exploit # Remotely exploitableMultiple input methods:
# Single ID lookup vulnx id CVE-2024-1234 # Multiple IDs (comma-separated) vulnx id CVE-2024-1234,CVE-2024-5678,CVE-2023-9999 # Auto-detection from stdin (no 'id' command needed!) echo "CVE-2024-1234" | vulnx echo -e "CVE-2024-1234\nCVE-2024-5678" | vulnx # File input vulnx id --file ids.txtBatch processing:
# JSON output for automation vulnx id --json CVE-2024-1234 CVE-2024-5678 # Save to file vulnx id --output vulns.json --file ids.txt # Pipeline integration cat report.txt | grep -o 'CVE-[0-9]\{4\}-[0-9]\+' | vulnx id --json| Field | Description | Example Values |
|---|---|---|
severity | Vulnerability severity | low, medium, high, critical |
cvss_score | CVSS score (0-10) | 7.5, >8.0, <9.0 |
cve_id | CVE identifier | CVE-2021-44228 |
is_remote | Remotely exploitable | true, false |
is_kev | Known exploited vuln | true, false |
is_poc | Has proof of concept | true, false |
affected_products.vendor | Vendor name | apache, microsoft |
affected_products.product | Product name | tomcat, windows |
cve_created_at | Publication date | >=2024, >2024-01-01, <2023 |
age_in_days | Days since publication | <30, >365, <=90 |
Basic searches:
vulnx search "apache" # Simple term vulnx search "remote code execution" # Phrase search vulnx search "severity:critical" # Field searchBoolean logic:
vulnx search "apache && nginx" # Both terms vulnx search "apache || nginx" # Either term vulnx search "apache NOT tomcat" # Exclude term vulnx search "(apache || nginx) && severity:high" # GroupedRanges and wildcards:
vulnx search "cvss_score:>8.0" # Greater than vulnx search "cvss_score:<9.0" # Less than vulnx search "cve_created_at:>=2024-01-01" # Date comparison vulnx search "age_in_days:<30" # Recent vulnerabilities vulnx search "apache*" # WildcardImportant: Date fields require comparison operators (>=, >, <, <=).
Single date comparisons:
vulnx search "cve_created_at:>=2024" # CVEs from 2024 onward vulnx search "cve_created_at:<2024" # CVEs before 2024 vulnx search "cve_created_at:>2024-06-01" # CVEs after June 1, 2024Date ranges:
# CVEs from January 2024 only vulnx search "cve_created_at:>=2024-01-01 && cve_created_at:<2024-02-01" # High CVSS CVEs from 2024 vulnx search "cvss_score:>8.0 && cve_created_at:>=2024" # Recent vulnerabilities (age-based) vulnx search "age_in_days:<30" # Last 30 days vulnx search "age_in_days:>365" # Older than 1 yearSupported formats:
2024(year)2024-01(year-month)2024-01-15(full date)
vulnx works without an API key, but authentication provides significant benefits:
- Limited to 10 requests per minutes
- Subject to strict rate limits
- May encounter "429 Too Many Requests" errors
✅ With API key:
- Much higher rate limits
- Access to all the filters
Set up authentication:
vulnx auth # Interactive setup vulnx auth --api-key YOUR_API_KEY # Non-interactive (automation) vulnx auth --test # Test current API key export PDCP_API_KEY="your-key-here" # Environment variableAuthentication modes:
- Interactive:
vulnx auth- Guided setup with prompts - Non-interactive:
vulnx auth --api-key KEY- Perfect for automation/CI/CD - Test only:
vulnx auth --test- Validate current configuration
Version management:
vulnx version # Show version and check for updates vulnx version --disable-update-check # Show version without update check vulnx update # Update to latest version vulnx --update # Alternative update commandGlobal options:
vulnx --json search "apache" # JSON output vulnx --silent search "apache" # No banner vulnx --timeout 60s search "apache" # Custom timeout vulnx --disable-update-check search "apache" # Disable automatic update checksRate limit issues:
Rate limit exceeded! API key required for higher limits. → Run: vulnx auth to configure API key and get higher limits Automation/CI/CD setup:
# Docker containers vulnx auth --api-key "$SECRET_API_KEY" # CI/CD pipelines vulnx auth --api-key "${PDCP_API_KEY}" # Kubernetes init containers vulnx auth --api-key "$(cat /secrets/api-key)" # Test authentication in scripts vulnx auth --test && echo "Auth OK" || echo "Auth failed"Rate limit suggestions:
Configure API key with 'vulnx auth' to avoid rate limits → This appears when no API key is configured. To remove: 1. Set up API key: vulnx auth 2. Or use --silent flag to suppress informational messages No results:
vulnx search "is_kev:true" --limit 1 # Test with known results vulnx healthcheck # Check connectivityLarge result sets:
vulnx search "apache" --limit 100 # Increase limit vulnx search "apache" --offset 100 # Pagination vulnx search --fields cve_id,severity "apache" # Fewer fieldsConnection issues:
vulnx --timeout 60s search "apache" # Increase timeout vulnx --proxy http://localhost:8080 search "apache" # Use proxy vulnx --debug search "apache" # Debug modeHelp commands (no API key required):
vulnx --help # All commands overview vulnx search --help # Search command help vulnx id --help # ID command help vulnx filters --help # Filters command help vulnx analyze --help # Analyze command help vulnx version # Version info with update check vulnx version --disable-update-check # Version info without update checkData exploration (subject to rate limits without API key):
vulnx filters # Show all searchable fields vulnx search help # Detailed search fields vulnx analyze help # Available analyze fields
⚠️ Note All commands work without an API key, but are subject to rate limits. Configure an API key withvulnx authfor higher limits and better performance.
- Start immediately: vulnx works without an API key - just run
vulnx search apache - Avoid rate limits: Configure API key with
vulnx authfor heavy usage - Stay updated: vulnx automatically checks for updates; use
--disable-update-checkto disable - Use
vulnx filtersto discover all available search fields and their syntax - Start with broad searches, then narrow down with filters
- Use
--jsonfor scripting and automation - Combine multiple filters for precise results
- Use
analyzeto understand data patterns - Save frequently used queries as shell aliases
For advanced usage patterns and examples, see USAGE.md.
For development setup, code quality checks, and contribution guidelines, see DEVELOPMENT.md.
vulnx is distributed under MIT License.
![@dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=64&v=4){kind=small}
![@cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=64&v=4){kind=small}