# SSVC returns an action for a stakeholder and CVSS returns a severity number; they answer different questions and CISA uses both

COMPARISON, read 10 Nov 2026

**The short answer.** CVSS is a severity score from 0.0 to 10.0; SSVC is a decision method that returns an action such as defer, scheduled, out-of-cycle or immediate. CISA's BOD 26-04 uses an SSVC tree with four inputs and no CVSS score. In the KEV Lag Ledger, 33 of 318 KEV additions scored under CVSS 7.0.

- **Maintained by:** SSVC: CERT/CC, with CISA publishing data. CVSS: FIRST
- **Scale:** SSVC: action categories. CVSS: 0.0 to 10.0
- **Current version:** SSVC: CISA outcome group cisa:BOD2604:1.0.0. CVSS: v3.1 and v4.0
- **Updated:** SSVC: per CVE in Vulnrichment. CVSS: on scoring
- **Answers:** SSVC: what this stakeholder should do and how fast. CVSS: the severity of the flaw

## Output and purpose

The CERT/CC documentation contrasts the two directly. Unlike systems that rate technical severity or exploitability, SSVC rates vulnerabilities on risk to the concerned stakeholder, through a stakeholder-defined decision model. CVSS, in FIRST's wording, produces numerical scores indicating the severity of a vulnerability relative to other vulnerabilities.

A CVSS output is a number a person must interpret against a policy. An SSVC output is already the policy: Defer, Scheduled, Out-of-cycle or Immediate for suppliers and deployers, or in the CISA tree Fix on system upgrade, 60 days, 14 days, 3 days, and 3 days with forensic investigation.

Both are public methods, which is the property an auditor values. The CERT/CC site includes calculator and explorer tools for SSVC, and FIRST provides calculators for CVSS. Neither depends on a vendor product. The difference lies in what the user must supply: CVSS needs the metrics for the flaw, and SSVC needs the decision points for the flaw and, for deployers, for the asset.

| Property | SSVC | CVSS |
| --- | --- | --- |
| Output | Action category | Score and band |
| Inputs | Decision points: exploitation, exposure, automatable, technical impact, others | Eight base metrics (v3.1); more in v4.0 |
| Reproducibility | Decision table, inspectable | Formula (v3.1) or MacroVector lookup (v4.0) |
| Stakeholder-specific | Yes, by design | Base is not; Environmental is optional |
| Effort per CVE | Answer the decision points or accept a publisher's answers | Usually supplied with the CVE |

## Where they overlap

SSVC borrows from CVSS. The CERT/CC reference lists CVSS-based decision points, including a CVSS v4 analyst model, so the two can be used together. BOD 26-04 itself states that its Technical Impact concept is similar to the CVSS base score's concept of severity, and that the remediation table is informed by SSVC.

Technical Impact in the CISA tree is binary: the adversary gains partial or total control of the asset. CVSS spreads similar information across confidentiality, integrity and availability impact, attack vector and privileges. The SSVC form discards detail in return for a decision.

The KEV feed also shows SSVC at work in the data: current entries carry a forensicTriage field, which was Yes for 103 of the 1,779 entries on 2026-11-10. That field lines up with the 3 days and forensic investigation outcome in the CISA tree. CVSS has no counterpart to it, because a severity score carries no instruction about checking an asset for compromise.

## What CISA does with them

CISA's Vulnrichment repository takes each CVE through SSVC scoring, recording Exploitation, Automatable and Technical Impact. For CVEs rated Total Technical Impact, Automatable, or with Exploitation of proof of concept or active, CISA considers adding CWE and CVSS data where the CNA has not. CISA therefore uses SSVC to decide where to spend effort on CVSS.

The NVD, since 2026-06-17, carries CISA's SSVC data next to CVSS in the same record, with a Computed SSVC Score showing how the priority was decided. A program that reads the NVD receives both.

Because CISA enriches the CVE record rather than a separate database, any consumer of CVE data can read it. The Vulnrichment README states that CISA never overwrites the originating CNA's data and adds its own values in the ADP container, so a CVSS value from a CNA and an SSVC answer from CISA can sit side by side in one record, each with its author.

