<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Provider Urgency | FirewallSync</title><link>https://firewallsync.com/tags/provider-urgency/</link><description>Practical cybersecurity writing for engineering teams that ship fast.</description><language>en-us</language><image><url>https://firewallsync.com/icon-512.png</url><title>FirewallSync</title><link>https://firewallsync.com/</link></image><lastBuildDate>Sat, 14 Nov 2026 04:40:00 +0000</lastBuildDate><atom:link href="https://firewallsync.com/tags/provider-urgency/index.xml" rel="self" type="application/rss+xml"/><item><title>CVSS v4 Supplemental Metrics in CVE Records: Who Sets Them</title><link>https://firewallsync.com/posts/cvss-v4-supplemental-metrics-in-cve-records-automatable-provider-urgency/</link><guid>https://firewallsync.com/posts/cvss-v4-supplemental-metrics-in-cve-records-automatable-provider-urgency/</guid><pubDate>Sat, 14 Nov 2026 04:40:00 +0000</pubDate><dc:creator>John Marshall</dc:creator><category>Security Operations</category><description>CVSS v4.0 Supplemental metrics (Safety, Automatable, Recovery, Value Density, Response Effort, Provider Urgency) never change the score. A count across every published CVE record shows only 3.4% of CNA v4.0 entries set any of them, which CNAs do, how the JSON fields and vector string drift apart, and how to use them without overtrusting them.</description><enclosure url="https://firewallsync.com/posts/cvss-v4-supplemental-metrics-in-cve-records-automatable-provider-urgency/cover_hu4154979156842941863.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/cvss-v4-supplemental-metrics-in-cve-records-automatable-provider-urgency/cover_hu4154979156842941863.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/cvss-v4-supplemental-metrics-in-cve-records-automatable-provider-urgency/cover_hu4154979156842941863.jpg" alt="A lit red no-entry signal with a white horizontal bar, glowing against a dark background at night" width="1200" height="630"></p><p><strong>Short answer:</strong> CVSS v4.0 added six optional <em>Supplemental</em> metrics that describe a vulnerability without changing its score. They are real fields in the CVE JSON 5 schema, but almost nobody fills them in. Across every published CVE record in the cvelistV5 snapshot of November 14, 2026, only <strong>3.4%</strong> of records with a CNA <code>cvssV4_0</code> entry set any Supplemental metric, and two vendors, Juniper and Palo Alto Networks, produce nearly a third of them (516 of 1,661 entries). If you parse them, parse both the JSON fields and the vector string, and treat them as the supplier&rsquo;s opinion at publication time.</p>
<p>This article covers the field names and values, who actually sets them, two parsing traps, and where they fit in a patch decision. For the overall flow from CVE record to ticket, see the <a href="/posts/vulnerability-prioritization-workflow-cve-record-to-patch-ticket/">vulnerability prioritization workflow</a>. For reading the rest of a v4.0 vector, see <a href="/posts/how-to-read-a-cvss-v4-0-vector-string-metric-by-metric-with-real-cve-records/">how to read a CVSS v4.0 vector string</a>.</p>
<h2 id="the-six-supplemental-metrics">The six Supplemental metrics</h2>
<p>The <a href="https://www.first.org/cvss/v4.0/specification-document">CVSS v4.0 specification</a> introduces &ldquo;a new, optional metric group called the Supplemental metric group&rdquo; and states: &ldquo;No metric will have any impact on the final calculated CVSS score (e.g. CVSS-BTE).&rdquo; The values &ldquo;convey additional extrinsic characteristics of the vulnerability itself.&rdquo;</p>
<table>
  <thead>
      <tr>
          <th>Metric</th>
          <th>Vector</th>
          <th>Allowed values</th>
          <th>CVE JSON property</th>
          <th>JSON enum</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Safety</td>
          <td><code>S</code></td>
          <td>X, N, P</td>
          <td><code>Safety</code></td>
          <td>NEGLIGIBLE, PRESENT</td>
      </tr>
      <tr>
          <td>Automatable</td>
          <td><code>AU</code></td>
          <td>X, N, Y</td>
          <td><code>Automatable</code></td>
          <td>NO, YES</td>
      </tr>
      <tr>
          <td>Recovery</td>
          <td><code>R</code></td>
          <td>X, A, U, I</td>
          <td><code>Recovery</code></td>
          <td>AUTOMATIC, USER, IRRECOVERABLE</td>
      </tr>
      <tr>
          <td>Value Density</td>
          <td><code>V</code></td>
          <td>X, D, C</td>
          <td><code>valueDensity</code></td>
          <td>DIFFUSE, CONCENTRATED</td>
      </tr>
      <tr>
          <td>Vulnerability Response Effort</td>
          <td><code>RE</code></td>
          <td>X, L, M, H</td>
          <td><code>vulnerabilityResponseEffort</code></td>
          <td>LOW, MODERATE, HIGH</td>
      </tr>
      <tr>
          <td>Provider Urgency</td>
          <td><code>U</code></td>
          <td>X, Clear, Green, Amber, Red</td>
          <td><code>providerUrgency</code></td>
          <td>CLEAR, GREEN, AMBER, RED</td>
      </tr>
  </tbody>
