<?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>Kev-Data | FirewallSync</title><link>https://firewallsync.com/tags/kev-data/</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>Wed, 18 Nov 2026 04:58:00 +0000</lastBuildDate><atom:link href="https://firewallsync.com/tags/kev-data/index.xml" rel="self" type="application/rss+xml"/><item><title>KEV dueDate: 3, 14 or 21 Days After dateAdded, 2021-2026</title><link>https://firewallsync.com/posts/kev-duedate-days-after-dateadded-3-14-21-day-deadlines/</link><guid>https://firewallsync.com/posts/kev-duedate-days-after-dateadded-3-14-21-day-deadlines/</guid><pubDate>Wed, 18 Nov 2026 04:58:00 +0000</pubDate><dc:creator>John Marshall</dc:creator><category>Security Operations</category><description>We measured dueDate minus dateAdded for all 1,782 entries in CISA's KEV catalog (version 2026.11.17) and replayed the cisagov/kev-data history to find every dueDate CISA edited after publication. The default gap was 14 days in 2021, 21 days from March 2022, and since mid-2026 is 3 or 14 days. Every forensicTriage Yes entry is due in 3 days, but 23 No entries are too.</description><enclosure url="https://firewallsync.com/posts/kev-duedate-days-after-dateadded-3-14-21-day-deadlines/cover_hu5441541435602915000.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/kev-duedate-days-after-dateadded-3-14-21-day-deadlines/cover_hu5441541435602915000.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/kev-duedate-days-after-dateadded-3-14-21-day-deadlines/cover_hu5441541435602915000.jpg" alt="A wall calendar page for December 2020 in four languages, with week numbers down the left and weekend dates in grey and red" width="1200" height="630"></p><p><strong>Short answer:</strong> the KEV catalog&rsquo;s <code>dueDate</code> is a calendar date, set per entry, and the gap to <code>dateAdded</code> has changed three times. In the current catalog (version 2026.11.17, 1,782 entries) every entry added since June 10, 2026 is due <strong>3 or 14 days</strong> after it was added. Before that, from March 2022 until early March 2026, the usual gap was <strong>21 days</strong>. If you build SLAs from KEV, read <code>dueDate</code> from every catalog sync rather than hard-coding a number of days, because CISA also edits due dates after publishing them.</p>
<p>This article measures the field. For what each KEV field means, see 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>. For what BOD 26-04 requires of federal agencies, see <a href="/posts/cisa-bod-26-04-explained-kev-deadlines-forensic-triage-and-what-private-teams-can-borrow/">CISA BOD 26-04 explained</a>. For where KEV fits in a patch decision, see the <a href="/posts/vulnerability-prioritization-workflow-cve-record-to-patch-ticket/">vulnerability prioritization workflow</a>.</p>
<h2 id="what-the-field-is">What the field is</h2>
<p>The catalog schema in <a href="https://github.com/cisagov/kev-data">cisagov/kev-data</a> describes <code>dueDate</code> as &ldquo;The date the required action is due in the format YYYY-MM-DD&rdquo;. It is required on every entry. A second field, <code>forensicTriage</code>, is described as &ldquo;&lsquo;Yes&rsquo; if this vulnerability requires forensic triage per BOD 26-04; &lsquo;No&rsquo; if forensic triage is not required per BOD 26-04&rdquo;. That field first appears in the catalog published on September 1, 2026, when it was filled in for all entries then listed (38 Yes, 1,649 No).</p>
<p>Neither field states the number of days. To get it, subtract <code>dateAdded</code> from <code>dueDate</code>.</p>
<h2 id="gap-by-year-added">Gap by year added</h2>
<p>We computed <code>dueDate − dateAdded</code> in days for all 1,782 entries in catalog version 2026.11.17 (released 2026-11-17T17:53Z). The three most common gaps per year:</p>
<table>
  <thead>
      <tr>
          <th>Year added</th>
          <th>Entries</th>
          <th>Most common gaps (days: entries)</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>2021</td>
          <td>311</td>
          <td>181: 189 · 14: 111 · 182: 11</td>
      </tr>
      <tr>
          <td>2022</td>
          <td>555</td>
          <td>21: 403 · 14: 88 · 181: 49</td>
      </tr>
      <tr>
          <td>2023</td>
          <td>187</td>
          <td>21: 177 · 4: 7 · 7: 1</td>
      </tr>
      <tr>
          <td>2024</td>
          <td>186</td>
          <td>21: 175 · 7: 7 · 12: 2</td>
      </tr>
      <tr>
          <td>2025</td>
          <td>245</td>
          <td>21: 226 · 7: 12 · 1: 6</td>
      </tr>
      <tr>
          <td>2026</td>
          <td>298</td>
          <td>3: 159 · 14: 92 · 21: 44</td>
      </tr>
  </tbody>
