<?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>Data Quality | FirewallSync</title><link>https://firewallsync.com/tags/data-quality/</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>Tue, 17 Nov 2026 04:55:00 +0000</lastBuildDate><atom:link href="https://firewallsync.com/tags/data-quality/index.xml" rel="self" type="application/rss+xml"/><item><title>KEV in CVE Records: Audit of All 1,781 CISA-ADP kev Blocks</title><link>https://firewallsync.com/posts/kev-in-cve-records-cisa-adp-kev-block-full-catalog-audit/</link><guid>https://firewallsync.com/posts/kev-in-cve-records-cisa-adp-kev-block-full-catalog-audit/</guid><pubDate>Tue, 17 Nov 2026 04:55:00 +0000</pubDate><dc:creator>Craig Leslie</dc:creator><category>Security Operations</category><description>We compared every entry in CISA's KEV catalog (version 2026.11.13, 1,781 CVEs) with the CISA-ADP kev block in each CVE record, and scanned all 426,227 records in the November 17, 2026 cvelistV5 snapshot for kev blocks that point at CVEs no longer in the catalog. The record copy matches the catalog for 1,777 CVEs; this article lists the four that don't, what happens to a record when CISA removes a CVE from KEV, and a script to run the check yourself.</description><enclosure url="https://firewallsync.com/posts/kev-in-cve-records-cisa-adp-kev-block-full-catalog-audit/cover_hu446428385090800819.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/kev-in-cve-records-cisa-adp-kev-block-full-catalog-audit/cover_hu446428385090800819.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/kev-in-cve-records-cisa-adp-kev-block-full-catalog-audit/cover_hu446428385090800819.jpg" alt="A wall of old wooden card-catalog drawers with brass label holders and handwritten labels, receding into the dark" width="1200" height="630"></p><p>If your vulnerability pipeline reads CVE JSON 5 records instead of the KEV catalog, you are trusting a copy. CISA&rsquo;s Vulnrichment program writes a <code>kev</code> block into the CISA-ADP container of each CVE record that is on the <a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog">Known Exploited Vulnerabilities catalog</a>. We checked that copy against the whole catalog on November 17, 2026.</p>
<p><strong>The short answer:</strong> the copy is close to complete. 1,777 of 1,781 KEV CVEs have a kev block whose <code>dateAdded</code> matches the catalog. Two have no block at all, two show a different date, and no record anywhere in the CVE corpus carries a kev block for a CVE that is not on the catalog, including the three CVEs CISA has removed since January 2025.</p>
<p>This piece goes beyond our <a href="/posts/cve-exploitation-alerts-cisa-adp-kev-ssvc-cvelistv5-diff/">30-day exploitation-alert diff</a>, which measured how quickly new KEV entries reach records. Here the question is whether the record copy can be trusted at full-catalog scale, in both directions.</p>
<h2 id="where-the-kev-block-lives">Where the kev block lives</h2>
<p>The kev block sits in the CISA-ADP container&rsquo;s <code>metrics</code> array, next to the SSVC block that the <a href="/posts/cisa-vulnrichment-how-to-read-ssvc-values-in-a-cve-record-and-turn-them-into-a-patch-decision/">Vulnrichment SSVC guide</a> explains. CISA&rsquo;s <a href="https://github.com/cisagov/vulnrichment">Vulnrichment README</a> states the rule: &ldquo;For those CVEs that are on the KEV, the CISA ADP will add a KEV block &hellip; For those that aren&rsquo;t, no update will occur.&rdquo;</p>
<p>Here is the CISA-ADP <code>metrics</code> content of CVE-2026-82078 (PaperCut NG/MF) as it appeared in cvelistV5 on November 17, 2026, trimmed to the two <code>other</code> entries:</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-json" data-lang="json"><span style="display:flex;"><span>[
</span></span><span style="display:flex;"><span>  {<span style="color:#f92672">&#34;other&#34;</span>: {<span style="color:#f92672">&#34;type&#34;</span>: <span style="color:#e6db74">&#34;ssvc&#34;</span>, <span style="color:#f92672">&#34;content&#34;</span>: {
</span></span><span style="display:flex;"><span>    <span style="color:#f92672">&#34;timestamp&#34;</span>: <span style="color:#e6db74">&#34;2026-08-28T00:00:00+00:00&#34;</span>,
</span></span><span style="display:flex;"><span>    <span style="color:#f92672">&#34;options&#34;</span>: [{<span style="color:#f92672">&#34;Exploitation&#34;</span>: <span style="color:#e6db74">&#34;active&#34;</span>}, {<span style="color:#f92672">&#34;Automatable&#34;</span>: <span style="color:#e6db74">&#34;no&#34;</span>}, {<span style="color:#f92672">&#34;Technical Impact&#34;</span>: <span style="color:#e6db74">&#34;total&#34;</span>}],
</span></span><span style="display:flex;"><span>    <span style="color:#f92672">&#34;role&#34;</span>: <span style="color:#e6db74">&#34;CISA Coordinator&#34;</span>, <span style="color:#f92672">&#34;version&#34;</span>: <span style="color:#e6db74">&#34;2.0.3&#34;</span>, <span style="color:#f92672">&#34;id&#34;</span>: <span style="color:#e6db74">&#34;CVE-2026-82078&#34;</span>}}},
</span></span><span style="display:flex;"><span>  {<span style="color:#f92672">&#34;other&#34;</span>: {<span style="color:#f92672">&#34;type&#34;</span>: <span style="color:#e6db74">&#34;kev&#34;</span>, <span style="color:#f92672">&#34;content&#34;</span>: {
</span></span><span style="display:flex;"><span>    <span style="color:#f92672">&#34;dateAdded&#34;</span>: <span style="color:#e6db74">&#34;2026-08-28&#34;</span>,
</span></span><span style="display:flex;"><span>    <span style="color:#f92672">&#34;reference&#34;</span>: <span style="color:#e6db74">&#34;https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-82078&#34;</span>}}}
</span></span><span style="display:flex;"><span>]
</span></span></code></pre></div><p>The block has two fields: <code>dateAdded</code> and a <code>reference</code> URL. Everything else KEV publishes (<code>dueDate</code>, <code>requiredAction</code>, <code>knownRansomwareCampaignUse</code>, <code>notes</code>, <code>cwes</code>) is only in the catalog. Our <a href="/posts/cisa-kev-json-feed-what-each-field-means-and-how-to-match-it-against-a-scanner-export/">KEV JSON feed field guide</a> covers those fields.</p>
<h2 id="what-we-compared">What we compared</h2>
<table>
  <thead>
      <tr>
          <th>Input</th>
          <th>Version used</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>KEV catalog</td>
          <td><code>known_exploited_vulnerabilities.json</code> from <a href="https://github.com/cisagov/kev-data">cisagov/kev-data</a>, catalogVersion 2026.11.13 (dateReleased 2026-11-13T20:24:18Z), 1,781 entries, dateAdded range 2021-11-03 to 2026-11-13</td>
      </tr>
      <tr>
          <td>CVE records for KEV CVEs</td>
          <td>Each record fetched from the <code>main</code> branch of <a href="https://github.com/CVEProject/cvelistV5">CVEProject/cvelistV5</a> on 2026-11-17 (branch head <code>a683955</code>)</td>
      </tr>
      <tr>
          <td>Full CVE corpus</td>
          <td><code>2026-11-17_all_CVEs_at_midnight.zip.zip</code> from the cvelistV5 release <code>cve_2026-11-17_0000Z</code>: 426,227 records</td>
      </tr>
      <tr>
          <td>Removal history</td>
          <td>Git history of <code>known_exploited_vulnerabilities.json</code> in cisagov/kev-data, 344 commits from 2025-01-27</td>
      </tr>
  </tbody>
</table>
<p>Two checks ran. <strong>Forward:</strong> for every catalog CVE, does the record have a CISA-ADP kev block, and does its <code>dateAdded</code> equal the catalog&rsquo;s? <strong>Reverse:</strong> does any record in the full corpus carry a CISA-ADP kev block for a CVE that is not in the catalog?</p>
<h2 id="results">Results</h2>
<table>
  <thead>
      <tr>
          <th>Check</th>
          <th>Count</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>KEV catalog entries</td>
          <td>1,781</td>
      </tr>
      <tr>
          <td>Records with a CISA-ADP kev block and matching dateAdded</td>
          <td>1,777</td>
      </tr>
      <tr>
          <td>Records with a kev block but a different dateAdded</td>
          <td>2</td>
      </tr>
      <tr>
          <td>Records with a CISA-ADP container but no kev block</td>
          <td>2</td>
      </tr>
      <tr>
          <td>KEV records with no CISA-ADP container</td>
          <td>0</td>
      </tr>
      <tr>
          <td>KEV records not in PUBLISHED state</td>
          <td>0</td>
      </tr>
      <tr>
          <td>Records in the full corpus with a kev block for a non-KEV CVE</td>
          <td>0</td>
      </tr>
  </tbody>
</table>
<p>The 1,781 KEV CVEs span every catalog year: 311 added in 2021, 555 in 2022, 187 in 2023, 186 in 2024, 245 in 2025 and 297 so far in 2026. The kev blocks therefore cover the backfilled early catalog as well as recent additions.</p>
<p>Every one of the 1,781 records also carried a CISA-ADP SSVC block with Exploitation set to <code>active</code>, including the two without a kev block.</p>
<h3 id="two-kev-cves-with-no-kev-block">Two KEV CVEs with no kev block</h3>
<table>
  <thead>
      <tr>
          <th>CVE</th>
          <th>Catalog entry</th>
          <th>KEV dateAdded</th>
          <th>CISA-ADP container dateUpdated</th>
          <th>SSVC Exploitation</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>CVE-2026-48356</td>
          <td>Adobe Commerce and Magento</td>
          <td>2026-10-27</td>
          <td>2026-10-28T03:55:44Z</td>
          <td>active</td>
      </tr>
      <tr>
          <td>CVE-2026-111497</td>
          <td>Google Brotli</td>
          <td>2026-10-27</td>
          <td>2026-10-28T03:55:48Z</td>
          <td>active</td>
      </tr>
  </tbody>
</table>
<p>Both were already missing a kev block in the November 16 snapshot used in our <a href="/posts/cve-exploitation-alerts-cisa-adp-kev-ssvc-cvelistv5-diff/">exploitation-alert diff</a>. Their CISA-ADP containers were updated the day after the KEV addition (the SSVC change arrived) but the kev block did not. We do not know why; CISA has not published an explanation that we could find. A pipeline that treats &ldquo;kev block present&rdquo; as &ldquo;on KEV&rdquo; would have missed both for three weeks.</p>
<h3 id="two-kev-blocks-with-a-different-dateadded">Two kev blocks with a different dateAdded</h3>
<table>
  <thead>
      <tr>
          <th>CVE</th>
          <th>Catalog entry</th>
          <th>Catalog dateAdded</th>
          <th>Record kev dateAdded</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>CVE-2026-81578</td>
          <td>PaperCut NG/MF</td>
          <td>2026-08-31</td>
          <td>2026-08-28</td>
      </tr>
      <tr>
          <td>CVE-2026-82078</td>
          <td>PaperCut NG/MF</td>
          <td>2026-08-31</td>
          <td>2026-08-28</td>
      </tr>
  </tbody>
</table>
<p>The kev-data git history shows both CVEs first appearing in catalog version 2026.08.31, committed 2026-08-31, with dateAdded 2026-08-31, and the date never changing afterwards. The record says three days earlier, matching the timestamp on the record&rsquo;s SSVC block. If you compute time-to-KEV or BOD due dates from the record, these two come out three days early. Use the catalog date; our <a href="/posts/kev-time-to-listing-cve-published-to-dateadded-days-by-vendor/">KEV time-to-listing analysis</a> does.</p>
<h2 id="what-happens-to-the-record-when-a-cve-leaves-kev">What happens to the record when a CVE leaves KEV</h2>
<p>CISA occasionally removes entries. The kev-data history since January 27, 2025 shows three CVEs that were in the catalog and are not in it now, plus one that briefly disappeared and came back:</p>
<table>
  <thead>
      <tr>
          <th>CVE</th>
          <th>Catalog entry</th>
          <th>In catalog</th>
          <th>Removed from catalog</th>
          <th>Record today</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>CVE-2025-4664</td>
          <td>Google Chromium</td>
          <td>from version 2025.05.15</td>
          <td>version 2025.06.09</td>
          <td>no kev block; SSVC Exploitation <code>none</code></td>
      </tr>
      <tr>
          <td>CVE-2025-6264</td>
          <td>Rapid7 Velociraptor</td>
          <td>from version 2025.10.14</td>
          <td>version 2025.10.22</td>
          <td>no kev block; SSVC Exploitation <code>none</code></td>
      </tr>
      <tr>
          <td>CVE-2026-69836</td>
          <td>Microsoft Entra ID</td>
          <td>added 2026-08-21 17:28 UTC commit</td>
          <td>2026-08-21 18:42 UTC commit</td>
          <td>no kev block; SSVC Exploitation <code>none</code></td>
      </tr>
      <tr>
          <td>CVE-2026-1281</td>
          <td>Ivanti EPMM</td>
          <td>added 2026-01-29 18:15 UTC commit</td>
          <td>dropped 19:14 UTC, back 20:41 UTC the same day</td>
          <td>kev block, dateAdded 2026-01-29</td>
      </tr>
  </tbody>
</table>
<p>These are what the data shows; the commits do not record why an entry was removed, and we did not find a CISA statement for each. The record behaviour is consistent, though: when an entry left the catalog, the record lost its kev block and its SSVC Exploitation value was set to <code>none</code>. A pipeline that only ever adds &ldquo;exploited&rdquo; flags and never clears them will keep all three marked as exploited.</p>
<p>The reverse scan backs this up at corpus scale: none of the 426,227 records in the November 17 snapshot carries a CISA-ADP kev block for a CVE outside the catalog.</p>
<h2 id="run-the-audit-yourself">Run the audit yourself</h2>
<p>Tested with Python 3 on November 17, 2026. Fetch the catalog and the records, then run the script.</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-bash" data-lang="bash"><span style="display:flex;"><span>curl -sSO https://raw.githubusercontent.com/cisagov/kev-data/main/known_exploited_vulnerabilities.json
</span></span><span style="display:flex;"><span>mkdir -p records
</span></span><span style="display:flex;"><span>python3 - <span style="color:#e6db74">&lt;&lt;&#39;EOF&#39; &gt; curl.cfg
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">import json
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">for v in json.load(open(&#34;known_exploited_vulnerabilities.json&#34;))[&#34;vulnerabilities&#34;]:
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">    cve = v[&#34;cveID&#34;]; year, num = cve.split(&#34;-&#34;)[1:]
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">    path = f&#34;cves/{year}/{int(num)//1000}xxx/{cve}.json&#34;
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">    print(f&#39;url=&#34;https://raw.githubusercontent.com/CVEProject/cvelistV5/main/{path}&#34;&#39;)
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">    print(f&#39;output=&#34;records/{cve}.json&#34;&#39;)
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">EOF</span>
</span></span><span style="display:flex;"><span>curl -sS --parallel --parallel-max <span style="color:#ae81ff">16</span> -K curl.cfg
</span></span></code></pre></div><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:#75715e"># audit_kev_blocks.py: compare the KEV catalog with the CISA-ADP &#34;kev&#34; block in each CVE record.</span>
</span></span><span style="display:flex;"><span><span style="color:#75715e"># Usage: python3 audit_kev_blocks.py known_exploited_vulnerabilities.json records/</span>
</span></span><span style="display:flex;"><span><span style="color:#f92672">import</span> json<span style="color:#f92672">,</span> sys<span style="color:#f92672">,</span> pathlib
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span>catalog <span style="color:#f92672">=</span> {v[<span style="color:#e6db74">&#34;cveID&#34;</span>]: v <span style="color:#66d9ef">for</span> v <span style="color:#f92672">in</span> json<span style="color:#f92672">.</span>load(open(sys<span style="color:#f92672">.</span>argv[<span style="color:#ae81ff">1</span>]))[<span style="color:#e6db74">&#34;vulnerabilities&#34;</span>]}
</span></span><span style="display:flex;"><span>records <span style="color:#f92672">=</span> pathlib<span style="color:#f92672">.</span>Path(sys<span style="color:#f92672">.</span>argv[<span style="color:#ae81ff">2</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">cisa_adp_metrics</span>(record):
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">for</span> adp <span style="color:#f92672">in</span> record<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;containers&#34;</span>, {})<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;adp&#34;</span>, []):
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">if</span> adp<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;providerMetadata&#34;</span>, {})<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;shortName&#34;</span>) <span style="color:#f92672">==</span> <span style="color:#e6db74">&#34;CISA-ADP&#34;</span>:
</span></span><span style="display:flex;"><span>            <span style="color:#66d9ef">return</span> {m[<span style="color:#e6db74">&#34;other&#34;</span>][<span style="color:#e6db74">&#34;type&#34;</span>]: m[<span style="color:#e6db74">&#34;other&#34;</span>][<span style="color:#e6db74">&#34;content&#34;</span>]
</span></span><span style="display:flex;"><span>                    <span style="color:#66d9ef">for</span> m <span style="color:#f92672">in</span> adp<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;metrics&#34;</span>, []) <span style="color:#66d9ef">if</span> <span style="color:#e6db74">&#34;other&#34;</span> <span style="color:#f92672">in</span> m}
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">return</span> <span style="color:#66d9ef">None</span>
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span>missing, date_mismatch, ok <span style="color:#f92672">=</span> [], [], <span style="color:#ae81ff">0</span>
</span></span><span style="display:flex;"><span><span style="color:#66d9ef">for</span> cve, entry <span style="color:#f92672">in</span> sorted(catalog<span style="color:#f92672">.</span>items()):
</span></span><span style="display:flex;"><span>    record <span style="color:#f92672">=</span> json<span style="color:#f92672">.</span>loads((records <span style="color:#f92672">/</span> <span style="color:#e6db74">f</span><span style="color:#e6db74">&#34;</span><span style="color:#e6db74">{</span>cve<span style="color:#e6db74">}</span><span style="color:#e6db74">.json&#34;</span>)<span style="color:#f92672">.</span>read_text())
</span></span><span style="display:flex;"><span>    metrics <span style="color:#f92672">=</span> cisa_adp_metrics(record) <span style="color:#f92672">or</span> {}
</span></span><span style="display:flex;"><span>    kev <span style="color:#f92672">=</span> metrics<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;kev&#34;</span>)
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">if</span> kev <span style="color:#f92672">is</span> <span style="color:#66d9ef">None</span>:
</span></span><span style="display:flex;"><span>        missing<span style="color:#f92672">.</span>append((cve, entry[<span style="color:#e6db74">&#34;dateAdded&#34;</span>]))
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">elif</span> kev[<span style="color:#e6db74">&#34;dateAdded&#34;</span>] <span style="color:#f92672">!=</span> entry[<span style="color:#e6db74">&#34;dateAdded&#34;</span>]:
</span></span><span style="display:flex;"><span>        date_mismatch<span style="color:#f92672">.</span>append((cve, entry[<span style="color:#e6db74">&#34;dateAdded&#34;</span>], kev[<span style="color:#e6db74">&#34;dateAdded&#34;</span>]))
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">else</span>:
</span></span><span style="display:flex;"><span>        ok <span style="color:#f92672">+=</span> <span style="color:#ae81ff">1</span>
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span>print(<span style="color:#e6db74">f</span><span style="color:#e6db74">&#34;catalog entries: </span><span style="color:#e6db74">{</span>len(catalog)<span style="color:#e6db74">}</span><span style="color:#e6db74">  matching kev block: </span><span style="color:#e6db74">{</span>ok<span style="color:#e6db74">}</span><span style="color:#e6db74">&#34;</span>)
</span></span><span style="display:flex;"><span>print(<span style="color:#e6db74">&#34;no kev block:&#34;</span>, missing)
</span></span><span style="display:flex;"><span>print(<span style="color:#e6db74">&#34;dateAdded differs (catalog, record):&#34;</span>, date_mismatch)
</span></span></code></pre></div><p>Output on November 17, 2026:</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>catalog entries: 1781  matching kev block: 1777
</span></span><span style="display:flex;"><span>no kev block: [(&#39;CVE-2026-111497&#39;, &#39;2026-10-27&#39;), (&#39;CVE-2026-48356&#39;, &#39;2026-10-27&#39;)]
</span></span><span style="display:flex;"><span>dateAdded differs (catalog, record): [(&#39;CVE-2026-81578&#39;, &#39;2026-08-31&#39;, &#39;2026-08-28&#39;), (&#39;CVE-2026-82078&#39;, &#39;2026-08-31&#39;, &#39;2026-08-28&#39;)]
</span></span></code></pre></div><p>The script assumes every catalog CVE has a published record (true on this date). For the reverse check, stream the midnight release zip with Python&rsquo;s <code>zipfile</code>, skip any record whose bytes do not contain <code>&quot;kev&quot;</code>, and collect CISA-ADP kev blocks whose CVE is not in the catalog; a full pass took about 20 seconds here. To keep the check current without refetching everything, drive it from cvelistV5 <code>delta.json</code> as described in our <a href="/posts/cvelistv5-delta-json-deltalog-incremental-cve-sync/">incremental CVE sync guide</a>.</p>
<h2 id="what-to-do-with-this">What to do with this</h2>
<ol>
<li><strong>Keep the catalog as the source of truth.</strong> It is published first, carries the fields the record lacks, and its <code>dateAdded</code> is the one BOD due dates are computed from.</li>
<li><strong>Use the kev block as a cross-check, not a trigger.</strong> Alert when the two disagree: a catalog CVE with no kev block, a kev block with a different date, or a kev block for a non-catalog CVE.</li>
<li><strong>Handle removals.</strong> If an exploited flag in your system came from KEV or from SSVC <code>active</code>, clear or re-review it when the CVE leaves the catalog or Exploitation goes back to <code>none</code>.</li>
<li><strong>Fall back to SSVC when the kev block is missing.</strong> Both missing-block CVEs had Exploitation <code>active</code>, so a rule of &ldquo;kev block OR SSVC active OR in catalog&rdquo; would not have missed them.</li>
</ol>
<p>These steps slot into the KEV and exploitation stages of our <a href="/posts/vulnerability-prioritization-workflow-cve-record-to-patch-ticket/">vulnerability prioritization workflow</a>.</p>
<h2 id="limits-of-this-article">Limits of this article</h2>
<ul>
<li>One snapshot: the catalog as of version 2026.11.13 and records as of November 17, 2026. The two missing blocks may be added later.</li>
<li>The removal history covers only what the cisagov/kev-data repository records, which starts on 2025-01-27. Earlier removals, if any, are not counted.</li>
<li>We report what the data shows about removals, not why CISA removed each entry.</li>
<li>The forward check fetched records from the moving <code>main</code> branch over about 11 seconds; the reverse check used the fixed midnight release.</li>
</ul>
<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>1,781 catalog entries, version 2026.11.13</td>
          <td><a href="https://github.com/cisagov/kev-data">cisagov/kev-data</a> <code>known_exploited_vulnerabilities.json</code></td>
          <td>Verified (computed)</td>
      </tr>
      <tr>
          <td>1,777 matching, 2 missing, 2 date mismatches</td>
          <td><a href="https://github.com/CVEProject/cvelistV5">CVEProject/cvelistV5</a> records, script above</td>
          <td>Verified (computed)</td>
      </tr>
      <tr>
          <td>0 kev blocks for non-catalog CVEs across 426,227 records</td>
          <td>cvelistV5 release <code>cve_2026-11-17_0000Z</code></td>
          <td>Verified (computed)</td>
      </tr>
      <tr>
          <td>CISA ADP adds a kev block only for KEV CVEs</td>
          <td><a href="https://github.com/cisagov/vulnrichment">cisagov/vulnrichment README</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>Three removals and one remove-and-re-add since 2025-01-27</td>
          <td>cisagov/kev-data git history</td>
          <td>Verified (computed); reasons not stated</td>
      </tr>
      <tr>
          <td>Removed CVEs have no kev block and SSVC Exploitation none</td>
          <td>cvelistV5 records, November 17, 2026</td>
          <td>Verified</td>
      </tr>
  </tbody>
</table>
]]></content:encoded></item></channel></rss>