Structured software-security tasks spanning Python application security and TypeScript dependency and supply-chain vulnerabilities. Every record pairs vulnerable and patched code with a unified diff.
Available Now · Sample Available
CVE-Class Vulnerability Fix Dataset
Vulnerability diagnosis and verified repair tasks with full CVE/CWE/MITRE ATT&CK metadata.
Volume
0
Volume
Scalable Volume
Coverage
Application Security, Software Supply Chain, Python, TypeScript, Cybersecurity, Coding
0.0
%
Targets
Modality & Delivery
TextCode→CodeText
Formats
JSON
What You Receive
Coverage
Structured software-security tasks covering vulnerability diagnosis and verified repair. Every record includes root-cause and weakness analysis, affected component, attack vector, exploit path, impact, mitigation, vulnerable and patched code, a unified diff, and CVE/CWE/MITRE ATT&CK metadata. The set spans Python application security and TypeScript dependency and supply-chain vulnerabilities.
Package Structure
Differentiators
- Each record traces root cause through exploit path to a secure patched implementation and unified diff.
Record Schema
| Field | Description |
|---|---|
affectedComponent | The vulnerable function, module, package, or call site. |
attackVector | How an attacker can reach or influence the vulnerable behavior. |
code | Vulnerable code, patched code, and a unified patch diff. |
exploitPath | A multi-step chain from attacker action to successful exploitation. |
impact | The resulting confidentiality, integrity, or availability consequence. |
mitigation | The secure remediation approach. |
references | CVE, CWE, ATT&CK, commit, and advisory metadata when available. |
rootCause | The implementation decision or condition creating the weakness. |
vulnerability | A concise description of the exploitable defect. |
weakness | The vulnerability class and associated CWE. |
Results
Methodology & Quality
Methodology
SME involvement
Domain-expert curated with up to L2 review
Stressors
Application-security vulnerabilities and dependency or software-supply-chain weaknesses.
Design criteria
- Keep vulnerability reasoning, remediation, code, and CVE/CWE/ATT&CK metadata together in one record.
Build assumptions
Quality approach
- Records include vulnerable and patched code plus a unified patch diff for repair inspection.
Known limitations
Customization & Scalability
Custom sets available. Additional volume in progress