</table>
<p>Three regimes are visible:</p>
<ol>
<li><strong>2021 to early 2022: two weeks or six months.</strong> <a href="https://www.cisa.gov/binding-operational-directive-22-01">BOD 22-01</a> told agencies to remediate &ldquo;within 6 months for vulnerabilities with a Common Vulnerabilities and Exposures (CVE) ID assigned prior to 2021&rdquo; and &ldquo;within two weeks for all other vulnerabilities&rdquo;, and added: &ldquo;These default timelines may be adjusted in the case of grave risk to the Federal Enterprise.&rdquo; The 2021 data follows that split: 179 of the 2021 entries with pre-2021 CVE IDs have a 181-day gap and 11 have 182; 110 entries with 2021 CVE IDs have 14 days.</li>
<li><strong>March 2022 to March 2026: 21 days.</strong> The first 21-day entry was added on 2022-03-03 and the last on 2026-03-05. The last six-month entry was added on 2022-03-07 and the last 2022 entry with 14 days on 2022-06-08. We did not find a CISA statement explaining the switch from two weeks to 21 days, so we report it only as what the data shows.</li>
<li><strong>2026: 3 and 14 days.</strong> The first 3-day entry was added on 2026-01-27 (Fortinet, CVE-2026-24858), months before BOD 26-04 was published on June 10, 2026. The first 14-day entry in this regime was added on 2026-03-09. Since June 10, 2026 no other gap appears.</li>
</ol>
<p>Short one-off gaps exist outside those patterns, for example six 1-day entries added in 2025 and two 2-day Cisco entries (CVE-2022-20775 and CVE-2026-20127) added on 2026-02-25.</p>
<h2 id="since-bod-26-04-3-or-14-days-and-what-forensictriage-tells-you">Since BOD 26-04: 3 or 14 days, and what forensicTriage tells you</h2>
<p>For the 165 entries added on or after June 10, 2026:</p>
<table>
  <thead>
      <tr>
          <th>Gap</th>
          <th>forensicTriage</th>
          <th>Entries</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>3 days</td>
          <td>Yes</td>
          <td>105</td>
      </tr>
      <tr>
          <td>3 days</td>
          <td>No</td>
          <td>23</td>
      </tr>
      <tr>
          <td>14 days</td>
          <td>No</td>
          <td>37</td>
      </tr>
  </tbody>
</table>
<p>Every Yes entry is due in 3 days. But a No does not mean 14 days: 23 No entries are due in 3 days too, including CVE-2015-5477 (BIND) from the October 8, 2026 batch our BOD 26-04 article examined.</p>
<p>We also joined these 165 entries to their CVE records in <a href="https://github.com/CVEProject/cvelistV5">CVEProject/cvelistV5</a> and read the CISA-ADP SSVC &ldquo;Technical Impact&rdquo; option:</p>
<table>
  <thead>
      <tr>
          <th>Gap</th>
          <th>forensicTriage</th>
          <th>Technical Impact total</th>
          <th>Technical Impact partial</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>3 days</td>
          <td>Yes</td>
          <td>104</td>
          <td>1</td>
      </tr>
      <tr>
          <td>3 days</td>
          <td>No</td>
          <td>13</td>
          <td>10</td>
      </tr>
      <tr>
          <td>14 days</td>
          <td>No</td>
          <td>19</td>
          <td>18</td>
      </tr>
  </tbody>
