extract 0 0 0

aavhawkeye/cve-red-team-v1

published by @aavhawkeye

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
137
Last 30 days
6
Likes
1
Size
1.8 MB
Created on HF
2025-12-24
Age
10 months ago

Description

Attack Vector Fine-tuning Dataset

This is a .json dataset of 3,660 synthetic instruction-tuning examples. It is intended to assist in training language models for automated red-teaming tasks, specifically focusing on the analysis of CVEs (Common Vulnerabilities and Exposures).

Source Data

The examples are derived from the official CVEListV5 repository, providing consensus vulnerability descriptions and standardized CVSS metrics.

Dataset Structure… See the full description on the dataset page: https://huggingface.co/datasets/aavhawkeye/cve-red-team-v1.

Tags

license:cc-by-nc-nd-4.0size_categories:1K<n<10Kformat:jsonmodality:textlibrary:datasetslibrary:pandaslibrary:polarslibrary:mlcroissantregion:us

README current version from Hugging Face


license: cc-by-nc-nd-4.0

Attack Vector Fine-tuning Dataset

This is a .json dataset of 3,660 synthetic instruction-tuning examples. It is intended to assist in training language models for automated red-teaming tasks, specifically focusing on the analysis of CVEs (Common Vulnerabilities and Exposures).

Source Data

The examples are derived from the official CVEListV5 repository, providing consensus vulnerability descriptions and standardized CVSS metrics.

Dataset Structure

The data uses valid CVE records to create three distinct types of training examples to enhance model capabilities:

  1. Attack Vector Identification: Teaches the model to deduce the primary attack vector (e.g., Network, Local, Physical) solely from the vulnerability description.
  2. Risk Assessment: Trains the model to estimate risk levels (Critical, High, Medium) and base scores based on the description.
  3. Executive Summary: Fine-tunes the ability to generate concise summaries combining the CVE ID, risk level, and attack vector.

Usage

The dataset is provided in a standard JSON format suitable for fine-tuning pipelines. It was generated with python to process raw CVE data, filter for quality (removing short descriptions or unknown vectors), and shuffle the entries for diverse training batches.

README history 3 revisions

Every night we snapshot the README of every dataset in the catalog. When the SHA changes we archive the new version and diff it against the last. This is the evolving thought record of the alignment-data field: what the author decided to say about the corpus, and how that framing shifted over time.

  1. 2025-12-24Update README.md8ce5ac91.3 KB
    Loading...
  2. 2025-12-24Upload dataset and READMEac4eced1.4 KB
    Loading...
  3. 2025-12-24initial commit77d9c5736 B
    Loading...

Used by abliterated models none yet

No abliterated models in our catalog have declared this dataset in their YAML metadata yet. This can mean the dataset is used but not declared, is used outside abliteration workflows, or is new. The link will populate automatically as models are indexed.

Community discussions 1 thread · 1 open · 1 comments

Threads posted by the community on Hugging Face: bug reports, questions about usage, pull requests on the README, license clarifications. Click any thread to expand and read the full conversation inline. Newest first.

  1. 2025-12-25[bot] Conversion to Parquetopen1 💬#1
    Loading...

Related datasets same stage · extract

Read further

Metadata

License
cc-by-nc-nd-4.0

Repository

Download the dataset

0

Copy any of these snippets into your notebook or terminal. All three fetch directly from Hugging Face using your own credentials.

Recommended: datasets library (Python)
from datasets import load_dataset
ds = load_dataset("aavhawkeye/cve-red-team-v1")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="aavhawkeye/cve-red-team-v1", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/aavhawkeye/cve-red-team-v1
Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Open in Abliteration