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
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
affectedComponentstringThe vulnerable function, module, package, or call site.
attackVectorstringHow an attacker can reach or influence the vulnerable behavior.
codeobjectVulnerable code, patched code, and a unified patch diff.
exploitPatharrayA multi-step chain from attacker action to successful exploitation.
impactstringThe resulting confidentiality, integrity, or availability consequence.
mitigationstringThe secure remediation approach.
referencesobjectCVE, CWE, ATT&CK, commit, and advisory metadata when available.
rootCausestringThe implementation decision or condition creating the weakness.
vulnerabilitystringA concise description of the exploitable defect.
weaknessstringThe 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
Get Started
Request a Sample
Share your target domains and the OTS team will follow up with sample data and next steps.