</table>
<p>Under BOD 26-04 the agency timeline depends on KEV status, public exposure, automatability and technical impact for the specific asset, and the catalog publishes one date per CVE. Because 19 &ldquo;total&rdquo; entries got 14 days and 10 &ldquo;partial&rdquo; entries got 3, you cannot rebuild the catalog&rsquo;s <code>dueDate</code> from the SSVC values in the CVE record. Treat <code>dueDate</code> as CISA&rsquo;s published decision for that CVE and copy it as is. (The SSVC fields themselves are explained in <a href="/posts/cisa-vulnrichment-how-to-read-ssvc-values-in-a-cve-record-and-turn-them-into-a-patch-decision/">our Vulnrichment SSVC guide</a>.)</p>
<h3 id="weekends-count">Weekends count</h3>
<p>The gap is in calendar days. Of the 165 due dates since June 10, 2026, 26 fall on a Saturday and 23 on a Sunday, and 44 on a Friday. An internal SLA of &ldquo;3 business days from KEV listing&rdquo; will often land after the catalog date.</p>
<h2 id="cisa-edits-due-dates-after-publishing">CISA edits due dates after publishing</h2>
<p>The <a href="https://github.com/cisagov/kev-data">kev-data</a> repository keeps every catalog version since January 27, 2025 (345 commits to the JSON file when we checked). Replaying them and comparing each entry&rsquo;s <code>dateAdded</code>, <code>dueDate</code> and <code>forensicTriage</code> between consecutive versions found these changes, apart from the one-time September 1, 2026 backfill of <code>forensicTriage</code>:</p>
<table>
  <thead>
      <tr>
          <th>Catalog version</th>
          <th>CVE</th>
          <th>Change</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>2025.02.18</td>
          <td>CVE-2025-0108 (PAN-OS)</td>
          <td>dueDate 2025-04-08 → 2025-03-11</td>
      </tr>
      <tr>
          <td>2025.04.29</td>
          <td>CVE-2025-3928 (Commvault)</td>
          <td>dueDate 2025-05-17 → 2025-05-19</td>
      </tr>
      <tr>
          <td>2025.10.06</td>
          <td>CVE-2025-61882</td>
          <td>dateAdded and dueDate each moved one day earlier</td>
      </tr>
      <tr>
          <td>2025.10.15</td>
          <td>CVE-2025-54253</td>
          <td>dateAdded and dueDate each moved one day earlier</td>
      </tr>
      <tr>
          <td>2025.12.09</td>
          <td>CVE-2025-55182 (React Server Components)</td>
          <td>dueDate 2025-12-26 → 2025-12-12</td>
      </tr>
      <tr>
          <td>2025.12.17</td>
          <td>15 entries added 2021-11-03</td>
          <td>dueDate corrected to 2022-05-03 (previously earlier than dateAdded)</td>
      </tr>
      <tr>
          <td>2026.05.20</td>
          <td>CVE-2010-0249 (Internet Explorer)</td>
          <td>dateAdded 2026-06-03 → 2026-05-20, dueDate unchanged</td>
      </tr>
      <tr>
          <td>2026.08.17</td>
          <td>CVE-2025-62593</td>
          <td>dateAdded and dueDate each moved one day earlier</td>
      </tr>
      <tr>
          <td>2026.10.08</td>
          <td>CVE-2026-86950 (Apple)</td>
          <td>forensicTriage Yes → No, dueDate 2026-10-02 → 2026-10-13</td>
      </tr>
      <tr>
          <td>2026.10.08</td>
          <td>CVE-2022-0995 (Linux kernel)</td>
          <td>forensicTriage No → Yes, dueDate 2026-09-09 → 2026-08-29</td>
      </tr>
      <tr>
          <td>2026.10.08</td>
          <td>CVE-2026-88779 (NetScaler), CVE-2023-22894 (Strapi)</td>
          <td>forensicTriage flipped, dueDate unchanged</td>
      </tr>
      <tr>
          <td>2026.10.13</td>
          <td>CVE-2026-12569 (PTC Windchill)</td>
          <td>forensicTriage No → Yes, dueDate unchanged</td>
      </tr>
  </tbody>
