<?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>Cisa-Adp | FirewallSync</title><link>https://firewallsync.com/tags/cisa-adp/</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>Thu, 19 Nov 2026 04:20:00 +0000</lastBuildDate><atom:link href="https://firewallsync.com/tags/cisa-adp/index.xml" rel="self" type="application/rss+xml"/><item><title>Public PoC CVEs: Pull All 47,926 SSVC poc Records</title><link>https://firewallsync.com/posts/public-poc-cves-cisa-adp-ssvc-exploitation-poc-epss/</link><guid>https://firewallsync.com/posts/public-poc-cves-cisa-adp-ssvc-exploitation-poc-epss/</guid><pubDate>Thu, 19 Nov 2026 04:20:00 +0000</pubDate><dc:creator>Craig Leslie</dc:creator><category>Security Operations</category><description>CISA-ADP marks 47,926 CVE records with SSVC Exploitation poc, meaning a public proof of concept or a well-known exploitation method. We pulled them from the cvelistV5 corpus, joined EPSS and KEV, and show what the label does and does not tell you, with a script that writes the full list to CSV.</description><enclosure url="https://firewallsync.com/posts/public-poc-cves-cisa-adp-ssvc-exploitation-poc-epss/cover_hu9432398450888018006.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/public-poc-cves-cisa-adp-ssvc-exploitation-poc-epss/cover_hu9432398450888018006.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/public-poc-cves-cisa-adp-ssvc-exploitation-poc-epss/cover_hu9432398450888018006.jpg" alt="A brass key hanging on a ring from the keyhole of a white door, above a black iron handle" width="1200" height="630"></p><p><strong>Short answer:</strong> CISA&rsquo;s Vulnrichment program writes an SSVC <code>Exploitation</code> value into the CISA-ADP container of the CVE records it scores. The value <code>poc</code> means a public proof of concept or a well-known exploitation method exists. In the cvelistV5 snapshot of 2026-11-18 00:00 UTC, <strong>47,926</strong> records have it. That makes it the largest machine-readable list of &ldquo;public exploit available&rdquo; CVEs you can download for free, but it is a capability label, not a priority queue: only 2.6% of those CVEs score 0.1 or higher in EPSS.</p>
<p>This article shows how to pull the list, what the counts look like next to KEV and EPSS, and how to cut it down to something a team can act on. For what each SSVC field means and how CISA&rsquo;s decision tree turns them into Track, Track*, Attend or Act, see our <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>. For where this fits in a patch decision from CVE record to ticket, see the <a href="/posts/vulnerability-prioritization-workflow-cve-record-to-patch-ticket/">vulnerability prioritization workflow</a>.</p>
<h2 id="what-poc-means-in-the-specs-words">What poc means, in the spec&rsquo;s words</h2>
<p>The SSVC project at Carnegie Mellon SEI defines the <code>Exploitation</code> decision point in <a href="https://github.com/CERTCC/SSVC/blob/main/src/ssvc/decision_points/ssvc/exploitation.py"><code>exploitation.py</code></a>. It has two versions, and the meaning of the middle value narrowed between them.</p>
<table>
  <thead>
      <tr>
          <th>Version</th>
          <th>Value</th>
          <th>Definition (verbatim)</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>1.0.0</td>
          <td>PoC</td>
          <td>&ldquo;One of the following cases is true: (1) private evidence of exploitation is attested but not shared; (2) widespread hearsay attests to exploitation; (3) typical public PoC in places such as Metasploit or ExploitDB; or (4) the vulnerability has a well-known method of exploitation.&rdquo;</td>
      </tr>
      <tr>
          <td>1.1.0 (latest)</td>
          <td>Public PoC</td>
          <td>&ldquo;One of the following is true: (1) Typical public PoC exists in sources such as Metasploit or websites like ExploitDB; or (2) the vulnerability has a well-known method of exploitation.&rdquo;</td>
      </tr>
      <tr>
          <td>both</td>
          <td>Active</td>
          <td>&ldquo;Shared, observable, reliable evidence that the exploit is being used in the wild by real attackers; there is credible public reporting.&rdquo;</td>
      </tr>
      <tr>
          <td>both</td>
          <td>None</td>
          <td>&ldquo;There is no evidence of active exploitation and no public proof of concept (PoC) of how to exploit the vulnerability.&rdquo;</td>
      </tr>
  </tbody>