</table>
<p>Every JSON enum also allows <code>NOT_DEFINED</code>, which is the schema default (<a href="https://github.com/CVEProject/cve-schema/blob/main/schema/imports/cvss/cvss-v4.0.json">cve-schema <code>cvss-v4.0.json</code></a>). In the vector, <code>X</code> means Not Defined, and the spec tells consumers to &ldquo;treat unspecified Threat, Environmental and Supplemental as Not Defined.&rdquo;</p>
<p>What each one means, in the spec&rsquo;s words:</p>
<ul>
<li><strong>Safety:</strong> whether consequences meet the IEC 61508 consequence categories. <code>P</code> (Present) versus <code>N</code> (Negligible).</li>
<li><strong>Automatable:</strong> &ldquo;Can an attacker automate exploitation events for this vulnerability across multiple targets?&rdquo; <code>Y</code> means &ldquo;Attackers can reliably automate all 4 steps of the kill chain.&rdquo;</li>
<li><strong>Recovery:</strong> whether the system recovers services automatically (<code>A</code>), needs user intervention (<code>U</code>), or is irrecoverable by the user (<code>I</code>) after an attack.</li>
<li><strong>Value Density:</strong> what one exploitation event gains the attacker. <code>D</code> (Diffuse): &ldquo;The vulnerable system has limited resources.&rdquo; <code>C</code> (Concentrated): &ldquo;The vulnerable system is rich in resources.&rdquo;</li>
<li><strong>Vulnerability Response Effort:</strong> how hard it is for the consumer to respond, from <code>L</code> (&ldquo;low/trivial&rdquo;) to <code>H</code> (&ldquo;significant and/or difficult&rdquo;).</li>
<li><strong>Provider Urgency:</strong> an optional &ldquo;pass-through&rdquo; metric for the provider&rsquo;s own assessment, from Clear (&ldquo;no urgency (Informational)&rdquo;) to Red (&ldquo;the highest urgency&rdquo;).</li>
</ul>
<p>Two schema details trip up parsers:</p>
<ol>
<li><strong>Property-name casing is inconsistent.</strong> <code>Safety</code>, <code>Automatable</code> and <code>Recovery</code> start with a capital letter; the other three are camelCase. A loop that lower-cases the first letter of every metric name will miss three of them.</li>
<li><strong>Provider Urgency uses words in the vector.</strong> The vector segment is <code>U:Amber</code>, not <code>U:A</code>, and the JSON value is <code>AMBER</code>. A regex for single-letter values silently drops it.</li>
</ol>
<h2 id="who-actually-sets-them">Who actually sets them</h2>
<p>We streamed every record in the cvelistV5 midnight release of November 14, 2026 (<code>2026-11-14_all_CVEs_at_midnight.zip.zip</code>), kept records in state <code>PUBLISHED</code>, and counted CNA <code>cvssV4_0</code> entries where either the JSON property is set to something other than <code>NOT_DEFINED</code> or the vector has a non-<code>X</code> segment. Counts below are from that run; the method is described so you can repeat it.</p>
<table>
  <thead>
      <tr>
          <th>Measure</th>
          <th>Count</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Published records with a CNA <code>cvssV4_0</code> entry</td>
          <td>46,973 (47,055 entries)</td>
      </tr>
      <tr>
          <td>Records with at least one Supplemental metric</td>
          <td>1,609 (3.4%)</td>
      </tr>
      <tr>
          <td>CNA entries with at least one Supplemental metric</td>
          <td>1,661</td>
      </tr>
      <tr>
          <td>Entries with all six set</td>
          <td>257</td>
      </tr>
      <tr>
          <td>CNAs publishing v4.0 / of those, using Supplemental at least once</td>
          <td>326 / 149</td>
      </tr>
  </tbody>