</table>
<p>That is 23 <code>dueDate</code> changes in total. Two cases matter most for automation:</p>
<ul>
<li><strong>Shortened deadlines.</strong> CVE-2025-0108 lost four weeks and CVE-2025-55182 lost two. A ticket created from the first catalog version would show the wrong date.</li>
<li><strong>Retroactive deadlines.</strong> CVE-2022-0995&rsquo;s new dueDate (2026-08-29) was published on October 8, 2026, so the entry went straight to overdue. If your pipeline only reads new entries, it never sees this.</li>
</ul>
<p>Our <a href="/posts/kev-time-to-listing-cve-published-to-dateadded-days-by-vendor/">KEV time-to-listing analysis</a> covers the other end of the timeline: how long CVEs wait before <code>dateAdded</code>.</p>
<h2 id="run-it-yourself">Run it yourself</h2>
<p>Tested with Python 3 (standard library only) against <code>known_exploited_vulnerabilities.json</code> downloaded from <code>raw.githubusercontent.com/cisagov/kev-data/main/</code> on November 18, 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-python" data-lang="python"><span style="display:flex;"><span><span style="color:#f92672">import</span> json<span style="color:#f92672">,</span> sys<span style="color:#f92672">,</span> collections
</span></span><span style="display:flex;"><span><span style="color:#f92672">from</span> datetime <span style="color:#f92672">import</span> date
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span>kev <span style="color:#f92672">=</span> json<span style="color:#f92672">.</span>load(open(sys<span style="color:#f92672">.</span>argv[<span style="color:#ae81ff">1</span>]))
</span></span><span style="display:flex;"><span>print(<span style="color:#e6db74">&#34;catalogVersion&#34;</span>, kev[<span style="color:#e6db74">&#34;catalogVersion&#34;</span>], <span style="color:#e6db74">&#34;count&#34;</span>, kev[<span style="color:#e6db74">&#34;count&#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">days</span>(v):
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">return</span> (date<span style="color:#f92672">.</span>fromisoformat(v[<span style="color:#e6db74">&#34;dueDate&#34;</span>]) <span style="color:#f92672">-</span> date<span style="color:#f92672">.</span>fromisoformat(v[<span style="color:#e6db74">&#34;dateAdded&#34;</span>]))<span style="color:#f92672">.</span>days
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span>by_year <span style="color:#f92672">=</span> collections<span style="color:#f92672">.</span>defaultdict(collections<span style="color:#f92672">.</span>Counter)
</span></span><span style="display:flex;"><span><span style="color:#66d9ef">for</span> v <span style="color:#f92672">in</span> kev[<span style="color:#e6db74">&#34;vulnerabilities&#34;</span>]:
</span></span><span style="display:flex;"><span>    by_year[v[<span style="color:#e6db74">&#34;dateAdded&#34;</span>][:<span style="color:#ae81ff">4</span>]][days(v)] <span style="color:#f92672">+=</span> <span style="color:#ae81ff">1</span>
</span></span><span style="display:flex;"><span><span style="color:#66d9ef">for</span> year <span style="color:#f92672">in</span> sorted(by_year):
</span></span><span style="display:flex;"><span>    c <span style="color:#f92672">=</span> by_year[year]
</span></span><span style="display:flex;"><span>    print(year, sum(c<span style="color:#f92672">.</span>values()), c<span style="color:#f92672">.</span>most_common(<span style="color:#ae81ff">4</span>))
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span><span style="color:#75715e"># Entries added from a given date: interval vs forensicTriage</span>
</span></span><span style="display:flex;"><span>since <span style="color:#f92672">=</span> sys<span style="color:#f92672">.</span>argv[<span style="color:#ae81ff">2</span>] <span style="color:#66d9ef">if</span> len(sys<span style="color:#f92672">.</span>argv) <span style="color:#f92672">&gt;</span> <span style="color:#ae81ff">2</span> <span style="color:#66d9ef">else</span> <span style="color:#e6db74">&#34;2026-06-10&#34;</span>
</span></span><span style="display:flex;"><span>pairs <span style="color:#f92672">=</span> collections<span style="color:#f92672">.</span>Counter(
</span></span><span style="display:flex;"><span>    (days(v), v<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;forensicTriage&#34;</span>))
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">for</span> v <span style="color:#f92672">in</span> kev[<span style="color:#e6db74">&#34;vulnerabilities&#34;</span>] <span style="color:#66d9ef">if</span> v[<span style="color:#e6db74">&#34;dateAdded&#34;</span>] <span style="color:#f92672">&gt;=</span> since)
</span></span><span style="display:flex;"><span>print(<span style="color:#e6db74">&#34;since&#34;</span>, since, sorted(pairs<span style="color:#f92672">.</span>items()))
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span><span style="color:#75715e"># Open items: due today or later, and those due on a weekend</span>
</span></span><span style="display:flex;"><span>today <span style="color:#f92672">=</span> date<span style="color:#f92672">.</span>today()
</span></span><span style="display:flex;"><span><span style="color:#66d9ef">for</span> v <span style="color:#f92672">in</span> kev[<span style="color:#e6db74">&#34;vulnerabilities&#34;</span>]:
</span></span><span style="display:flex;"><span>    due <span style="color:#f92672">=</span> date<span style="color:#f92672">.</span>fromisoformat(v[<span style="color:#e6db74">&#34;dueDate&#34;</span>])
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">if</span> due <span style="color:#f92672">&gt;=</span> today:
</span></span><span style="display:flex;"><span>        flag <span style="color:#f92672">=</span> <span style="color:#e6db74">&#34; (weekend)&#34;</span> <span style="color:#66d9ef">if</span> due<span style="color:#f92672">.</span>weekday() <span style="color:#f92672">&gt;=</span> <span style="color:#ae81ff">5</span> <span style="color:#66d9ef">else</span> <span style="color:#e6db74">&#34;&#34;</span>
</span></span><span style="display:flex;"><span>        print(v[<span style="color:#e6db74">&#34;cveID&#34;</span>], v[<span style="color:#e6db74">&#34;dateAdded&#34;</span>], v[<span style="color:#e6db74">&#34;dueDate&#34;</span>], days(v), v<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;forensicTriage&#34;</span>), flag)
</span></span></code></pre></div><p>Run it as <code>python3 kev_due.py known_exploited_vulnerabilities.json</code>. On November 18, 2026 it printed seven entries still open, all with 14-day gaps, the latest CVE-2026-115731 due 2026-12-01.</p>
<p>To find edited due dates, clone <code>cisagov/kev-data</code> (about 3 MB), list commits with <code>git log --reverse -- known_exploited_vulnerabilities.json</code>, load each version with <code>git show &lt;commit&gt;:known_exploited_vulnerabilities.json</code>, and compare each CVE&rsquo;s <code>(dateAdded, dueDate, forensicTriage)</code> with the previous version.</p>
<h2 id="what-to-do-with-this">What to do with this</h2>
<ul>
<li><strong>Copy <code>dueDate</code> into the ticket and update it on every sync.</strong> Key the comparison on <code>cveID</code> across the whole catalog, not only on entries added since your last run.</li>
<li><strong>Alert on changes, not just additions.</strong> A shortened or past <code>dueDate</code> on an existing entry deserves the same page as a new entry.</li>
<li><strong>Do not derive the deadline</strong> from <code>forensicTriage</code>, SSVC Technical Impact or CVSS. In the current data none of them reproduces the catalog date.</li>
<li><strong>Count calendar days.</strong> Map the catalog date to your SLA directly instead of adding business days.</li>
<li><strong>If you are not a federal agency,</strong> the catalog date is a strong urgency signal, not your legal deadline. Our <a href="/posts/cvss-vs-epss-vs-kev-which-signal-should-decide-what-you-patch-first/">CVSS vs EPSS vs KEV comparison</a> covers how to weigh it.</li>
</ul>
<h2 id="limits-of-this-article">Limits of this article</h2>
<ul>
<li>Counts come from catalog version 2026.11.17 and the kev-data history from January 27, 2025 onward. Edits made before that date are not visible in the repository.</li>
<li><code>dueDate</code> in the catalog is one date per CVE. Federal agencies&rsquo; asset-level timelines under BOD 26-04 depend on exposure and other decision points the catalog does not carry; we did not re-verify the directive&rsquo;s Table 1 for this article.</li>
<li>We describe what the data shows about the 21-day period and the 2026 change; we found no CISA statement explaining either.</li>
<li>SSVC values were read from cvelistV5 records on November 18, 2026; CISA-ADP can update them after a CVE is added to KEV.</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>dueDate and forensicTriage field descriptions</td>
          <td><a href="https://github.com/cisagov/kev-data/blob/main/known_exploited_vulnerabilities_schema.json">kev-data schema</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>Gap counts by year and since June 10, 2026</td>
          <td><a href="https://github.com/cisagov/kev-data">KEV catalog JSON, version 2026.11.17</a> (script above)</td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>forensicTriage first published 2026-09-01 (38 Yes, 1,649 No)</td>
          <td>kev-data git history</td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>BOD 22-01 six-month / two-week defaults and grave-risk adjustment</td>
          <td><a href="https://www.cisa.gov/binding-operational-directive-22-01">CISA BOD 22-01</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>SSVC Technical Impact per entry</td>
          <td><a href="https://github.com/CVEProject/cvelistV5">CVEProject/cvelistV5</a> CISA-ADP containers</td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>23 dueDate edits since January 2025</td>
          <td>kev-data git history replay</td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>BOD 26-04 publication date June 10, 2026</td>
          <td><a href="https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk">CISA BOD 26-04</a>, via our <a href="/posts/cisa-bod-26-04-explained-kev-deadlines-forensic-triage-and-what-private-teams-can-borrow/">earlier article</a></td>
          <td>Qualified (page not re-fetched today)</td>
      </tr>
  </tbody>
</table>
]]></content:encoded></item></channel></rss>