</table>
<p>CISA&rsquo;s <a href="https://github.com/cisagov/vulnrichment">Vulnrichment README</a> describes a <code>poc</code> value as &ldquo;indicating there was a public proof-of-concept available at the time of analysis&rdquo;. Two practical points follow:</p>
<ul>
<li><strong>&ldquo;Well-known method of exploitation&rdquo; counts.</strong> A <code>poc</code> label does not guarantee a working exploit sits on GitHub or Exploit-DB. Some records get it because the bug class is trivially exploitable.</li>
<li><strong>&ldquo;At the time of analysis.&rdquo;</strong> The SSVC block carries a <code>timestamp</code>. A <code>none</code> scored a year ago says nothing about the PoC that appeared last week.</li>
</ul>
<p>The CVE record does not say which <code>Exploitation</code> version CISA applied. Every CISA-ADP SSVC block in our snapshot carries <code>&quot;version&quot;: &quot;2.0.3&quot;</code>, which is a version string for the SSVC block, not for the decision point.</p>
<h2 id="where-it-sits-in-the-record">Where it sits in the record</h2>
<p>The value lives in the CISA-ADP container, as one of three single-key objects in <code>options</code>. This is the example from CISA&rsquo;s own README (CVE-2024-25522):</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 style="color:#e6db74">&#34;options&#34;</span><span style="color:#960050;background-color:#1e0010">:</span> [
</span></span><span style="display:flex;"><span>  { <span style="color:#f92672">&#34;Exploitation&#34;</span>: <span style="color:#e6db74">&#34;poc&#34;</span> },
</span></span><span style="display:flex;"><span>  { <span style="color:#f92672">&#34;Automatable&#34;</span>: <span style="color:#e6db74">&#34;yes&#34;</span> },
</span></span><span style="display:flex;"><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></span></code></pre></div><p>The path is <code>containers.adp[]</code> where <code>providerMetadata.shortName</code> is <code>CISA-ADP</code>, then <code>metrics[].other</code> where <code>type</code> is <code>ssvc</code>, then <code>content.options</code>. The <a href="/posts/cve-adp-containers-cisa-adp-cve-program-supplier-sadp/">CVE ADP containers guide</a> covers the container itself.</p>
<h2 id="the-numbers-poc-next-to-kev-and-epss">The numbers: poc next to KEV and EPSS</h2>
<p>We counted every CISA-ADP SSVC block in the cvelistV5 release <code>2026-11-18_all_CVEs_at_midnight.zip.zip</code>, then joined the KEV catalog (version 2026.11.18, 1,786 entries) and the EPSS scores for 2026-11-18 (model <code>v2026.06.15</code>). Every SSVC record had an EPSS score.</p>
<table>
  <thead>
      <tr>
          <th>Exploitation</th>
          <th style="text-align: right">Records</th>
          <th style="text-align: right">Share</th>
          <th style="text-align: right">In KEV</th>
          <th style="text-align: right">Median EPSS</th>
          <th style="text-align: right">EPSS ≥ 0.1</th>
          <th style="text-align: right">EPSS ≥ 0.5</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>none</td>
          <td style="text-align: right">173,136</td>
          <td style="text-align: right">77.7%</td>
          <td style="text-align: right">3</td>
          <td style="text-align: right">0.00361</td>
          <td style="text-align: right">2,026</td>
          <td style="text-align: right">598</td>
      </tr>
      <tr>
          <td>poc</td>
          <td style="text-align: right">47,926</td>
          <td style="text-align: right">21.5%</td>
          <td style="text-align: right">1</td>
          <td style="text-align: right">0.00478</td>
          <td style="text-align: right">1,231</td>
          <td style="text-align: right">308</td>
      </tr>
      <tr>
          <td>active</td>
          <td style="text-align: right">1,787</td>
          <td style="text-align: right">0.8%</td>
          <td style="text-align: right">1,782</td>
          <td style="text-align: right">0.53535</td>
          <td style="text-align: right">1,348</td>
          <td style="text-align: right">916</td>
      </tr>
      <tr>
          <td><strong>Total</strong></td>
          <td style="text-align: right"><strong>222,849</strong></td>
          <td style="text-align: right"></td>
          <td style="text-align: right"><strong>1,786</strong></td>
          <td style="text-align: right"></td>
          <td style="text-align: right"></td>
          <td style="text-align: right"></td>
      </tr>
  </tbody>
</table>
<p>Three things stand out.</p>
<p><strong>1. poc is not a queue for KEV.</strong> You might expect a pool of poc CVEs waiting to be added to KEV. The current data cannot show that, because CISA moves a record to <code>active</code> when it joins the catalog. 1,782 of the 1,786 KEV entries read <code>active</code>. The other four (CVE-2024-10441, CVE-2026-40217, CVE-2026-90817 and CVE-2026-90436) all have a KEV <code>dateAdded</code> of 2026-11-18, the same day as the snapshot, so their CISA-ADP blocks had not caught up yet. The single poc record in KEV is one of them. To measure how many poc CVEs later become KEV entries you need two points in time; our <a href="/posts/cve-exploitation-alerts-cisa-adp-kev-ssvc-cvelistv5-diff/">CVE exploitation alerts</a> post diffs snapshots that way.</p>
<p><strong>2. active and KEV are not identical.</strong> Five records read <code>active</code> but are not in the current KEV catalog: CVE-2023-24932, CVE-2022-21894, CVE-2021-30120, CVE-2021-30119 and CVE-2021-21983. Treat the <a href="/posts/cisa-kev-json-feed-what-each-field-means-and-how-to-match-it-against-a-scanner-export/">KEV JSON feed</a> as the authority for &ldquo;known exploited&rdquo; and the ADP value as a second opinion.</p>
<p><strong>3. Most poc CVEs score low in EPSS.</strong> The poc median (0.00478) is only slightly above the none median (0.00361). EPSS estimates the probability of exploitation activity in the next 30 days, and a published PoC raises that only somewhat on its own. Read our <a href="/posts/epss-data-feed-columns-percentile-vs-probability-and-how-to-join-it-to-a-scanner-export/">EPSS feed guide</a> before comparing these numbers to a percentile threshold.</p>
<p>There is also a coverage gap to keep in mind. Of the 17,558 CVEs with an EPSS score of 0.1 or higher on 2026-11-18, 12,953 have no CISA-ADP SSVC block at all. CISA scores records as they are published and has not scored the back catalog, so an absent <code>poc</code> does not mean &ldquo;no PoC&rdquo;.</p>
<h2 id="slice-poc-by-the-other-two-decision-points">Slice poc by the other two decision points</h2>
<p><code>Exploitation</code> is one of three values CISA writes. Splitting the poc set by the other two gives smaller groups with different EPSS profiles:</p>
<table>
  <thead>
      <tr>
          <th>Automatable</th>
          <th>Technical Impact</th>
          <th style="text-align: right">poc records</th>
          <th style="text-align: right">Median EPSS</th>
          <th style="text-align: right">EPSS ≥ 0.1</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>yes</td>
          <td>total</td>
          <td style="text-align: right">5,328</td>
          <td style="text-align: right">0.00891</td>
          <td style="text-align: right">394</td>
      </tr>
      <tr>
          <td>no</td>
          <td>total</td>
          <td style="text-align: right">9,701</td>
          <td style="text-align: right">0.00628</td>
          <td style="text-align: right">377</td>
      </tr>
      <tr>
          <td>yes</td>
          <td>partial</td>
          <td style="text-align: right">9,887</td>
          <td style="text-align: right">0.00516</td>
          <td style="text-align: right">165</td>
      </tr>
      <tr>
          <td>no</td>
          <td>partial</td>
          <td style="text-align: right">23,010</td>
          <td style="text-align: right">0.00385</td>
          <td style="text-align: right">295</td>
      </tr>
  </tbody>
</table>
<p>The poc / yes / total slice (11.1% of poc records) has about twice the median EPSS of the full poc set. It is also the combination CISA&rsquo;s own decision tree treats most seriously short of active exploitation: our <a href="/posts/cisa-vulnrichment-how-to-read-ssvc-values-in-a-cve-record-and-turn-them-into-a-patch-decision/">Vulnrichment guide</a> shows it at Attend for high mission and well-being impact.</p>
<p>The highest-scoring poc CVEs are not in KEV. CVE-2023-27372 (EPSS 0.99682) and CVE-2025-1974 (0.99400) are both poc / yes / total and absent from catalog version 2026.11.18. In the 2026-11-18 data, 308 poc CVEs score 0.5 or higher. That small set is where poc earns its keep: a public PoC, a high EPSS score and no KEV entry yet.</p>
<h2 id="pull-the-list-yourself">Pull the list yourself</h2>
<p>The script below reads the cvelistV5 daily release zip and an EPSS daily file, and writes every poc CVE to CSV. It uses only the Python standard library.</p>
<p>Inputs:</p>
<ul>
<li><strong>CVE corpus:</strong> the <code>&lt;date&gt;_all_CVEs_at_midnight.zip.zip</code> asset from a <code>cve_&lt;date&gt;_0000Z</code> release of <a href="https://github.com/CVEProject/cvelistV5/releases">CVEProject/cvelistV5</a> (about 660 MB; it holds an inner <code>cves.zip</code>). Some days the asset is missing; take the previous day&rsquo;s.</li>
<li><strong>EPSS:</strong> a daily <code>epss_scores-YYYY-MM-DD.csv.gz</code> from the <a href="https://github.com/empiricalsec/epss_scores">empiricalsec/epss_scores</a> repository. Its first line is a <code>#model_version</code> comment, which the script skips.</li>
</ul>
<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">#!/usr/bin/env python3</span>
</span></span><span style="display:flex;"><span><span style="color:#e6db74">&#34;&#34;&#34;List CVEs that CISA-ADP marks SSVC Exploitation &#39;poc&#39;, joined to EPSS.
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">usage: public_poc.py &lt;cvelistV5 *_all_CVEs_at_midnight.zip.zip&gt; &lt;epss_scores-YYYY-MM-DD.csv.gz&gt; &gt; poc.csv&#34;&#34;&#34;</span>
</span></span><span style="display:flex;"><span><span style="color:#f92672">import</span> csv<span style="color:#f92672">,</span> gzip<span style="color:#f92672">,</span> io<span style="color:#f92672">,</span> json<span style="color:#f92672">,</span> sys<span style="color:#f92672">,</span> zipfile
</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_ssvc</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 style="color:#f92672">or</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">continue</span>
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">for</span> metric <span style="color:#f92672">in</span> adp<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;metrics&#34;</span>, []) <span style="color:#f92672">or</span> []:
</span></span><span style="display:flex;"><span>            other <span style="color:#f92672">=</span> metric<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;other&#34;</span>, {})
</span></span><span style="display:flex;"><span>            <span style="color:#66d9ef">if</span> other<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;type&#34;</span>) <span style="color:#f92672">==</span> <span style="color:#e6db74">&#34;ssvc&#34;</span>:
</span></span><span style="display:flex;"><span>                content <span style="color:#f92672">=</span> other<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;content&#34;</span>, {})
</span></span><span style="display:flex;"><span>                opts <span style="color:#f92672">=</span> {}
</span></span><span style="display:flex;"><span>                <span style="color:#66d9ef">for</span> d <span style="color:#f92672">in</span> content<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;options&#34;</span>, []):
</span></span><span style="display:flex;"><span>                    opts<span style="color:#f92672">.</span>update(d)  <span style="color:#75715e"># options is a list of one-key objects</span>
</span></span><span style="display:flex;"><span>                <span style="color:#66d9ef">return</span> content<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;timestamp&#34;</span>), opts
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">return</span> <span style="color:#66d9ef">None</span>, <span style="color:#66d9ef">None</span>
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span>epss <span style="color:#f92672">=</span> {}
</span></span><span style="display:flex;"><span><span style="color:#66d9ef">with</span> gzip<span style="color:#f92672">.</span>open(sys<span style="color:#f92672">.</span>argv[<span style="color:#ae81ff">2</span>], <span style="color:#e6db74">&#34;rt&#34;</span>) <span style="color:#66d9ef">as</span> f:
</span></span><span style="display:flex;"><span>    next(f)  <span style="color:#75715e"># first line is &#34;#model_version:...,score_date:...&#34;</span>
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">for</span> row <span style="color:#f92672">in</span> csv<span style="color:#f92672">.</span>DictReader(f):
</span></span><span style="display:flex;"><span>        epss[row[<span style="color:#e6db74">&#34;cve&#34;</span>]] <span style="color:#f92672">=</span> (row[<span style="color:#e6db74">&#34;epss&#34;</span>], row[<span style="color:#e6db74">&#34;percentile&#34;</span>])
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span>outer <span style="color:#f92672">=</span> zipfile<span style="color:#f92672">.</span>ZipFile(sys<span style="color:#f92672">.</span>argv[<span style="color:#ae81ff">1</span>])
</span></span><span style="display:flex;"><span>inner <span style="color:#f92672">=</span> zipfile<span style="color:#f92672">.</span>ZipFile(io<span style="color:#f92672">.</span>BytesIO(outer<span style="color:#f92672">.</span>read(outer<span style="color:#f92672">.</span>namelist()[<span style="color:#ae81ff">0</span>])))
</span></span><span style="display:flex;"><span>out <span style="color:#f92672">=</span> csv<span style="color:#f92672">.</span>writer(sys<span style="color:#f92672">.</span>stdout)
</span></span><span style="display:flex;"><span>out<span style="color:#f92672">.</span>writerow([<span style="color:#e6db74">&#34;cve&#34;</span>, <span style="color:#e6db74">&#34;datePublished&#34;</span>, <span style="color:#e6db74">&#34;ssvc_timestamp&#34;</span>, <span style="color:#e6db74">&#34;automatable&#34;</span>,
</span></span><span style="display:flex;"><span>              <span style="color:#e6db74">&#34;technical_impact&#34;</span>, <span style="color:#e6db74">&#34;epss&#34;</span>, <span style="color:#e6db74">&#34;epss_percentile&#34;</span>])
</span></span><span style="display:flex;"><span><span style="color:#66d9ef">for</span> name <span style="color:#f92672">in</span> inner<span style="color:#f92672">.</span>namelist():
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">if</span> <span style="color:#e6db74">&#34;/CVE-&#34;</span> <span style="color:#f92672">not</span> <span style="color:#f92672">in</span> name <span style="color:#f92672">or</span> <span style="color:#f92672">not</span> name<span style="color:#f92672">.</span>endswith(<span style="color:#e6db74">&#34;.json&#34;</span>):
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">continue</span>
</span></span><span style="display:flex;"><span>    rec <span style="color:#f92672">=</span> json<span style="color:#f92672">.</span>loads(inner<span style="color:#f92672">.</span>read(name))
</span></span><span style="display:flex;"><span>    ts, opts <span style="color:#f92672">=</span> cisa_ssvc(rec)
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">if</span> <span style="color:#f92672">not</span> opts <span style="color:#f92672">or</span> opts<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;Exploitation&#34;</span>) <span style="color:#f92672">!=</span> <span style="color:#e6db74">&#34;poc&#34;</span>:
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">continue</span>
</span></span><span style="display:flex;"><span>    cve <span style="color:#f92672">=</span> rec[<span style="color:#e6db74">&#34;cveMetadata&#34;</span>][<span style="color:#e6db74">&#34;cveId&#34;</span>]
</span></span><span style="display:flex;"><span>    e, p <span style="color:#f92672">=</span> epss<span style="color:#f92672">.</span>get(cve, (<span style="color:#e6db74">&#34;&#34;</span>, <span style="color:#e6db74">&#34;&#34;</span>))
</span></span><span style="display:flex;"><span>    out<span style="color:#f92672">.</span>writerow([cve, rec[<span style="color:#e6db74">&#34;cveMetadata&#34;</span>]<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;datePublished&#34;</span>, <span style="color:#e6db74">&#34;&#34;</span>), ts,
</span></span><span style="display:flex;"><span>                  opts<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;Automatable&#34;</span>), opts<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;Technical Impact&#34;</span>), e, p])
</span></span></code></pre></div><p>We ran it with Python 3 against the 2026-11-18 release and EPSS file: it took about 37 seconds and wrote 47,926 rows. It loads the inner zip into memory, so give it at least 2.5 GB of RAM (peak resident memory was about 2.2 GB in our run). To keep the list current between full runs, apply cvelistV5&rsquo;s hourly changes as described in our <a href="/posts/cvelistv5-delta-json-deltalog-incremental-cve-sync/">delta.json and deltaLog.json guide</a>.</p>
<p>Then filter. For example, poc / yes / total with EPSS at or above 0.1 that is not in KEV:</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> csv<span style="color:#f92672">,</span> json
</span></span><span style="display:flex;"><span>kev <span style="color:#f92672">=</span> {v[<span style="color:#e6db74">&#34;cveID&#34;</span>] <span style="color:#66d9ef">for</span> v <span style="color:#f92672">in</span> json<span style="color:#f92672">.</span>load(open(<span style="color:#e6db74">&#34;known_exploited_vulnerabilities.json&#34;</span>))[<span style="color:#e6db74">&#34;vulnerabilities&#34;</span>]}
</span></span><span style="display:flex;"><span>rows <span style="color:#f92672">=</span> [r <span style="color:#66d9ef">for</span> r <span style="color:#f92672">in</span> csv<span style="color:#f92672">.</span>DictReader(open(<span style="color:#e6db74">&#34;poc.csv&#34;</span>))
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">if</span> r[<span style="color:#e6db74">&#34;automatable&#34;</span>] <span style="color:#f92672">==</span> <span style="color:#e6db74">&#34;yes&#34;</span> <span style="color:#f92672">and</span> r[<span style="color:#e6db74">&#34;technical_impact&#34;</span>] <span style="color:#f92672">==</span> <span style="color:#e6db74">&#34;total&#34;</span>
</span></span><span style="display:flex;"><span>        <span style="color:#f92672">and</span> float(r[<span style="color:#e6db74">&#34;epss&#34;</span>] <span style="color:#f92672">or</span> <span style="color:#ae81ff">0</span>) <span style="color:#f92672">&gt;=</span> <span style="color:#ae81ff">0.1</span> <span style="color:#f92672">and</span> r[<span style="color:#e6db74">&#34;cve&#34;</span>] <span style="color:#f92672">not</span> <span style="color:#f92672">in</span> kev]
</span></span><span style="display:flex;"><span>print(len(rows))
</span></span></code></pre></div><p>On the 2026-11-18 data this prints 394, since no poc / yes / total record is in KEV. The 0.1 cut-off is an example, not a recommendation; pick a threshold you can staff.</p>
<h2 id="how-to-use-poc-in-a-patch-decision">How to use poc in a patch decision</h2>
<ul>
<li><strong>Never as the only gate.</strong> 47,926 CVEs is a backlog, not a priority list. Match the list against your inventory first; the share that applies to you will be far smaller.</li>
<li><strong>Rank inside it.</strong> Within matched poc CVEs, sort by Automatable and Technical Impact, then EPSS, then your exposure (internet-facing first).</li>
<li><strong>KEV beats poc.</strong> A KEV entry means confirmed exploitation and, for US federal agencies, a due date. Check the KEV feed before the poc list.</li>
<li><strong>Watch for upgrades.</strong> A move from <code>none</code> to <code>poc</code>, or from <code>poc</code> to <code>active</code>, is the event worth an alert. Store the value you last saw and compare.</li>
<li><strong>Check the timestamp.</strong> A <code>none</code> with an old SSVC <code>timestamp</code> on a CVE that is now in the news may simply be stale.</li>
</ul>
<h2 id="limits-of-this-article">Limits of this article</h2>
<ul>
<li>The counts describe one snapshot: cvelistV5 at 2026-11-18 00:00 UTC, KEV version 2026.11.18 and EPSS scores of 2026-11-18. They move daily.</li>
<li>A current snapshot cannot tell you how often poc CVEs become KEV entries, because CISA rewrites the value to active. That needs historical snapshots.</li>
<li>CISA-ADP covers records CISA has scored, mostly those published or updated since 2024. Older CVEs and many 2022-2023 ones have no SSVC block.</li>
<li>We did not check whether the PoCs behind individual poc labels work, or where they are published.</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>Exploitation definitions, versions 1.0.0 and 1.1.0</td>
          <td><a href="https://github.com/CERTCC/SSVC/blob/main/src/ssvc/decision_points/ssvc/exploitation.py">CERTCC/SSVC exploitation.py</a></td>
          <td>Verified (verbatim)</td>
      </tr>
      <tr>
          <td>poc means a public PoC &ldquo;at the time of analysis&rdquo;; CVE-2024-25522 example</td>
          <td><a href="https://github.com/cisagov/vulnrichment">cisagov/vulnrichment README</a></td>
          <td>Verified (verbatim)</td>
      </tr>
      <tr>
          <td>222,849 SSVC records; 47,926 poc, 1,787 active, 173,136 none</td>
          <td><a href="https://github.com/CVEProject/cvelistV5/releases">cvelistV5 release, 2026-11-18 midnight</a>, counted with the script above</td>
          <td>Verified (computed)</td>
      </tr>
      <tr>
          <td>KEV: 1,786 entries; 1,782 active; four same-day additions; five active not in KEV</td>
          <td><a href="https://github.com/cisagov/kev-data">cisagov/kev-data</a>, catalog 2026.11.18, joined to the corpus</td>
          <td>Verified (computed)</td>
      </tr>
      <tr>
          <td>EPSS medians and threshold counts</td>
          <td><a href="https://github.com/empiricalsec/epss_scores">empiricalsec/epss_scores</a>, 2026-11-18 file, model v2026.06.15</td>
          <td>Verified (computed)</td>
      </tr>
      <tr>
          <td>EPSS estimates exploitation activity over the next 30 days</td>
          <td><a href="https://github.com/empiricalsec/epss_scores">empiricalsec/epss_scores README</a></td>
          <td>Verified</td>
      </tr>
  </tbody>
</table>
]]></content:encoded></item><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><item><title>CVE Exploitation Alerts: Diff CISA-ADP KEV and SSVC Data</title><link>https://firewallsync.com/posts/cve-exploitation-alerts-cisa-adp-kev-ssvc-cvelistv5-diff/</link><guid>https://firewallsync.com/posts/cve-exploitation-alerts-cisa-adp-kev-ssvc-cvelistv5-diff/</guid><pubDate>Mon, 16 Nov 2026 04:56:00 +0000</pubDate><dc:creator>John Marshall</dc:creator><category>Security Operations</category><description>A CVE record's CISA-ADP container gains a KEV block and an SSVC Exploitation value of active when exploitation is confirmed. We diffed 31,312 changed records between the October 17 and November 16, 2026 cvelistV5 snapshots to see how those signals move, then built a small watcher that alerts on them.</description><enclosure url="https://firewallsync.com/posts/cve-exploitation-alerts-cisa-adp-kev-ssvc-cvelistv5-diff/cover_hu7826863987297709055.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/cve-exploitation-alerts-cisa-adp-kev-ssvc-cvelistv5-diff/cover_hu7826863987297709055.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/cve-exploitation-alerts-cisa-adp-kev-ssvc-cvelistv5-diff/cover_hu7826863987297709055.jpg" alt="A person standing on a frozen, rocky shore holds a lit flare above their head, trailing a cloud of red smoke against a white sky" width="1200" height="630"></p><p>If you want to know the moment a CVE in your inventory becomes exploited, there are two machine-readable places to look: CISA&rsquo;s KEV JSON feed and the CISA-ADP container inside the CVE record itself. The record carries an SSVC <strong>Exploitation</strong> value (<code>none</code>, <code>poc</code> or <code>active</code>) and, for KEV CVEs, a <code>kev</code> block. Diffing those two fields between record versions gives you an exploitation alert that rides on the same cvelistV5 sync you may already run.</p>
<p>We measured how those fields actually moved over 30 days, from the cvelistV5 snapshot tagged <code>cve_2026-10-17_0000Z</code> to <code>cve_2026-11-16_0000Z</code>. The short answer: in this window, <code>active</code> never appeared on a CVE that was not already in KEV, and the <code>kev</code> block followed the KEV catalog by about a day, with two misses. So the KEV feed stays the primary trigger; the CVE-record diff is the second signal, and it is the one that catches <code>poc</code> changes and rejections.</p>
<p>This builds on the <a href="/posts/vulnerability-prioritization-workflow-cve-record-to-patch-ticket/">vulnerability prioritization workflow</a>, where exploitation is the first gate on the way from CVE record to ticket.</p>
<h2 id="where-the-exploitation-signals-live-in-a-cve-record">Where the exploitation signals live in a CVE record</h2>
<p>CISA publishes its enrichment through an Authorized Data Publisher container (see <a href="/posts/cve-adp-containers-cisa-adp-cve-program-supplier-sadp/">CVE ADP containers</a> for how ADP containers relate to the CNA&rsquo;s). In a CVE JSON 5 record, look for <code>containers.adp[]</code> with <code>providerMetadata.shortName</code> equal to <code>CISA-ADP</code>. Its <code>metrics[]</code> array holds <code>other</code> objects, two of which matter here. From the current record for GitLab CVE-2026-97229:</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 style="color:#f92672">&#34;type&#34;</span>: <span style="color:#e6db74">&#34;ssvc&#34;</span>, <span style="color:#f92672">&#34;content&#34;</span>: {<span style="color:#f92672">&#34;id&#34;</span>: <span style="color:#e6db74">&#34;CVE-2026-97229&#34;</span>, <span style="color:#f92672">&#34;role&#34;</span>: <span style="color:#e6db74">&#34;CISA Coordinator&#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;...&#34;</span>}, {<span style="color:#f92672">&#34;Technical Impact&#34;</span>: <span style="color:#e6db74">&#34;...&#34;</span>}],
</span></span><span style="display:flex;"><span>  <span style="color:#f92672">&#34;version&#34;</span>: <span style="color:#e6db74">&#34;2.0.3&#34;</span>, <span style="color:#f92672">&#34;timestamp&#34;</span>: <span style="color:#e6db74">&#34;...&#34;</span>}}
</span></span><span style="display:flex;"><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 style="color:#f92672">&#34;dateAdded&#34;</span>: <span style="color:#e6db74">&#34;2026-10-29&#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-97229&#34;</span>}}
</span></span></code></pre></div><p>(Automatable, Technical Impact and the timestamp are elided; the <a href="/posts/cisa-vulnrichment-how-to-read-ssvc-values-in-a-cve-record-and-turn-them-into-a-patch-decision/">Vulnrichment explainer</a> covers all three SSVC values.)</p>
<p>The <a href="https://github.com/cisagov/vulnrichment/blob/develop/README.md">CISA Vulnrichment README</a> states the rule for the second block: &ldquo;For those CVEs that are on the KEV, the CISA ADP will add a KEV block. For those that aren&rsquo;t, no update will occur.&rdquo; The SSVC values come from the CISA Coordinator decision tree; the SSVC project&rsquo;s <a href="https://github.com/CERTCC/SSVC/blob/main/src/ssvc/decision_points/ssvc/exploitation.py">Exploitation decision point</a> defines <code>active</code> as &ldquo;Shared, observable, reliable evidence that the exploit is being used in the wild by real attackers; there is credible public reporting&rdquo;, and <code>none</code> as no evidence of active exploitation and no public proof of concept.</p>
<table>
  <thead>
      <tr>
          <th>Field</th>
          <th>Values</th>
          <th>What a change means</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><code>ssvc</code> Exploitation</td>
          <td><code>none</code>, <code>poc</code>, <code>active</code></td>
          <td>CISA&rsquo;s current assessment of exploitation state</td>
      </tr>
      <tr>
          <td><code>kev</code> dateAdded</td>
          <td>a date</td>
          <td>The CVE is on the KEV catalog; date matches the catalog</td>
      </tr>
      <tr>
          <td><code>cveMetadata.state</code></td>
          <td><code>PUBLISHED</code>, <code>REJECTED</code></td>
          <td>A rejected record keeps no ADP containers</td>
      </tr>
  </tbody>
</table>
<h2 id="how-we-measured">How we measured</h2>
<p>We cloned <a href="https://github.com/CVEProject/cvelistV5">CVEProject/cvelistV5</a> without blobs and ran <code>git diff --name-status</code> between the two tags. The <code>cve_2026-10-17_0000Z</code> tag points at a commit made 2026-10-16 23:29 UTC; <code>cve_2026-11-16_0000Z</code> at 2026-11-16 00:15 UTC. That produced 31,312 changed CVE files: 16,690 added and 14,622 modified. We fetched both versions of each modified record and the new version of each added record from raw.githubusercontent.com at the two commits, then compared the CISA-ADP values. KEV comparisons used the <a href="https://github.com/cisagov/kev-data">kev-data</a> JSON as of November 16, 2026.</p>
<p>A two-point diff only sees the start and end state, so a record that went <code>none</code> to <code>poc</code> to <code>active</code> inside the window counts once, as <code>none</code> to <code>active</code>.</p>
<h2 id="what-moved-in-30-days">What moved in 30 days</h2>
<table>
  <thead>
      <tr>
          <th>Change in CISA-ADP Exploitation (modified records)</th>
          <th>Records</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>no SSVC block → <code>none</code></td>
          <td>2,389</td>
      </tr>
      <tr>
          <td>no SSVC block → <code>poc</code></td>
          <td>282</td>
      </tr>
      <tr>
          <td><code>none</code> → <code>active</code></td>
          <td>14</td>
      </tr>
      <tr>
          <td><code>none</code> → <code>poc</code></td>
          <td>10</td>
      </tr>
      <tr>
          <td><code>poc</code> → <code>none</code></td>
          <td>5</td>
      </tr>
      <tr>
          <td>no SSVC block → <code>active</code></td>
          <td>2</td>
      </tr>
      <tr>
          <td><code>none</code> or <code>poc</code> → no SSVC block</td>
          <td>19</td>
      </tr>
  </tbody>
</table>
<p>All 19 losses were records that changed from <code>PUBLISHED</code> to <code>REJECTED</code>; none of the 672 rejected records in the changed set carries an ADP container. (29 modified records were rejected in the window in total; the other 10 had no CISA-ADP SSVC to lose.) The <a href="/posts/cve-record-states-published-rejected-and-disputed-what-each-means-for-vulnerability-triage/">CVE record states</a> post covers what a rejection means for triage.</p>
<p>Of the 16,690 records first published in the window, 12,071 arrived with Exploitation <code>none</code>, 1,940 with <code>poc</code>, 18 with <code>active</code> and 2,661 with no CISA-ADP SSVC block yet.</p>
<p>Two findings matter for alerting:</p>
<ol>
<li><strong><code>active</code> tracked KEV exactly.</strong> All 34 records that gained <code>active</code> (16) or were published with it (18) were on the KEV catalog. In this window, alerting on <code>active</code> would not have told you about any CVE that the KEV feed did not.</li>
<li><strong>Exploitation can go down.</strong> Five records went from <code>poc</code> to <code>none</code>. Store the current value and alert on increases; do not assume the field only ratchets upward.</li>
</ol>
<h2 id="how-closely-the-kev-block-followed-the-catalog">How closely the kev block followed the catalog</h2>
<p>CISA added 33 CVEs to KEV with a <code>dateAdded</code> between October 17 and November 15, 2026. By the November 16 snapshot:</p>
<ul>
<li>31 had a CISA-ADP <code>kev</code> block whose <code>dateAdded</code> matched the catalog.</li>
<li>All 33 had SSVC Exploitation <code>active</code>.</li>
<li>Two had <code>active</code> but <strong>no</strong> <code>kev</code> block: Adobe CVE-2026-48356 and Google CVE-2026-111497, both added to KEV on October 27. Their CISA-ADP containers were last updated on October 28 with only the SSVC entry.</li>
</ul>
<p>For the 31 with a block, the CISA-ADP container&rsquo;s <code>dateUpdated</code> fell one calendar day after the KEV <code>dateAdded</code> for 28 CVEs, two days later for 2 (the PHP pair CVE-2026-109618 and CVE-2026-109619) and four days later for 1 (Ivanti CVE-2026-118527). Most updates landed between 03:55 and 04:57 UTC. Because <code>dateUpdated</code> is the container&rsquo;s <em>last</em> update, it is an upper bound on when the block appeared, not an exact timestamp. The KEV catalog&rsquo;s own <code>dateAdded</code> is a date with no time.</p>
<p>The practical reading: the record-level <code>kev</code> block is a copy that typically lags the catalog by about a day and occasionally does not arrive. If you need same-day KEV alerts, read the catalog. The <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 matching it against a scanner export.</p>
<h2 id="a-watcher-that-diffs-cisa-adp-signals">A watcher that diffs CISA-ADP signals</h2>
<p>The script below reads cvelistV5&rsquo;s <code>delta.json</code> (the change list described in the <a href="/posts/cvelistv5-delta-json-deltalog-incremental-cve-sync/">delta.json and deltaLog.json guide</a>), fetches each new or updated record, extracts the CISA-ADP signals and compares them with a local state file. It alerts on a new <code>kev</code> block, an increase in Exploitation to <code>poc</code> or <code>active</code>, and a change to <code>REJECTED</code>. Python 3 standard library only.</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:#75715e">#!/usr/bin/env python3</span>
</span></span><span style="display:flex;"><span><span style="color:#e6db74">&#34;&#34;&#34;Alert when a CVE record&#39;s CISA-ADP container gains a KEV block or a new SSVC Exploitation value.
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">Usage:
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">  python3 adp_watch.py state.json                 # read cvelistV5 delta.json, fetch changed records
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">  python3 adp_watch.py state.json rec1.json ...   # offline: compare local record files
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">&#34;&#34;&#34;</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> urllib.request
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span>DELTA <span style="color:#f92672">=</span> <span style="color:#e6db74">&#34;https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/delta.json&#34;</span>
</span></span><span style="display:flex;"><span>RANK <span style="color:#f92672">=</span> {<span style="color:#66d9ef">None</span>: <span style="color:#ae81ff">0</span>, <span style="color:#e6db74">&#34;none&#34;</span>: <span style="color:#ae81ff">1</span>, <span style="color:#e6db74">&#34;poc&#34;</span>: <span style="color:#ae81ff">2</span>, <span style="color:#e6db74">&#34;active&#34;</span>: <span style="color:#ae81ff">3</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">signals</span>(rec):
</span></span><span style="display:flex;"><span>    s <span style="color:#f92672">=</span> {<span style="color:#e6db74">&#34;state&#34;</span>: rec[<span style="color:#e6db74">&#34;cveMetadata&#34;</span>][<span style="color:#e6db74">&#34;state&#34;</span>], <span style="color:#e6db74">&#34;exploitation&#34;</span>: <span style="color:#66d9ef">None</span>, <span style="color:#e6db74">&#34;kev&#34;</span>: <span style="color:#66d9ef">None</span>}
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">for</span> adp <span style="color:#f92672">in</span> rec<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 style="color:#f92672">or</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">continue</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:#f92672">or</span> []:
</span></span><span style="display:flex;"><span>            other <span style="color:#f92672">=</span> m<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;other&#34;</span>) <span style="color:#f92672">or</span> {}
</span></span><span style="display:flex;"><span>            <span style="color:#66d9ef">if</span> other<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;type&#34;</span>) <span style="color:#f92672">==</span> <span style="color:#e6db74">&#34;ssvc&#34;</span>:
</span></span><span style="display:flex;"><span>                <span style="color:#66d9ef">for</span> opt <span style="color:#f92672">in</span> other[<span style="color:#e6db74">&#34;content&#34;</span>]<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;options&#34;</span>, []):
</span></span><span style="display:flex;"><span>                    <span style="color:#66d9ef">if</span> <span style="color:#e6db74">&#34;Exploitation&#34;</span> <span style="color:#f92672">in</span> opt:
</span></span><span style="display:flex;"><span>                        s[<span style="color:#e6db74">&#34;exploitation&#34;</span>] <span style="color:#f92672">=</span> opt[<span style="color:#e6db74">&#34;Exploitation&#34;</span>]
</span></span><span style="display:flex;"><span>            <span style="color:#66d9ef">elif</span> other<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;type&#34;</span>) <span style="color:#f92672">==</span> <span style="color:#e6db74">&#34;kev&#34;</span>:
</span></span><span style="display:flex;"><span>                s[<span style="color:#e6db74">&#34;kev&#34;</span>] <span style="color:#f92672">=</span> other[<span style="color:#e6db74">&#34;content&#34;</span>]<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;dateAdded&#34;</span>)
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">return</span> s
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span><span style="color:#66d9ef">def</span> <span style="color:#a6e22e">compare</span>(cve, old, new):
</span></span><span style="display:flex;"><span>    alerts <span style="color:#f92672">=</span> []
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">if</span> new[<span style="color:#e6db74">&#34;state&#34;</span>] <span style="color:#f92672">==</span> <span style="color:#e6db74">&#34;REJECTED&#34;</span> <span style="color:#f92672">and</span> (old <span style="color:#f92672">or</span> {})<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;state&#34;</span>) <span style="color:#f92672">!=</span> <span style="color:#e6db74">&#34;REJECTED&#34;</span>:
</span></span><span style="display:flex;"><span>        alerts<span style="color:#f92672">.</span>append(<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">: record REJECTED, ADP data removed&#34;</span>)
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">if</span> new[<span style="color:#e6db74">&#34;kev&#34;</span>] <span style="color:#f92672">and</span> <span style="color:#f92672">not</span> (old <span style="color:#f92672">or</span> {})<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;kev&#34;</span>):
</span></span><span style="display:flex;"><span>        alerts<span style="color:#f92672">.</span>append(<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">: KEV block added (dateAdded </span><span style="color:#e6db74">{</span>new[<span style="color:#e6db74">&#39;kev&#39;</span>]<span style="color:#e6db74">}</span><span style="color:#e6db74">)&#34;</span>)
</span></span><span style="display:flex;"><span>    o <span style="color:#f92672">=</span> (old <span style="color:#f92672">or</span> {})<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;exploitation&#34;</span>)
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">if</span> RANK<span style="color:#f92672">.</span>get(new[<span style="color:#e6db74">&#34;exploitation&#34;</span>], <span style="color:#ae81ff">0</span>) <span style="color:#f92672">&gt;</span> RANK<span style="color:#f92672">.</span>get(o, <span style="color:#ae81ff">0</span>) <span style="color:#f92672">and</span> new[<span style="color:#e6db74">&#34;exploitation&#34;</span>] <span style="color:#f92672">in</span> (<span style="color:#e6db74">&#34;poc&#34;</span>, <span style="color:#e6db74">&#34;active&#34;</span>):
</span></span><span style="display:flex;"><span>        alerts<span style="color:#f92672">.</span>append(<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">: SSVC Exploitation </span><span style="color:#e6db74">{</span>o<span style="color:#e6db74">}</span><span style="color:#e6db74"> -&gt; </span><span style="color:#e6db74">{</span>new[<span style="color:#e6db74">&#39;exploitation&#39;</span>]<span style="color:#e6db74">}</span><span style="color:#e6db74">&#34;</span>)
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">return</span> alerts
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span><span style="color:#66d9ef">def</span> <span style="color:#a6e22e">get</span>(url):
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">with</span> urllib<span style="color:#f92672">.</span>request<span style="color:#f92672">.</span>urlopen(url, timeout<span style="color:#f92672">=</span><span style="color:#ae81ff">30</span>) <span style="color:#66d9ef">as</span> r:
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">return</span> json<span style="color:#f92672">.</span>load(r)
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span><span style="color:#66d9ef">def</span> <span style="color:#a6e22e">main</span>():
</span></span><span style="display:flex;"><span>    state_path, files <span style="color:#f92672">=</span> sys<span style="color:#f92672">.</span>argv[<span style="color:#ae81ff">1</span>], sys<span style="color:#f92672">.</span>argv[<span style="color:#ae81ff">2</span>:]
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">try</span>:
</span></span><span style="display:flex;"><span>        state <span style="color:#f92672">=</span> json<span style="color:#f92672">.</span>load(open(state_path))
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">except</span> <span style="color:#a6e22e">FileNotFoundError</span>:
</span></span><span style="display:flex;"><span>        state <span style="color:#f92672">=</span> {}
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">if</span> files:
</span></span><span style="display:flex;"><span>        records <span style="color:#f92672">=</span> [json<span style="color:#f92672">.</span>load(open(f)) <span style="color:#66d9ef">for</span> f <span style="color:#f92672">in</span> files]
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">else</span>:
</span></span><span style="display:flex;"><span>        delta <span style="color:#f92672">=</span> get(DELTA)
</span></span><span style="display:flex;"><span>        print(<span style="color:#e6db74">f</span><span style="color:#e6db74">&#34;delta fetchTime </span><span style="color:#e6db74">{</span>delta[<span style="color:#e6db74">&#39;fetchTime&#39;</span>]<span style="color:#e6db74">}</span><span style="color:#e6db74">: </span><span style="color:#e6db74">{</span>delta[<span style="color:#e6db74">&#39;numberOfChanges&#39;</span>]<span style="color:#e6db74">}</span><span style="color:#e6db74"> changes&#34;</span>)
</span></span><span style="display:flex;"><span>        records <span style="color:#f92672">=</span> [get(e[<span style="color:#e6db74">&#34;githubLink&#34;</span>]) <span style="color:#66d9ef">for</span> k <span style="color:#f92672">in</span> (<span style="color:#e6db74">&#34;new&#34;</span>, <span style="color:#e6db74">&#34;updated&#34;</span>) <span style="color:#66d9ef">for</span> e <span style="color:#f92672">in</span> delta<span style="color:#f92672">.</span>get(k, [])]
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">for</span> rec <span style="color:#f92672">in</span> records:
</span></span><span style="display:flex;"><span>        cve <span style="color:#f92672">=</span> rec[<span style="color:#e6db74">&#34;cveMetadata&#34;</span>][<span style="color:#e6db74">&#34;cveId&#34;</span>]
</span></span><span style="display:flex;"><span>        new <span style="color:#f92672">=</span> signals(rec)
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">for</span> a <span style="color:#f92672">in</span> compare(cve, state<span style="color:#f92672">.</span>get(cve), new):
</span></span><span style="display:flex;"><span>            print(<span style="color:#e6db74">&#34;ALERT&#34;</span>, a)
</span></span><span style="display:flex;"><span>        state[cve] <span style="color:#f92672">=</span> new
</span></span><span style="display:flex;"><span>    json<span style="color:#f92672">.</span>dump(state, open(state_path, <span style="color:#e6db74">&#34;w&#34;</span>), indent<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><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>    main()
</span></span></code></pre></div><p><strong>How we ran it (Python 3.13, November 16, 2026):</strong> feeding the October 17 version and then the November 16 version of CVE-2026-97229 printed:</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>ALERT CVE-2026-97229: KEV block added (dateAdded 2026-10-29)
</span></span><span style="display:flex;"><span>ALERT CVE-2026-97229: SSVC Exploitation none -&gt; active
</span></span></code></pre></div><p>The same two-step test on CVE-2023-54404 printed <code>record REJECTED, ADP data removed</code>. A live run against <code>delta.json</code> (fetchTime 2026-11-16T03:48:36Z, one change) fetched the record and wrote state without alerting.</p>
<p>Limits of the script as written: it fetches records one at a time, so a large delta is slow; <code>delta.json</code> only holds the latest batch, so a missed run loses changes unless you replay <code>deltaLog.json</code> as the delta guide describes; and a CVE seen for the first time with <code>poc</code> or <code>active</code> alerts immediately, which is what you want for new records but noisy on the first run. Filter to the CVEs in your inventory before alerting, and seed the state file from a full snapshot before going live. Treat it as a starting point, not production code.</p>
<h2 id="wiring-it-into-a-patch-decision">Wiring it into a patch decision</h2>
<ul>
<li><strong>KEV feed first.</strong> Poll the KEV JSON and alert on new <code>cveID</code> values in your inventory. In our window it was never behind the CVE record.</li>
<li><strong>CISA-ADP diff second.</strong> Use it for <code>poc</code> changes, SSVC values on CVEs that will never reach KEV, and rejections that should close tickets.</li>
<li><strong>Re-score on change.</strong> An Exploitation change moves the SSVC outcome; feed it back into the decision step of the <a href="/posts/vulnerability-prioritization-workflow-cve-record-to-patch-ticket/">prioritization workflow</a> rather than paging on every <code>poc</code>.</li>
<li><strong>Watch the ransomware flag separately.</strong> KEV&rsquo;s <code>knownRansomwareCampaignUse</code> changes in the catalog only; see <a href="/posts/kev-knownransomwarecampaignuse-unknown-to-known-flips/">KEV ransomware flag flips</a>.</li>
</ul>
<h2 id="limits-of-this-article">Limits of this article</h2>
<ul>
<li>One 30-day window. The finding that <code>active</code> matched KEV exactly is an observation for October 17 to November 16, 2026, not a documented CISA rule.</li>
<li>Two-point diff: intermediate states inside the window are not visible.</li>
<li>Lag figures use the CISA-ADP container&rsquo;s last <code>dateUpdated</code>, which can be later than the moment the <code>kev</code> block first appeared.</li>
<li>The two missing <code>kev</code> blocks were missing as of the November 16 snapshot; they may be added later.</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>CISA-ADP adds a KEV block only for KEV CVEs</td>
          <td><a href="https://github.com/cisagov/vulnrichment/blob/develop/README.md">cisagov/vulnrichment README</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>SSVC Exploitation definitions</td>
          <td><a href="https://github.com/CERTCC/SSVC/blob/main/src/ssvc/decision_points/ssvc/exploitation.py">CERTCC/SSVC exploitation.py</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>31,312 changed records; transition counts; 34 active, all in KEV</td>
          <td><a href="https://github.com/CVEProject/cvelistV5">cvelistV5</a> tags cve_2026-10-17_0000Z and cve_2026-11-16_0000Z, our script</td>
          <td>Verified (computed)</td>
      </tr>
      <tr>
          <td>33 KEV adds Oct 17 to Nov 15; 31 with kev block; lag 1/2/4 days</td>
          <td><a href="https://github.com/cisagov/kev-data">cisagov/kev-data</a>, CVE records at cve_2026-11-16_0000Z</td>
          <td>Verified (computed); lag qualified as upper bound</td>
      </tr>
      <tr>
          <td>CVE-2026-48356 and CVE-2026-111497 lack a kev block</td>
          <td>CVE records at cve_2026-11-16_0000Z</td>
          <td>Verified as of that snapshot</td>
      </tr>
      <tr>
          <td>Watcher output</td>
          <td>Run on November 16, 2026</td>
          <td>Verified</td>
      </tr>
  </tbody>
</table>
]]></content:encoded></item><item><title>CVE problemTypes and cweId: Getting CWE From CVE JSON</title><link>https://firewallsync.com/posts/cve-problemtypes-cweid-cwe-from-cve-json/</link><guid>https://firewallsync.com/posts/cve-problemtypes-cweid-cwe-from-cve-json/</guid><pubDate>Sun, 15 Nov 2026 04:50:00 +0000</pubDate><dc:creator>Craig Leslie</dc:creator><category>AppSec &amp; APIs</category><description>The CWE for a CVE lives in problemTypes[].descriptions[].cweId, but a count across the November 15, 2026 cvelistV5 snapshot shows 24% of 2026 CVE records have no CNA cweId. Where the gaps come from, what CISA-ADP fills in (often CWE-284), and a parser that handles all four cases.</description><enclosure url="https://firewallsync.com/posts/cve-problemtypes-cweid-cwe-from-cve-json/cover_hu11811165115856360047.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/cve-problemtypes-cweid-cwe-from-cve-json/cover_hu11811165115856360047.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/cve-problemtypes-cweid-cwe-from-cve-json/cover_hu11811165115856360047.jpg" alt="Rows of wooden library card catalogue drawers with metal label holders, receding into soft focus" width="1200" height="630"></p><p><strong>Short answer:</strong> the CWE for a CVE is in <code>containers.cna.problemTypes[].descriptions[].cweId</code>. That field is optional, and a lot of records do not have it. Of the 97,709 CVE records published in 2026 in the cvelistV5 snapshot of November 15, 2026, <strong>24.1% have no CNA <code>cweId</code></strong>: 13,044 carry only text and 10,476 have no <code>problemTypes</code> at all. CISA-ADP fills 15,650 of those gaps, most often with CWE-284, a mapping CWE itself discourages. If you build CWE metrics from CVE JSON, read three places in a fixed order and keep track of which one answered.</p>
<p>This is a field-level guide for engineers building weakness dashboards, SAST/CVE correlation or CWE Top 25-style reports from raw CVE data. Where it fits in the larger triage flow is covered in the <a href="/posts/vulnerability-prioritization-workflow-cve-record-to-patch-ticket/">vulnerability prioritization workflow</a>. How ADP containers work in general is in <a href="/posts/cve-adp-containers-cisa-adp-cve-program-supplier-sadp/">CVE ADP containers: CISA-ADP, CVE Program and supplier ADPs</a>.</p>
<h2 id="the-problemtypes-structure">The problemTypes structure</h2>
<p>The <a href="https://github.com/CVEProject/cve-schema/blob/main/schema/CVE_Record_Format.json">CVE Record Format schema</a> (v5.2.0 in the repository) defines <code>problemTypes</code> as an array with at least one item. Each item has a required <code>descriptions</code> array, and each description object looks like this:</p>
<table>
  <thead>
      <tr>
          <th>Property</th>
          <th>Required</th>
          <th>Schema constraint</th>
          <th>What it holds</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><code>lang</code></td>
          <td>yes</td>
          <td>language tag</td>
          <td><code>en</code>, <code>en-US</code></td>
      </tr>
      <tr>
          <td><code>description</code></td>
          <td>yes</td>
          <td>string, 1-4096 chars</td>
          <td>&ldquo;Text description of problemType, or title from CWE or OWASP.&rdquo;</td>
      </tr>
      <tr>
          <td><code>cweId</code></td>
          <td>no</td>
          <td><code>^CWE-[1-9][0-9]*$</code>, 5-9 chars</td>
          <td>&ldquo;CWE ID of the CWE that best describes this problemType entry.&rdquo;</td>
      </tr>
      <tr>
          <td><code>type</code></td>
          <td>no</td>
          <td>free string, 1-128 chars</td>
          <td>&ldquo;Problemtype source, text, OWASP, CWE, etc.,&rdquo;</td>
      </tr>
      <tr>
          <td><code>references</code></td>
          <td>no</td>
          <td>references array</td>
          <td>supporting links</td>
      </tr>
  </tbody>
</table>
<p>A well-formed CNA entry:</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 style="color:#e6db74">&#34;problemTypes&#34;</span><span style="color:#960050;background-color:#1e0010">:</span> [
</span></span><span style="display:flex;"><span>  { <span style="color:#f92672">&#34;descriptions&#34;</span>: [
</span></span><span style="display:flex;"><span>      { <span style="color:#f92672">&#34;lang&#34;</span>: <span style="color:#e6db74">&#34;en&#34;</span>, <span style="color:#f92672">&#34;type&#34;</span>: <span style="color:#e6db74">&#34;CWE&#34;</span>, <span style="color:#f92672">&#34;cweId&#34;</span>: <span style="color:#e6db74">&#34;CWE-352&#34;</span>,
</span></span><span style="display:flex;"><span>        <span style="color:#f92672">&#34;description&#34;</span>: <span style="color:#e6db74">&#34;CWE-352 Cross-Site Request Forgery (CSRF)&#34;</span> } ] }
</span></span><span style="display:flex;"><span>]
</span></span></code></pre></div><p>Two schema details cause most parser bugs:</p>
<ul>
<li><strong><code>problemTypes</code> is not required for a CNA.</strong> The <code>cnaPublishedContainer</code> required list is <code>providerMetadata</code>, <code>descriptions</code>, <code>affected</code> and <code>references</code>. The schema&rsquo;s description text says the field &ldquo;Must contain: At least one entry&rdquo;, but validation will not enforce that.</li>
<li><strong><code>type</code> is free text.</strong> In the full corpus the most common values are <code>CWE</code> (198,469 descriptions) and <code>text</code> (183,625), then a missing <code>type</code> (19,161), <code>Impact</code> (2,778) and lower-case <code>cwe</code> (1,586), plus a tail of one-off values such as &ldquo;RCE (Remote Code Execution)&rdquo;. <code>type: &quot;CWE&quot;</code> does not guarantee a <code>cweId</code> is present.</li>
</ul>
<p>The program rules match the schema&rsquo;s looseness. <a href="https://www.cve.org/Resources/Roles/Cnas/CNA_Rules_v4.1.0.pdf">CNA Operational Rules 4.1.0</a> (effective May 14, 2025), rule 5.1.7, say a CNA &ldquo;MUST identify the type of Vulnerability&rdquo; and that the record &ldquo;SHOULD use the Common Weakness Enumeration (CWE)&rdquo;. A text label satisfies the MUST.</p>
<h2 id="how-often-the-cna-supplies-a-cweid">How often the CNA supplies a cweId</h2>
<p>We streamed the <code>2026-11-15_all_CVEs_at_midnight</code> release zip from cvelistV5 and counted every record in state <code>PUBLISHED</code>, grouped by the year of <code>cveMetadata.datePublished</code>. Each record lands in exactly one CNA bucket.</p>
<table>
  <thead>
      <tr>
          <th>Publication year</th>
          <th>Published records</th>
          <th>CNA cweId</th>
          <th>CNA text only</th>
          <th>No problemTypes</th>
          <th>No cweId anywhere (CNA or CISA-ADP)</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>2024</td>
          <td>39,924</td>
          <td>25,623 (64.2%)</td>
          <td>9,054 (22.7%)</td>
          <td>5,247 (13.1%)</td>
          <td>5,366 (13.4%)</td>
      </tr>
      <tr>
          <td>2025</td>
          <td>48,150</td>
          <td>34,764 (72.2%)</td>
          <td>6,982 (14.5%)</td>
          <td>6,404 (13.3%)</td>
          <td>5,626 (11.7%)</td>
      </tr>
      <tr>
          <td>2026 (to Nov 15)</td>
          <td>97,709</td>
          <td>74,189 (75.9%)</td>
          <td>13,044 (13.3%)</td>
          <td>10,476 (10.7%)</td>
          <td>7,870 (8.1%)</td>
      </tr>
  </tbody>
</table>
<p>CNA coverage is improving year on year, but roughly one in four 2026 records still needs a fallback. Most records with a CNA <code>cweId</code> have exactly one: across all years, 157,531 of 177,478 (88.8%) list a single distinct CWE and 19,947 list two or more. Treat <code>cweId</code> as a set, not a scalar.</p>
<h2 id="where-the-gaps-come-from">Where the gaps come from</h2>
<p>The gaps are not random. They follow individual CNAs&rsquo; publishing habits, which matters because a dashboard filtered to one vendor can show zero CWE data for that vendor without anything being wrong with your parser.</p>
<table>
  <thead>
      <tr>
          <th>CNA (<code>assignerShortName</code>)</th>
          <th>2026 records</th>
          <th>Pattern</th>
          <th>Example</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><code>Linux</code></td>
          <td>8,262</td>
          <td>no <code>problemTypes</code> in any 2026 record</td>
          <td>CVE-2026-74687</td>
      </tr>
      <tr>
          <td><code>oracle</code></td>
          <td>4,154</td>
          <td>all text only (risk sentence such as &ldquo;Easily exploitable vulnerability allows &hellip;&rdquo;)</td>
          <td>CVE-2026-82997</td>
      </tr>
      <tr>
          <td><code>mitre</code></td>
          <td>3,773</td>
          <td>3,027 text-only, description <code>n/a</code></td>
          <td>CVE-2026-104586</td>
      </tr>
      <tr>
          <td><code>WPScan</code></td>
          <td>2,314</td>
          <td>CWE named in text with <code>type: &quot;CWE&quot;</code>, no <code>cweId</code> (2,312 records)</td>
          <td>CVE-2026-82126</td>
      </tr>
      <tr>
          <td><code>apple</code></td>
          <td>1,196</td>
          <td>all text only</td>
          <td>CVE-2026-86917</td>
      </tr>
      <tr>
          <td><code>Chrome</code></td>
          <td>3,972</td>
          <td>705 text-only (labels such as &ldquo;Inappropriate implementation&rdquo;)</td>
          <td>CVE-2026-106484</td>
      </tr>
      <tr>
          <td><code>mozilla</code></td>
          <td>968</td>
          <td>no <code>problemTypes</code> in any 2026 record</td>
          <td></td>
      </tr>
  </tbody>
</table>
<p>The WPScan pattern deserves its own handling. Its entries look like this:</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 style="color:#f92672">&#34;description&#34;</span>: <span style="color:#e6db74">&#34;CWE-284 Improper Access Control&#34;</span>, <span style="color:#f92672">&#34;lang&#34;</span>: <span style="color:#e6db74">&#34;en&#34;</span>, <span style="color:#f92672">&#34;type&#34;</span>: <span style="color:#e6db74">&#34;CWE&#34;</span> }
</span></span></code></pre></div><p>A parser that only reads <code>cweId</code> drops these. In 2026, 3,063 records name a CWE ID only in CNA text, and 2,559 description objects have <code>type</code> <code>CWE</code> or <code>cwe</code> with no <code>cweId</code>, 2,359 of them from WPScan. CISA&rsquo;s own <a href="https://github.com/cisagov/vulnrichment">Vulnrichment README</a> uses a WPScan record, CVE-2024-3477, as its example of CISA adding a CWE; the CNA text in that record already says &ldquo;CWE-352 Cross-Site Request Forgery (CSRF)&rdquo;.</p>
<h2 id="what-cisa-adp-adds">What CISA-ADP adds</h2>
<p>The <a href="https://github.com/cisagov/vulnrichment">Vulnrichment README</a> says that once CVEs are SSVC-scored, &ldquo;some higher-risk CVEs will also receive enrichment of CWE and/or CVSS data points, where possible&rdquo;, that CISA populates the ADP container only for CVEs &ldquo;that do not already have these fields populated by the originating CNA&rdquo;, and that &ldquo;At no point will CISA overwrite the originating CNA&rsquo;s data&rdquo;. If a CNA later adds the data, &ldquo;the CISA ADP will drop its own assessments&rdquo;. When both exist, it says the CNA&rsquo;s data &ldquo;should take precedence&rdquo;.</p>
<p>In 2026 records:</p>
<ul>
<li>CISA-ADP carries a <code>cweId</code> in 16,066 records. In 15,650 of them the CNA had none.</li>
<li>In 416 records both containers carry a <code>cweId</code>; in 101 they differ. Per the README, prefer the CNA value.</li>
<li>Of the 3,063 records where the CNA named a CWE only in text, CISA-ADP has a <code>cweId</code> in 2,591, and in 2,544 it is the same ID the text already named.</li>
<li>The only other ADP supplying <code>cweId</code> across the corpus is <code>redhat-SADP</code> (1,124 records). CISA-ADP has 44,152.</li>
</ul>
<p>The most frequent CWEs CISA-ADP adds when the CNA gave none, 2026 records:</p>
<table>
  <thead>
      <tr>
          <th>CWE</th>
          <th>Records</th>
          <th>CWE mapping note</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>CWE-284 Improper Access Control</td>
          <td>3,334</td>
          <td>Pillar; usage DISCOURAGED</td>
      </tr>
      <tr>
          <td>CWE-200 Exposure of Sensitive Information</td>
          <td>975</td>
          <td></td>
      </tr>
      <tr>
          <td>CWE-79 Cross-site Scripting</td>
          <td>829</td>
          <td></td>
      </tr>
      <tr>
          <td>CWE-269 Improper Privilege Management</td>
          <td>717</td>
          <td></td>
      </tr>
      <tr>
          <td>CWE-416 Use After Free</td>
          <td>696</td>
          <td></td>
      </tr>
  </tbody>
</table>
<p>CWE-284&rsquo;s own <a href="https://cwe.mitre.org/data/definitions/284">definition page</a> (CWE 5.0) lists vulnerability mapping usage as &ldquo;DISCOURAGED&rdquo;, says the ID &ldquo;should not be used to map to real-world vulnerabilities&rdquo;, and calls it &ldquo;extremely high-level, a Pillar&rdquo; that is &ldquo;not useful for trend analysis&rdquo;. Most of those 3,334 (2,624) are Oracle records whose CNA entry is text only. CVE-2026-82997 is one, where CISA-ADP adds CWE-284 to a CNA entry that reads &ldquo;Easily exploitable vulnerability allows low privileged attacker with network access via T3, IIOP to compromise Service Delivery Platform.&rdquo; The pillar choice reflects how little the CNA text says, so treat these as &ldquo;access-control-ish, details unknown&rdquo;, not as evidence that access control is your top weakness class.</p>
<h2 id="a-parser-that-handles-all-four-cases">A parser that handles all four cases</h2>
<p>This Python 3 function (tested with Python 3.13 against the five records listed below, fetched from <code>raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/...</code>) returns the CWE set and where it came from:</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> re<span style="color:#f92672">,</span> sys
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span>CWE_RE <span style="color:#f92672">=</span> re<span style="color:#f92672">.</span>compile(<span style="color:#e6db74">r</span><span style="color:#e6db74">&#34;\bCWE-[1-9][0-9]*\b&#34;</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">cwe_ids</span>(record):
</span></span><span style="display:flex;"><span>    <span style="color:#e6db74">&#34;&#34;&#34;Return (ids, source) for one CVE JSON 5.x record.
</span></span></span><span style="display:flex;"><span><span style="color:#e6db74">    source: &#39;cna&#39;, &#39;cna-text&#39;, &#39;cisa-adp&#39; or &#39;none&#39;.&#34;&#34;&#34;</span>
</span></span><span style="display:flex;"><span>    c <span style="color:#f92672">=</span> record[<span style="color:#e6db74">&#34;containers&#34;</span>]
</span></span><span style="display:flex;"><span>    texts, ids <span style="color:#f92672">=</span> [], set()
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">for</span> pt <span style="color:#f92672">in</span> c[<span style="color:#e6db74">&#34;cna&#34;</span>]<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;problemTypes&#34;</span>, []):
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">for</span> d <span style="color:#f92672">in</span> pt<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;descriptions&#34;</span>, []):
</span></span><span style="display:flex;"><span>            <span style="color:#66d9ef">if</span> d<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;cweId&#34;</span>):
</span></span><span style="display:flex;"><span>                ids<span style="color:#f92672">.</span>add(d[<span style="color:#e6db74">&#34;cweId&#34;</span>])
</span></span><span style="display:flex;"><span>            <span style="color:#66d9ef">else</span>:
</span></span><span style="display:flex;"><span>                texts<span style="color:#f92672">.</span>append(d<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;description&#34;</span>, <span style="color:#e6db74">&#34;&#34;</span>))
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">if</span> ids:
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">return</span> sorted(ids), <span style="color:#e6db74">&#34;cna&#34;</span>
</span></span><span style="display:flex;"><span>    found <span style="color:#f92672">=</span> {m <span style="color:#66d9ef">for</span> t <span style="color:#f92672">in</span> texts <span style="color:#66d9ef">for</span> m <span style="color:#f92672">in</span> CWE_RE<span style="color:#f92672">.</span>findall(t)}
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">if</span> found:
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">return</span> sorted(found), <span style="color:#e6db74">&#34;cna-text&#34;</span>      <span style="color:#75715e"># CWE named in prose only</span>
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">for</span> adp <span style="color:#f92672">in</span> c<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:#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">continue</span>
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">for</span> pt <span style="color:#f92672">in</span> adp<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;problemTypes&#34;</span>, []):
</span></span><span style="display:flex;"><span>            <span style="color:#66d9ef">for</span> d <span style="color:#f92672">in</span> pt<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;descriptions&#34;</span>, []):
</span></span><span style="display:flex;"><span>                <span style="color:#66d9ef">if</span> d<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;cweId&#34;</span>):
</span></span><span style="display:flex;"><span>                    ids<span style="color:#f92672">.</span>add(d[<span style="color:#e6db74">&#34;cweId&#34;</span>])
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">return</span> (sorted(ids), <span style="color:#e6db74">&#34;cisa-adp&#34;</span>) <span style="color:#66d9ef">if</span> ids <span style="color:#66d9ef">else</span> ([], <span style="color:#e6db74">&#34;none&#34;</span>)
</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>    <span style="color:#66d9ef">for</span> path <span style="color:#f92672">in</span> sys<span style="color:#f92672">.</span>argv[<span style="color:#ae81ff">1</span>:]:
</span></span><span style="display:flex;"><span>        r <span style="color:#f92672">=</span> json<span style="color:#f92672">.</span>load(open(path))
</span></span><span style="display:flex;"><span>        print(r[<span style="color:#e6db74">&#34;cveMetadata&#34;</span>][<span style="color:#e6db74">&#34;cveId&#34;</span>], <span style="color:#f92672">*</span>cwe_ids(r))
</span></span></code></pre></div><p>Output on the November 15, 2026 versions of those records:</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-2905 [&#39;CWE-732&#39;] cna
</span></span><span style="display:flex;"><span>CVE-2024-3477 [&#39;CWE-352&#39;] cna-text
</span></span><span style="display:flex;"><span>CVE-2026-74687 [] none
</span></span><span style="display:flex;"><span>CVE-2026-82126 [&#39;CWE-284&#39;] cna-text
</span></span><span style="display:flex;"><span>CVE-2026-82997 [&#39;CWE-284&#39;] cisa-adp
</span></span></code></pre></div><p>Design choices, and their limits:</p>
<ul>
<li><strong>CNA text before CISA-ADP.</strong> The CNA is the authoritative source under the README&rsquo;s precedence rule, and in 2,544 of 2,591 overlapping cases the two agree anyway. Swap the order if you only trust structured fields.</li>
<li><strong>The regex can over-match.</strong> A description such as &ldquo;similar to CWE-79&rdquo; would be captured. In the corpus the prose-only CWE strings are overwhelmingly titles in the form &ldquo;CWE-NNN Name&rdquo;, but log <code>cna-text</code> results separately.</li>
<li><strong>Keep the source column.</strong> Store <code>source</code> with each row. It lets you report &ldquo;CNA-mapped&rdquo; and &ldquo;enriched&rdquo; weaknesses separately and lets you drop discouraged pillars from trend charts without losing the records.</li>
<li><strong>Re-read on updates.</strong> CISA-ADP values can disappear when a CNA adds its own. If you sync incrementally with <a href="/posts/cvelistv5-delta-json-deltalog-incremental-cve-sync/">cvelistV5 delta.json and deltaLog.json</a>, re-run the extractor on every updated record rather than caching the first answer.</li>
</ul>
<h2 id="common-mistakes">Common mistakes</h2>
<ul>
<li><strong>Reading <code>problemTypes[0].descriptions[0].cweId</code> only.</strong> 11.2% of records with CNA CWE data list more than one distinct CWE, and some put a text entry first.</li>
<li><strong>Assuming <code>type</code> tells you what you have.</strong> Lower-case <code>cwe</code>, missing <code>type</code> and <code>Impact</code> all occur.</li>
<li><strong>Treating &ldquo;no CWE&rdquo; as &ldquo;unknown vulnerability class&rdquo; for every vendor equally.</strong> Linux kernel and Mozilla records will always be in that bucket until those CNAs change practice.</li>
<li><strong>Merging CISA-ADP CWE-284 into a Top-N chart without a label.</strong> It becomes a top-three entry by volume in 2026 for reasons unrelated to the underlying bugs.</li>
<li><strong>Mixing CWE with severity signals.</strong> CWE says what kind of bug it is, not how urgent it is. Severity and exploitation come from <a href="/posts/cve-json-cvss-metrics-cvssv4-0-cvssv3-1-basescore-trap/">CVSS in the record</a>, <a href="/posts/cisa-vulnrichment-how-to-read-ssvc-values-in-a-cve-record-and-turn-them-into-a-patch-decision/">CISA&rsquo;s SSVC values</a> and KEV.</li>
</ul>
<h2 id="how-mitres-top-25-deals-with-the-same-data">How MITRE&rsquo;s Top 25 deals with the same data</h2>
<p>The <a href="https://cwe.mitre.org/top25/archive/2025/2025_methodology.html">2025 CWE Top 25 methodology</a> used 39,080 CVE records published between June 1, 2024 and June 1, 2025, including mappings &ldquo;added by CISA Vulnrichment after publication&rdquo;. About 9,468 (24%) were flagged for re-mapping review, for example where the CWE was too abstract or commonly misused. If you build an internal ranking from raw CVE data you get the unreviewed version of that dataset, so expect pillars and class-level CWEs to rank higher than they do in the published list.</p>
<h2 id="limits-of-this-article">Limits of this article</h2>
<ul>
<li>Counts come from one snapshot (the <code>cve_2026-11-15_0000Z</code> release) and change daily as records are published, updated and enriched.</li>
<li>Years are grouped by <code>datePublished</code>, not by CVE ID year.</li>
<li>We did not validate whether each CWE is the correct mapping for its vulnerability, only where it is recorded.</li>
<li>CWE usage notes are quoted from CWE 5.0 for CWE-284 only; check the definition page of any other CWE before excluding it.</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>problemTypes structure, cweId pattern, CNA required fields</td>
          <td><a href="https://github.com/CVEProject/cve-schema/blob/main/schema/CVE_Record_Format.json">CVE Record Format schema</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>CNA MUST identify vulnerability type; SHOULD use CWE (rule 5.1.7)</td>
          <td><a href="https://www.cve.org/Resources/Roles/Cnas/CNA_Rules_v4.1.0.pdf">CNA Operational Rules 4.1.0</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>CNA/ADP coverage counts, CNA patterns, CISA-ADP gap-fill counts</td>
          <td>cvelistV5 release <code>cve_2026-11-15_0000Z</code>, counted with Python</td>
          <td>Verified (our count)</td>
      </tr>
      <tr>
          <td>CISA-ADP adds CWE for some CVEs, never overwrites CNA, drops on CNA update, CNA precedence</td>
          <td><a href="https://github.com/cisagov/vulnrichment">cisagov/vulnrichment README</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>CWE-284 is a Pillar with mapping usage DISCOURAGED</td>
          <td><a href="https://cwe.mitre.org/data/definitions/284">CWE-284 definition</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>Top 25 2025 dataset size, window and re-mapping share</td>
          <td><a href="https://cwe.mitre.org/top25/archive/2025/2025_methodology.html">2025 CWE Top 25 methodology</a></td>
          <td>Verified</td>
      </tr>
  </tbody>
</table>
]]></content:encoded></item></channel></rss>