</table>
<p>By metric, across the 1,661 entries:</p>
<table>
  <thead>
      <tr>
          <th>Metric</th>
          <th>Entries set</th>
          <th>Value split</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Automatable</td>
          <td>1,210</td>
          <td>YES 732, NO 478</td>
      </tr>
      <tr>
          <td>Provider Urgency</td>
          <td>1,152</td>
          <td>AMBER 617, GREEN 212, RED 208, CLEAR 115</td>
      </tr>
      <tr>
          <td>Response Effort</td>
          <td>1,123</td>
          <td>MODERATE 726, LOW 330, HIGH 67</td>
      </tr>
      <tr>
          <td>Recovery</td>
          <td>1,067</td>
          <td>USER 679, AUTOMATIC 345, IRRECOVERABLE 43</td>
      </tr>
      <tr>
          <td>Value Density</td>
          <td>891</td>
          <td>DIFFUSE 448, CONCENTRATED 443</td>
      </tr>
      <tr>
          <td>Safety</td>
          <td>475</td>
          <td>NEGLIGIBLE 314, PRESENT 161</td>
      </tr>
  </tbody>
</table>
<p>Who sets them matters more than the totals:</p>
<table>
  <thead>
      <tr>
          <th>CNA</th>
          <th>CNA v4.0 entries</th>
          <th>With Supplemental</th>
          <th>Typical pattern</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>VulDB</td>
          <td>14,115</td>
          <td>0</td>
          <td>none</td>
      </tr>
      <tr>
          <td>VulnCheck</td>
          <td>11,610</td>
          <td>2</td>
          <td>none</td>
      </tr>
      <tr>
          <td>GitHub (GitHub_M)</td>
          <td>5,841</td>
          <td>31</td>
          <td>occasional</td>
      </tr>
      <tr>
          <td>icscert (CISA ICS)</td>
          <td>947</td>
          <td>0</td>
          <td>none</td>
      </tr>
      <tr>
          <td>Juniper</td>
          <td>426</td>
          <td>258</td>
          <td>AU, R, RE, often V</td>
      </tr>
      <tr>
          <td>Palo Alto Networks</td>
          <td>263</td>
          <td>258</td>
          <td>AU, R, V, RE, U</td>
      </tr>
  </tbody>
