cvss-score-extraction

Extract CVSS v3/v3.1 scores from NVD, GHSA, and RedHat with v2 fallback.

4|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/GeneralReasoning/env-skillsbench --skill cvss-score-extraction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cvss-score-extraction
Source: https://github.com/GeneralReasoning/env-skillsbench/tree/main/software-dependency-audit/environment/skills/cvss-score-extraction
Command: npx skills add https://github.com/GeneralReasoning/env-skillsbench --skill cvss-score-extraction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CVSS score extraction from vulnerability datasets can be inconsistent when sources differ. This guide explains how to derive a stable score using a priority cascade across NVD, GHSA, and RedHat, with sensible fallbacks.

Core Features & Use Cases

  • Source priority: Prefer CVSS v3/v3.1 scores from NVD, then GHSA, then RedHat.
  • Multi-source fallback: Gracefully degrade to v2 or 'N/A' when newer scores are missing.
  • Reporting readiness: Outputs a clean numeric score or an explicit 'N/A' for dashboards and reports.
  • Use Case: Generate consistent risk ratings for vulnerability reports across heterogeneous feeds such as NVD and GHSA.

Quick Start

Compute the CVSS v3 score for a vulnerability using the primary NVD source, with GHSA and RedHat as fallbacks.

Frequently Asked Questions about cvss-score-extraction

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract CVSS v3 scores from NVD when vulnerability data sources are inconsistent?

Extract CVSS v3 scores using a priority cascade that prefers NVD data, falling back to GHSA and RedHat sources when NVD scores are missing, ensuring consistent vulnerability risk scoring across heterogeneous feeds.

What is the best way to handle missing CVSS v3 scores in vulnerability datasets?

Handle missing CVSS v3 scores by implementing a multi-source fallback mechanism that gracefully degrades to CVSS v2 scores from NVD, GHSA, or RedHat, returning an explicit 'N/A' when no score exists.

Does CVSS score extraction support parsing nested vulnerability data structures?

CVSS score extraction supports parsing nested vulnerability data structures to retrieve v3/v3.1 scores from primary sources like NVD, with multi-source fallbacks to ensure accurate risk scoring for dashboards and reports.

Why does my vulnerability report show inconsistent CVSS scores from GHSA and NVD?

Inconsistent CVSS scores occur when sources differ. A priority cascade standardizes extraction by preferring NVD v3 scores, then GHSA and RedHat, with v2 fallback, to generate consistent risk ratings across feeds.

Can I use CVSS score extraction to generate clean numeric outputs for vulnerability dashboards?

CVSS score extraction outputs a clean numeric score or an explicit 'N/A' for vulnerability dashboards and reports. It prioritizes v3/v3.1 scores from NVD, GHSA, and RedHat to ensure reporting readiness.

What are the limitations of using CVSS v2 fallback for vulnerability risk scoring?

CVSS v2 fallback is a limitation used only when v3 scores are unavailable across NVD, GHSA, and RedHat. It provides risk scoring continuity but lacks the granular base metrics of CVSS v3/v3.1 standards.