AI Sec Watch dataset
AI Sec Watch aggregates, classifies, and enriches AI and LLM security data from 81 sources. Each record includes 48 structured fields with LLM-based classification, EPSS scores, CISA KEV status, CAPEC mappings, and MITRE ATLAS technique IDs. It is maintained by an information systems security researcher, named at the end of this page.
- Records
- 9,532
- Fields per record
- 48
- Data sources
- 81
- Date coverage
- Jan 2014 to Nov 2026
- Last updated
- Nov 4, 2026
- License
- CC-BY-4.0
- How to cite
- Citation formats
Full dataset export
9,532 issues, 48 fields per record, CC-BY-4.0 licensed
Programmatic access
| Format | Endpoint | Description |
|---|---|---|
| REST API (JSON) | /api/v1/issues | Filterable, paginated JSON with all enrichment fields |
| CSV export | /api/issues/export | Full dataset download as comma-separated values |
| STIX 2.1 bundle | /api/v1/issues/stix | Threat intelligence format for MISP and OpenCTI |
No authentication is required, the limit is 60 requests per minute, and CORS is enabled. See the full API docs.
Quick start
import pandas as pd
# Load full dataset (CSV)
df = pd.read_csv("https://aisecwatch.com/api/issues/export")
# Or use the JSON API with filtering
import requests
resp = requests.get("https://aisecwatch.com/api/v1/issues", params={
"severity": "critical",
"limit": 100,
})
data = resp.json()["data"]No API key is required. The limit is 60 requests per minute, and all data is licensed CC-BY-4.0.
What's included
Core fields
- Title, summary, solution
- Source name and URL
- CVE ID, severity, issue type
- Labels, affected vendors
- Published and processed dates
Enrichment fields
- EPSS exploit probability score and the date it was read
- CISA KEV exploitation status and listing date
- CAPEC attack pattern IDs
- MITRE ATLAS technique IDs
- CVSS vector and parsed components
Classification fields
- Attack sophistication level
- Impact type (CIA + safety)
- AI component targeted
- LLM-specific flag
- Research category (peer-reviewed, preprint, industry, blog)
- Classifier confidence (0-1)
Metadata and derived fields
- Cross-reference count
- Exploit maturity status
- Patch availability
- Disclosure date
- Source priority level (1-3)
- Severity source (CVSS, LLM, or none)
- Issue type source (override, CVE-inferred, LLM)
- Source category (academic, news, vendor, etc.)
- Classifier and summary prompt versions
How it works
- 1.
Collect
83 configured data sources fetched every six hours, including NVD, CISA KEV, GitHub Advisory, arXiv, and cybersecurity and AI news feeds. View all sources.
- 2.
Deduplicate
Incoming items are deduplicated by URL and CVE ID to prevent double-counting.
- 3.
Classify
Each item is processed by an LLM using a versioned prompt (currently v4) that assigns severity, issue type, attack type, affected vendors, and a confidence score (0 to 1).
- 4.
Enrich
Vulnerabilities with CVE IDs are enriched with EPSS exploit probability scores (FIRST API), CISA Known Exploited Vulnerabilities catalog status, CWE-to-CAPEC attack pattern mapping, and CVSS vector parsing.
- 5.
Deliver
Data is accessible via the web interface, public REST API (60 req/min, CORS enabled), STIX 2.1 threat intelligence feed, webhooks with HMAC-SHA256 signing, RSS feeds by category, and CSV export.
Enrichment details
- EPSSExploit Prediction Scoring System
- 30-day exploit probability from FIRST. Scores range from 0 to 1, indicating how likely a vulnerability is to be exploited in the wild within the next 30 days.
- CISA KEVKnown Exploited Vulnerabilities Catalog
- Known exploitation status from CISA, including whether the vulnerability has been observed in active exploitation and whether it is associated with ransomware campaigns.
- CAPECCommon Attack Pattern Enumeration and Classification
- Attack pattern taxonomy mapping derived from CWE IDs. Maps weaknesses to known attack patterns to help defenders understand exploitation techniques.
- CVSS v3.xCommon Vulnerability Scoring System
- Vector string parsing for attack characteristics including attack vector, complexity, privileges required, user interaction, and impact metrics.
- MITRE ATLASAdversarial Threat Landscape for AI Systems
- AI/ML-specific attack taxonomy mapping. Attack types identified by the classifier are mapped to ATLAS technique IDs, enabling alignment with enterprise AI risk frameworks.
How to cite
If you reference AI Sec Watch or use its dataset in academic work, industry reports, or threat intelligence analysis, please use one of the citation formats below. You can copy the citation text or download it as a file for import into your reference manager (Zotero, Mendeley, EndNote, etc.).
Citing the platform
Use this when referencing the AI Sec Watch website, its intelligence feed, or its methodology.
@misc{luu2026aisecwatch,
author = {Luu, Truong (Jack)},
title = {{AI Sec Watch}: A Security Intelligence Platform for {AI} Systems},
year = {2026},
url = {https://aisecwatch.com},
note = {Accessed: 2026-11-04}
}Citing the dataset
Use this when using exported data (CSV, JSON, JSONL) from AI Sec Watch in quantitative analysis or machine learning experiments.
@misc{luu2026aisecwatch_dataset,
author = {Luu, Truong (Jack)},
title = {{AI Sec Watch Dataset}: {AI/LLM} Security Threat Intelligence},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.19519469},
url = {https://doi.org/10.5281/zenodo.19519469},
note = {Data set. 48 fields per record, in CSV, JSON and JSONL. Accessed: 2026-11-04}
}Example usage in a paper
- Data source description: “We collected AI security threat intelligence from AI Sec Watch (Luu, 2026), a platform that aggregates and classifies vulnerabilities from 81 sources using LLM-based classification.”
- Dataset reference: “The AI Sec Watch Dataset (Luu, 2026) contains 9,532 structured records with 48fields per issue, including EPSS scores, CISA KEV status, and MITRE ATLAS technique mappings.”
- API reference: “Threat data was retrieved via the AI Sec Watch REST API (Luu, 2026), which provides structured JSON responses with enrichment from EPSS, CISA KEV, and MITRE ATLAS.”
Versions
A release is a frozen copy with its own DOI, archived on Zenodo, and it does not change. Cite a release when an analysis must be repeatable. The downloads above are generated from the live database at the time of the request, so their record counts change after each fetch.
| Release | Published | Records | Fields | Formats | DOI |
|---|---|---|---|---|---|
| 4.0 | 2026-10-10 | 8,260 | 48 | CSV, JSON, JSONL | 10.5281/zenodo.23282466 |
| 3.0 | 2026-04-11 | 3,020 | 44 | CSV | 10.5281/zenodo.19519470 |
- Latest release, any version
- 10.5281/zenodo.19519469
- Classifier prompt, live data
- v4
- First archived release
- 2026-04-11
- Live data last updated
- Nov 4, 2026
Documentation
- Guide for researchersWhat a record is, where each value comes from, and how to cite a release
- Lab exercises for coursesFour exercises with outcomes, steps and deliverables
- MethodsScope rule, prompts, enrichment and limits
- Label reliabilityAgreement statistics for the classifier fields, with the sample
- CorrectionsPublic log of corrected records
- API documentationEndpoints, parameters, examples
- Data sources83 monitored sources with live health status
- StatisticsTrends, distributions, analytics
Maintained by
Truong (Jack) Luu
Assistant Professor of Information Systems and Analytics, Texas State University. Ph.D. in Information Systems, University of Cincinnati.