# Severity scores: what they prove and what they miss

Method, read 19 Nov 2026

**The short answer.** A CVSS base score is a number from 0 to 10 that FIRST's open framework assigns to a flaw's intrinsic characteristics and bands from Low to Critical. Of the 37 ledger CVEs read on 19 Nov 2026, 16 have a base score of 9.0 or higher, and the lowest, 2.7, is on the CISA exploited list.

FIRST's CVSS v4.0 specification calls CVSS "an open framework for communicating the characteristics and severity of software vulnerabilities." Its Base group "represents the intrinsic qualities of a vulnerability that are constant over time and across user environments." The user guide is blunt about the limit: Base scores "are designed to measure the severity of a vulnerability and should not be used alone to assess risk." The specification's Table 22 maps a CVSS score to a rating: None 0.0, Low 0.1 to 3.9, Medium 4.0 to 6.9, High 7.0 to 8.9, Critical 9.0 to 10.0.

In practice the number arrives with the [advisory](/guides/reading-a-vendor-advisory/). The CNA, the vendor or NVD publishes a vector string, for example CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, which gives a base score of 9.8 for [CVE-2026-82329](/ledger/cve-2026-82329/). A scanner shows the CVSS score, and the team turns the rating into a deadline. The specification says Base values "are combined with default values that assume the highest severity for Threat and Environmental metrics," and the user guide adds that "the application of Environmental and Threat metrics is the responsibility of the CVSS consumer." A CVSS score computed from the Base metrics alone is written CVSS-B. The ledger mixes v3.1 and v4.0 vectors, which use different equations, so two base scores from different versions are not on one scale.

CVE-2026-41709 shows the gap. Broadcom rates the VMware ESX insufficient-logging flaw 2.7 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N), a Low rating that reflects an attacker who already holds ESX administrator privileges and can skip some log entries. At 2.7 it has the lowest base score of the 37 ledger CVEs. CISA added it to the KEV catalog on 28 Oct 2026 with a due date of 11 Nov 2026. In the other direction, CVE-2026-94545 carries two CVSS 4.0 scores for one flaw: 9.5 on the Next.js advisory and 5.3 on the Satori advisory (GitHub published the Next.js advisory on 30 Sep 2026 and the Satori advisory on 27 Oct 2026).

A base score gives the wrong answer in three situations: when exploitation is already happening and the flaw has a low CVSS score, as with CVE-2026-41709 above; when the vendor's own context moves the number only slightly, as with CVE-2026-0322, where Palo Alto's base score falls from 8.6 to 8.5 when the management interface is restricted to a jump box; and when two advisories assess the same flaw in different products, as with CVE-2026-94545. Adding Threat metrics, which the specification says rest on threat intelligence the consumer supplies, narrows the first gap but leaves the other two.

## The 37 ledger CVEs by rating

| Rating | Base score | CVEs | Of which in the CISA catalog |
| --- | --- | --- | --- |
| Critical | 9.0 to 10.0 | 16 | 14 |
| High | 7.0 to 8.9 | 19 | 18 |
| Medium | 4.0 to 6.9 | 1 | 0 |
| Low | 0.1 to 3.9 | 1 | 1 |

CVSS base scores as recorded in the ledger on 19 Nov 2026; CVSS 3.1 and CVSS 4.0 scores are counted together.

## A worked rescoring of CVE-2026-0322

The base vector from Palo Alto is CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N, a CVSS base score of 8.6. Palo Alto reports the exploit maturity as attacked, so the Threat metric is E:A. Because an unset Threat metric already assumes E:A, the vector with E:A is still 8.6: the exploitation evidence confirms the base score and does not raise it. Now the Environmental step. The management interface is reachable only from a jump box on the adjacent network, so set Modified Attack Vector to adjacent. The vector becomes ...SA:N/E:A/MAV:A. A CVSS score that combines Base, Threat and Environmental metrics is written CVSS-BTE, and this one is 8.5, which matches Palo Alto's own figure for the jump-box case. If the firewall is a lab device and its owner also sets the security requirements CR, IR and AR to low, the CVSS score falls to 7.0. Had the Threat value been E:P (proof-of-concept only), the CVSS score with the jump box would be 7.1, and with E:U (unreported) 5.9. All four figures were computed with the CVSS 4.0 equations; the Threat value is a judgment about exploitation, which is why the KEV listing matters to it.

## Who applies the metrics and where they are recorded

- Asset owner: proposes the Environmental values (Modified base metrics and the CR, IR and AR requirements) from what the device does and who can reach it.
- Security analyst: sets the Threat value from named evidence, such as a CISA listing or the vendor's exploit maturity, and computes the CVSS score.
- Record: the full vector string, the resulting CVSS score, the date, and the evidence behind each Threat and Environmental value, stored in the ticket beside the vendor's base vector.

## Related pages

- [Static reachability and configuration reads: what they prove and what they miss](/methods/static-reachability/)
- [Runtime reachability and live-state reads: what they prove and what they miss](/methods/runtime-reachability/)
- [EPSS exploit prediction: what it proves and what it misses](/methods/exploit-prediction/)

## Sources

- FIRST CVSS v4.0 specification, version 1.2: https://www.first.org/cvss/v4.0/specification-document (read 19 Nov 2026)
- FIRST CVSS v4.0 user guide: Base score measures severity, not risk: https://www.first.org/cvss/v4.0/user-guide (read 19 Nov 2026)
- CISA KEV JSON feed, version 2026.11.18: https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 19 Nov 2026)
- Broadcom advisory for CVE-2026-41709: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017 (read 19 Nov 2026)
- Next.js advisory for CVE-2026-94545 (CVSS 4.0 9.5): https://github.com/vercel/next.js/security/advisories/GHSA-vcvr-r3jv-pc5j (read 19 Nov 2026)
- Satori advisory for CVE-2026-94545 (CVSS 4.0 5.3): https://github.com/vercel/satori/security/advisories/GHSA-wx4j-mvgx-mqwp (read 19 Nov 2026)
- Palo Alto Networks advisory for CVE-2026-0322: https://security.paloaltonetworks.com/CVE-2026-0322 (read 19 Nov 2026)
- NVD record for CVE-2026-41709: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-41709 (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://reachabilityanalysis.com/methods/severity-score/