</table>
<p>Other frequent users in the snapshot include bcorg (mostly <code>U</code> only), Apache, OpenText, GovTech CSG and Google Cloud (mostly <code>U</code> only). By CVE ID year, 880 of the 1,661 entries are 2026 IDs, 456 are 2025 and 301 are 2024.</p>
<p>The practical reading: a missing <code>AU</code> or <code>U</code> is a statement about which CNA wrote the record, not about the vulnerability. The two largest producers of v4.0 scores leave every Supplemental metric undefined.</p>
<p>Only five ADP <code>cvssV4_0</code> entries exist in the snapshot (all CISA-ADP), and none set a Supplemental metric. CISA&rsquo;s exploitation and automatability signals arrive through SSVC instead; see <a href="/posts/cisa-vulnrichment-how-to-read-ssvc-values-in-a-cve-record-and-turn-them-into-a-patch-decision/">how to read SSVC values in a CVE record</a>.</p>
<h2 id="trap-the-vector-and-the-json-fields-drift-apart">Trap: the vector and the JSON fields drift apart</h2>
<p>The schema stores each Supplemental value twice: once as a segment in <code>vectorString</code> and once as its own property. In 61 CNA entries they disagree on which metrics are set. GitHub (22), NLnet Labs (14) and Vaadin (7) account for most of them. Two real shapes:</p>
<ul>
<li><code>CVE-2026-110803</code> (Vaadin): JSON sets all six properties (<code>Automatable: YES</code>, <code>providerUrgency: CLEAR</code> and so on) while the vector ends at <code>SA:N</code> with no Supplemental segments.</li>
<li><code>CVE-2026-41292</code> (NLnet Labs): the vector ends <code>E:U/U:Red</code>, but no <code>providerUrgency</code> property exists.</li>
</ul>
<p>We found no entry where both sides were set to different defined values; the drift is always one side missing. Tools that read only <code>vectorString</code> or only the JSON properties will each miss part of the data.</p>
<h2 id="a-parser-that-reads-both-and-flags-drift">A parser that reads both and flags drift</h2>
<p>This Python 3 function (run with Python 3.13 against the three records named in this article, downloaded from <code>raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/...</code>) returns defined Supplemental values from a <code>cvssV4_0</code> object, preferring the vector and falling back to JSON, and reports mismatches:</p>
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-python" data-lang="python"><span style="display:flex;"><span><span style="color:#f92672">import</span> json<span style="color:#f92672">,</span> sys
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span><span style="color:#75715e"># vector abbreviation -&gt; (JSON property in cvss-v4.0.json, vector value -&gt; JSON enum)</span>
</span></span><span style="display:flex;"><span>SUPPLEMENTAL <span style="color:#f92672">=</span> {
</span></span><span style="display:flex;"><span>    <span style="color:#e6db74">&#34;S&#34;</span>:  (<span style="color:#e6db74">&#34;Safety&#34;</span>, {<span style="color:#e6db74">&#34;N&#34;</span>: <span style="color:#e6db74">&#34;NEGLIGIBLE&#34;</span>, <span style="color:#e6db74">&#34;P&#34;</span>: <span style="color:#e6db74">&#34;PRESENT&#34;</span>}),
</span></span><span style="display:flex;"><span>    <span style="color:#e6db74">&#34;AU&#34;</span>: (<span style="color:#e6db74">&#34;Automatable&#34;</span>, {<span style="color:#e6db74">&#34;N&#34;</span>: <span style="color:#e6db74">&#34;NO&#34;</span>, <span style="color:#e6db74">&#34;Y&#34;</span>: <span style="color:#e6db74">&#34;YES&#34;</span>}),
</span></span><span style="display:flex;"><span>    <span style="color:#e6db74">&#34;R&#34;</span>:  (<span style="color:#e6db74">&#34;Recovery&#34;</span>, {<span style="color:#e6db74">&#34;A&#34;</span>: <span style="color:#e6db74">&#34;AUTOMATIC&#34;</span>, <span style="color:#e6db74">&#34;U&#34;</span>: <span style="color:#e6db74">&#34;USER&#34;</span>, <span style="color:#e6db74">&#34;I&#34;</span>: <span style="color:#e6db74">&#34;IRRECOVERABLE&#34;</span>}),
</span></span><span style="display:flex;"><span>    <span style="color:#e6db74">&#34;V&#34;</span>:  (<span style="color:#e6db74">&#34;valueDensity&#34;</span>, {<span style="color:#e6db74">&#34;D&#34;</span>: <span style="color:#e6db74">&#34;DIFFUSE&#34;</span>, <span style="color:#e6db74">&#34;C&#34;</span>: <span style="color:#e6db74">&#34;CONCENTRATED&#34;</span>}),
</span></span><span style="display:flex;"><span>    <span style="color:#e6db74">&#34;RE&#34;</span>: (<span style="color:#e6db74">&#34;vulnerabilityResponseEffort&#34;</span>, {<span style="color:#e6db74">&#34;L&#34;</span>: <span style="color:#e6db74">&#34;LOW&#34;</span>, <span style="color:#e6db74">&#34;M&#34;</span>: <span style="color:#e6db74">&#34;MODERATE&#34;</span>, <span style="color:#e6db74">&#34;H&#34;</span>: <span style="color:#e6db74">&#34;HIGH&#34;</span>}),
</span></span><span style="display:flex;"><span>    <span style="color:#e6db74">&#34;U&#34;</span>:  (<span style="color:#e6db74">&#34;providerUrgency&#34;</span>, {<span style="color:#e6db74">&#34;Clear&#34;</span>: <span style="color:#e6db74">&#34;CLEAR&#34;</span>, <span style="color:#e6db74">&#34;Green&#34;</span>: <span style="color:#e6db74">&#34;GREEN&#34;</span>, <span style="color:#e6db74">&#34;Amber&#34;</span>: <span style="color:#e6db74">&#34;AMBER&#34;</span>, <span style="color:#e6db74">&#34;Red&#34;</span>: <span style="color:#e6db74">&#34;RED&#34;</span>}),
</span></span><span style="display:flex;"><span>}
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span><span style="color:#66d9ef">def</span> <span style="color:#a6e22e">supplemental</span>(cvss4):
</span></span><span style="display:flex;"><span>    <span style="color:#e6db74">&#34;&#34;&#34;Return {json_field: value} for defined Supplemental metrics, plus conflicts.&#34;&#34;&#34;</span>
</span></span><span style="display:flex;"><span>    segs <span style="color:#f92672">=</span> dict(p<span style="color:#f92672">.</span>split(<span style="color:#e6db74">&#34;:&#34;</span>, <span style="color:#ae81ff">1</span>) <span style="color:#66d9ef">for</span> p <span style="color:#f92672">in</span> cvss4<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;vectorString&#34;</span>, <span style="color:#e6db74">&#34;&#34;</span>)<span style="color:#f92672">.</span>split(<span style="color:#e6db74">&#34;/&#34;</span>)[<span style="color:#ae81ff">1</span>:] <span style="color:#66d9ef">if</span> <span style="color:#e6db74">&#34;:&#34;</span> <span style="color:#f92672">in</span> p)
</span></span><span style="display:flex;"><span>    out, conflicts <span style="color:#f92672">=</span> {}, []
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">for</span> abbr, (field, mapping) <span style="color:#f92672">in</span> SUPPLEMENTAL<span style="color:#f92672">.</span>items():
</span></span><span style="display:flex;"><span>        from_vec <span style="color:#f92672">=</span> mapping<span style="color:#f92672">.</span>get(segs<span style="color:#f92672">.</span>get(abbr))            <span style="color:#75715e"># None if absent or X</span>
</span></span><span style="display:flex;"><span>        from_json <span style="color:#f92672">=</span> cvss4<span style="color:#f92672">.</span>get(field)
</span></span><span style="display:flex;"><span>        from_json <span style="color:#f92672">=</span> <span style="color:#66d9ef">None</span> <span style="color:#66d9ef">if</span> from_json <span style="color:#f92672">in</span> (<span style="color:#66d9ef">None</span>, <span style="color:#e6db74">&#34;NOT_DEFINED&#34;</span>) <span style="color:#66d9ef">else</span> from_json
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">if</span> from_vec <span style="color:#f92672">!=</span> from_json:          <span style="color:#75715e"># differs, or one side missing</span>
</span></span><span style="display:flex;"><span>            conflicts<span style="color:#f92672">.</span>append((field, from_vec, from_json))
</span></span><span style="display:flex;"><span>        value <span style="color:#f92672">=</span> from_vec <span style="color:#f92672">or</span> from_json
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">if</span> value:
</span></span><span style="display:flex;"><span>            out[field] <span style="color:#f92672">=</span> value
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">return</span> out, conflicts
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span><span style="color:#66d9ef">if</span> __name__ <span style="color:#f92672">==</span> <span style="color:#e6db74">&#34;__main__&#34;</span>:
</span></span><span style="display:flex;"><span>    record <span style="color:#f92672">=</span> json<span style="color:#f92672">.</span>load(open(sys<span style="color:#f92672">.</span>argv[<span style="color:#ae81ff">1</span>]))
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">for</span> m <span style="color:#f92672">in</span> record[<span style="color:#e6db74">&#34;containers&#34;</span>][<span style="color:#e6db74">&#34;cna&#34;</span>]<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;metrics&#34;</span>, []):
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">if</span> <span style="color:#e6db74">&#34;cvssV4_0&#34;</span> <span style="color:#f92672">in</span> m:
</span></span><span style="display:flex;"><span>            vals, conflicts <span style="color:#f92672">=</span> supplemental(m[<span style="color:#e6db74">&#34;cvssV4_0&#34;</span>])
</span></span><span style="display:flex;"><span>            print(record[<span style="color:#e6db74">&#34;cveMetadata&#34;</span>][<span style="color:#e6db74">&#34;cveId&#34;</span>], vals)
</span></span><span style="display:flex;"><span>            <span style="color:#66d9ef">for</span> c <span style="color:#f92672">in</span> conflicts:
</span></span><span style="display:flex;"><span>                print(<span style="color:#e6db74">&#34;  vector/JSON mismatch:&#34;</span>, c)
</span></span></code></pre></div><p>Output for <code>CVE-2024-0012</code> (two v4.0 entries, one per scenario) and <code>CVE-2026-41292</code>:</p>
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-text" data-lang="text"><span style="display:flex;"><span>CVE-2024-0012 {&#39;Automatable&#39;: &#39;NO&#39;, &#39;Recovery&#39;: &#39;USER&#39;, &#39;valueDensity&#39;: &#39;CONCENTRATED&#39;, &#39;vulnerabilityResponseEffort&#39;: &#39;HIGH&#39;, &#39;providerUrgency&#39;: &#39;RED&#39;}
</span></span><span style="display:flex;"><span>CVE-2024-0012 {&#39;Automatable&#39;: &#39;NO&#39;, &#39;Recovery&#39;: &#39;USER&#39;, &#39;valueDensity&#39;: &#39;CONCENTRATED&#39;, &#39;vulnerabilityResponseEffort&#39;: &#39;HIGH&#39;, &#39;providerUrgency&#39;: &#39;RED&#39;}
</span></span><span style="display:flex;"><span>CVE-2026-41292 {&#39;providerUrgency&#39;: &#39;RED&#39;}
</span></span><span style="display:flex;"><span>  vector/JSON mismatch: (&#39;providerUrgency&#39;, &#39;RED&#39;, None)
</span></span></code></pre></div><p>This is illustrative ingestion code: it reads the CNA container only and does not validate the rest of the vector. Store the CNA short name next to each value so a dashboard can show who said it.</p>
<h2 id="automatable-cvss-au-versus-ssvc-automatable">Automatable: CVSS AU versus SSVC Automatable</h2>
<p>CVSS <code>AU</code> and SSVC Automatable are close cousins. CERT/CC&rsquo;s SSVC decision point asks &ldquo;Can an attacker reliably automate creating exploitation events for this vulnerability?&rdquo; and defines yes as &ldquo;Attackers can reliably automate steps 1-4 of the kill chain&rdquo; (<a href="https://github.com/CERTCC/SSVC/blob/main/src/ssvc/decision_points/ssvc/automatable.py">CERTCC/SSVC <code>automatable.py</code></a>). The CVSS definition likewise refers to &ldquo;all 4 steps of the kill chain.&rdquo;</p>
<p>They can still disagree within a single record. In <code>CVE-2024-0012</code>, the PAN-OS management web interface authentication bypass, Palo Alto Networks&rsquo; CVSS vector says <code>AU:N</code>. The CISA-ADP SSVC entry in the same record, timestamped 2024-11-18, says <code>Exploitation: active</code>, <code>Automatable: yes</code>, <code>Technical Impact: total</code>. CISA added the CVE to KEV on 2024-11-18.</p>
<p>The record does not explain the difference, so we will not guess at it. The lesson for tooling is narrower: the CNA&rsquo;s <code>AU</code> is the CNA&rsquo;s assessment, and nothing in the schema ties it to exploitation evidence elsewhere in the record. Of the 117 KEV CVEs with a CNA v4.0 entry in this snapshot, 24 carry any Supplemental metric. KEV status comes from the <a href="/posts/cisa-kev-json-feed-what-each-field-means-and-how-to-match-it-against-a-scanner-export/">KEV catalog</a>, not from CVSS.</p>
<h2 id="how-to-use-them-in-a-patch-decision">How to use them in a patch decision</h2>
<ul>
<li><strong>Display, do not score.</strong> Show <code>AU</code>, <code>R</code>, <code>RE</code> and <code>U</code> on the ticket as supplier context. The spec is explicit that they do not change the CVSS number, so do not fold them into one.</li>
<li><strong>Prefer SSVC and KEV for exploitation-driven urgency.</strong> Where CISA-ADP has SSVC values, they reflect exploitation status; CVSS Supplemental values do not. See <a href="/posts/cvss-vs-epss-vs-kev-which-signal-should-decide-what-you-patch-first/">CVSS vs EPSS vs KEV</a> for how the signals divide the work.</li>
<li><strong>Use Response Effort for scheduling, not priority.</strong> <code>RE:H</code> (as in CVE-2024-0012) is a planning hint: the fix needs real work, so book the window early.</li>
<li><strong>Treat Safety: Present as a routing flag.</strong> 161 entries set <code>S:P</code>. If you run OT, medical or vehicle systems, route those to the owners who understand IEC 61508 consequences.</li>
<li><strong>Never require a value.</strong> A rule like &ldquo;page on <code>U:Red</code>&rdquo; fires for 208 entries in the entire CVE corpus and stays silent for every VulDB, VulnCheck and CISA ICS v4.0 score.</li>
</ul>
<h2 id="common-mistakes">Common mistakes</h2>
<ol>
<li>Reading only <code>vectorString</code> or only the JSON properties. Read both; 61 CNA entries differ.</li>
<li>Assuming camelCase for all six JSON names. Three are capitalised.</li>
<li>Parsing <code>U</code> as a single letter. Its values are <code>Clear</code>, <code>Green</code>, <code>Amber</code>, <code>Red</code>.</li>
<li>Treating an absent <code>AU</code> as &ldquo;not automatable&rdquo;. It almost always means &ldquo;not evaluated&rdquo;.</li>
<li>Adding Supplemental metrics into a custom score and labelling it CVSS. The spec says they do not affect the score; a blended number is your own model, so name it as such.</li>
</ol>
<h2 id="limits-of-this-article">Limits of this article</h2>
<p>Counts come from one cvelistV5 snapshot (midnight UTC, November 14, 2026) and cover CNA containers in published records of every CVE year; they will change as CNAs publish and update records. We did not check whether CNAs revise Supplemental values over time, and we have not assessed whether any CNA&rsquo;s values are accurate. The per-CNA table names the short names used in <code>cveMetadata.assignerShortName</code>.</p>
<h2 id="sources-and-verification">Sources and verification</h2>
<table>
  <thead>
      <tr>
          <th>Important claim</th>
          <th>Source</th>
          <th>Status</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Six Supplemental metrics, allowed vector values, &ldquo;No metric will have any impact on the final calculated CVSS score&rdquo;</td>
          <td><a href="https://www.first.org/cvss/v4.0/specification-document">FIRST CVSS v4.0 Specification Document</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>JSON property names, enums, NOT_DEFINED default</td>
          <td><a href="https://github.com/CVEProject/cve-schema/blob/main/schema/imports/cvss/cvss-v4.0.json">cve-schema cvss-v4.0.json</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>Corpus counts (3.4%, per-metric and per-CNA figures, 61 mismatches, 257 with all six)</td>
          <td><a href="https://github.com/CVEProject/cvelistV5/releases">cvelistV5 release <code>cve_2026-11-14_0000Z</code></a>, our count</td>
          <td>Verified (computed)</td>
      </tr>
      <tr>
          <td>CVE-2024-0012 AU:N, U:Red, RE:H; CISA-ADP SSVC Automatable: yes</td>
          <td><a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2024/0xxx/CVE-2024-0012.json">CVE-2024-0012 record in cvelistV5</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>CVE-2024-0012 added to KEV 2024-11-18; KEV CVE counts</td>
          <td><a href="https://github.com/cisagov/kev-data">cisagov/kev-data</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>SSVC Automatable definition</td>
          <td><a href="https://github.com/CERTCC/SSVC/blob/main/src/ssvc/decision_points/ssvc/automatable.py">CERTCC/SSVC automatable.py</a></td>
          <td>Verified</td>
      </tr>
  </tbody>
</table>
]]></content:encoded></item></channel></rss>