## What the ledger shows

CVSS performed as a severity indicator on the 318 KEV additions in the ledger window: median 8.8, 285 at 7.0 or above. It also left 33 below 7.0, which is 10.4 percent, and the median gap from NVD publication to listing was 27 days for those 33 against 8.0 days for entries scored 9.0 or above.

An SSVC tree handles that gap by letting In KEV decide. The ledger cannot test an SSVC tree, because exposure is an asset property that a vulnerability dataset does not hold. It can show that the vulnerability-side inputs CISA publishes, KEV status among them, carry information that the CVSS score alone did not.

## Cost and adoption

SSVC costs effort at the start: someone must define the tree, answer the decision points that are specific to the organization and keep the table under change control. CVSS costs nothing at the start, because the CNA or NVD supplies it. The CERT/CC pages organize getting started into steps titled Prepare, Collect, and Use and Respond.

A staged adoption is workable. Keep CVSS for severity reporting, adopt the CISA tree for KEV-listed CVEs, and extend to other CVEs when asset exposure data is reliable.

## What to write down

Record which tree is in use, its version and the date of the last review. Record, per decision, the answer to each decision point and who gave it. For CVSS, record the version, the vector, the source and the read date.

The two records together let an auditor ask why an item received its category and get an answer in two lines.

The questions an auditor can then ask are concrete: the tree that produced a timeline, its version, the person who answered the exposure decision point for the asset and the date, and the CVSS version and vector shown in the severity column. Each has a recorded answer, and neither method is accepted on reputation. A short register of these answers, one line per exception, is usually enough for a year-end review.

## Verdict by situation

- **Federal agencies and contractors:** Rank by the SSVC outcome first, using the CISA BOD 26-04 tree, because the directive's timelines come from it and CVSS is not one of its inputs.
- **Large enterprises with ten or more scanners:** Rank by an SSVC-style decision first for tiered assets, because a decision table can carry exposure and business impact that a CVSS score cannot.
- **Managed security providers:** Rank by CVSS first for the cross-client report, because every client already understands it, and add the CISA SSVC fields as a second column.
- **Mid-size teams replacing Kenna or a spreadsheet:** Rank by CVSS first for severity and KEV as the override, and adopt the CISA SSVC tree later, since a small team needs to start with inputs it can fill.
- **Application security and infrastructure in one queue:** Rank by CVSS first for application findings, which carry CVSS vectors from the testing tool, and by SSVC outcome for CVEs that CISA has assessed.

## Other comparisons

- [EPSS vs CVSS](/compare/epss-vs-cvss/)
- [CVSS vs KEV](/compare/cvss-vs-kev/)
- [EPSS vs KEV](/compare/epss-vs-kev/)
- [SSVC vs EPSS](/compare/ssvc-vs-epss/)
- [CVSS v3.1 vs v4.0](/compare/cvss-v3-1-vs-v4-0/)
- [KEV vs vendor intelligence](/compare/kev-vs-vendor-intelligence/)
- [CVSS vs EPSS vs KEV](/compare/cvss-vs-epss-vs-kev/)

## Sources

- CERT/CC, SSVC documentation: https://certcc.github.io/SSVC/ (read 10 Nov 2026)
- CERT/CC, SSVC overview: https://certcc.github.io/SSVC/tutorials/ssvc_overview/ (read 10 Nov 2026)
- CERT/CC, CISA BOD 26-04 Response Model: https://certcc.github.io/SSVC/howto/cisa_response/ (read 10 Nov 2026)
- CISA, Vulnrichment README: https://github.com/cisagov/vulnrichment (read 10 Nov 2026)
- CISA, BOD 26-04, archived copy: https://web.archive.org/web/20261110120100/https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (read 10 Nov 2026)
- FIRST, CVSS v3.1 specification: https://www.first.org/cvss/v3.1/specification-document (read 10 Nov 2026)
- NVD news (2026-06-17 SSVC deployment): https://nvd.nist.gov/general/news (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://epssvscvss.com/compare/ssvc-vs-cvss/
