<?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>Proof of Concept | FirewallSync</title><link>https://firewallsync.com/tags/proof-of-concept/</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/proof-of-concept/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></channel></rss>