Red Hat Security Data API · Search
access-redhat-com/vulnerabilities/searchGet developer and code data with Red Hat Security Data API · Search from Alexandria through one Spiral API key. You need Red Hat's CVE list for a package, product, severity or date range (e.g. critical openssl CVEs Red Hat published this year, or which CVEs an RHSA covers), or Red Hat severity for up to 50 CVE ids at once. It runs in the background and returns structured JSON. Pay as you go, with no subscription.
Pricing
$0.00873 per call.
Limits
- Runs
- In the background
- Returns
- json
- Longest queue wait
- 1 hour
- Run deadline
- 5 minutes
- Longest run, end to end
- 225 minutes
- Largest inline input
- 1 MB
- Largest input file
- 2 GB
- Largest output
- 5 GB
Input
| Field | Kind | Default | Description |
|---|---|---|---|
cwe | text | — | CWE id, e.g. CWE-79 or 79. Pattern: ^\s*([Cc][Ww][Ee]-)?[0-9]{1,6}\s*$. |
cursor | text | — | next_cursor from the previous page; keep the other inputs unchanged. Pattern: ^[0-9]{1,5}$. |
cve_ids | list | — | Only these CVE ids (up to 50). |
package | text | — | Package name as Red Hat names it, e.g. openssl, kernel, log4j (matches fixed and affected packages). |
product | text | — | Red Hat product name, e.g. Red Hat Enterprise Linux 9. |
severity | one of low, moderate, important, critical, Low, Moderate, Important, Critical | — | Red Hat threat severity. |
page_size | number 1 to 100 | 20 | Results per page (default 20). Lower it when a page of heavily packaged CVEs exceeds the 1 MiB read limit. |
advisory_id | text | — | Only CVEs fixed by this erratum, e.g. RHSA-2021:5137. Pattern: ^\s*[Rr][Hh][SsBbEe][Aa]-[0-9]{4}:[0-9]{4,9}\s*$. |
bugzilla_id | text | — | Red Hat Bugzilla id. Pattern: ^\s*[0-9]{1,10}\s*$. |
min_cvss3_score | number 0 to 10 | — | Only CVEs whose Red Hat CVSS v3 score is at least this. |
published_after | text | — | Public on or after this date, YYYY-MM-DD. Pattern: ^\s*[0-9]{4}-[0-9]{2}-[0-9]{2}\s*$. |
published_before | text | — | Public before this date, YYYY-MM-DD. Pattern: ^\s*[0-9]{4}-[0-9]{2}-[0-9]{2}\s*$. |
Same request in code
curl https://api.spiral.ai/v1/runs \
-H "Authorization: Bearer $SPIRAL_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"provider": "alexandria",
"model": "access-redhat-com/vulnerabilities/search",
"input": {
"cwe": "<cwe>"
}
}'Frequently asked questions
How much does Red Hat Security Data API · Search cost?
$0.00873 per call. You pay as you go from one Spiral balance, with no subscription, and a failed run is not charged.
How do I use Red Hat Security Data API · Search through an API?
Send `POST /v1/runs` with `"provider": "alexandria"`, `"model": "access-redhat-com/vulnerabilities/search"` and the input fields on this page, using one Spiral API key. It runs in the background: poll the run, or name a webhook to be told when it finishes.
Do I need an account with Alexandria to use Red Hat Security Data API · Search?
No. Spiral runs it on its own Alexandria account and charges your Spiral balance.
Can my AI agent use Red Hat Security Data API · Search?
Yes. Agents find and run it through Spiral's MCP server, CLI or agent skill, with the same API key.