<?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 | FirewallSync</title><link>https://firewallsync.com/tags/cisa/</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/cisa/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><item><title>Supermarket Freezer Hacks: What the CISA-FBI Warning Says</title><link>https://firewallsync.com/posts/supermarket-freezer-hacks-refrigeration-controllers-cisa-fbi-warning/</link><guid>https://firewallsync.com/posts/supermarket-freezer-hacks-refrigeration-controllers-cisa-fbi-warning/</guid><pubDate>Mon, 09 Nov 2026 04:56:00 +0000</pubDate><dc:creator>Craig Leslie</dc:creator><category>Security Operations</category><description>Attackers remotely switched supermarket freezers to heating in hundreds of French stores in October and in Belgium, Sweden, Estonia and other countries on November 2. On November 5 CISA, the FBI and three other US agencies told operators to pull refrigeration controllers off the internet. What is confirmed, what is not, and what to check.</description><enclosure url="https://firewallsync.com/posts/supermarket-freezer-hacks-refrigeration-controllers-cisa-fbi-warning/cover_hu16031666883070386899.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/supermarket-freezer-hacks-refrigeration-controllers-cisa-fbi-warning/cover_hu16031666883070386899.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/supermarket-freezer-hacks-refrigeration-controllers-cisa-fbi-warning/cover_hu16031666883070386899.jpg" alt="Close-up of feathery frost crystals spreading across a pale blue frozen window pane" width="1200" height="630"></p><p>Attackers have twice switched supermarket freezers into heaters across Europe. In the first wave, around October 11-12, 2026, refrigeration controllers in hundreds of French supermarkets were remotely pushed into heating and defrost cycles. On November 2 a second wave hit stores in Belgium, Sweden, Luxembourg, Estonia and the Netherlands, with Swedish stores reporting freezers set to 50°C. On November 5, CISA, the FBI and three other US agencies published a joint warning telling operators to take refrigeration controllers off the internet.</p>
<p>Nobody has claimed the attacks, and the way in has not been confirmed. The defensive lesson is clear anyway: these are internet-reachable OT devices, often past end of support, controlling equipment whose failure costs money within hours.</p>
<h2 id="what-happened">What happened</h2>
<p>The <a href="https://bleepingcomputer.com/news/security/cyberattack-shuts-down-refrigerators-at-french-supermarkets">BleepingComputer report of October 12</a> said attackers hijacked controllers on the Sunday night and used them to raise temperatures by triggering the built-in automatic defrost. Citing French outlets, it put the impact at 250 to 350 stores across chains including Intermarché, Coopérative U, Carrefour Market, Monoprix and Leclerc. Coopérative U&rsquo;s president called it &ldquo;an extremely serious matter and is unprecedented&rdquo;, and the Paris prosecutor&rsquo;s office opened an investigation into &ldquo;the large-scale cyberattack affecting the refrigerators of several major food retail chains across France&rdquo;, according to AFP as quoted by BleepingComputer.</p>
<p>The second wave came in the early hours of Monday, November 2. <a href="https://therecord.media/cyberattack-grocery-freezers-europe">The Record</a> quoted a Swedish store manager: &ldquo;We can&rsquo;t adjust the temperatures, we can&rsquo;t change them. Heat is blowing into the freezers. Everything is ruined.&rdquo; Retailers confirmed affected stores to <a href="https://www.itv.com/news/2026-11-02/freezers-at-supermarkets-across-europe-hit-by-apparent-cyberattacks">AP, as published by ITV</a>: Delhaize said several dozen stores, mostly in Belgium; Carrefour Belgium said 15 of its more than 700 stores, with &ldquo;an extremely limited impact&rdquo;; ICA said &ldquo;a limited number&rdquo; of Swedish stores.</p>
<h2 id="timeline">Timeline</h2>
<table>
  <thead>
      <tr>
          <th>Date (2026)</th>
          <th>Event</th>
          <th>Source</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Oct 11-12</td>
          <td>Refrigeration controllers in French supermarkets switched to heating/defrost; 250-350 stores reported</td>
          <td>BleepingComputer, citing French outlets</td>
      </tr>
      <tr>
          <td>By Oct 12</td>
          <td>Paris prosecutor opens an investigation</td>
          <td>AFP via BleepingComputer</td>
      </tr>
      <tr>
          <td>Nov 2</td>
          <td>Second wave: Belgium, Sweden, Luxembourg, Estonia, Netherlands, Ireland</td>
          <td>The Record; AP via ITV</td>
      </tr>
      <tr>
          <td>Nov 2</td>
          <td>Belgium&rsquo;s Centre for Cybersecurity (CCB) says it is aware but cannot identify the actor</td>
          <td>The Record</td>
      </tr>
      <tr>
          <td>Nov 5</td>
          <td>CISA, FBI, HHS, USDA and DoT publish a joint hardening warning</td>
          <td><a href="https://www.ic3.gov/CSA/2026/261105.pdf">Joint advisory (IC3 PDF)</a></td>
      </tr>
  </tbody>
</table>
<h2 id="confirmed-vs-not-confirmed">Confirmed vs not confirmed</h2>
<table>
  <thead>
      <tr>
          <th>Claim</th>
          <th>Status</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Refrigeration controllers in French stores were remotely manipulated in October</td>
          <td>Confirmed by retailers and a criminal investigation</td>
      </tr>
      <tr>
          <td>Around 700 victims in the French attack</td>
          <td>Attributed: the Paris prosecutor&rsquo;s office, as reported by The Record</td>
      </tr>
      <tr>
          <td>Stores hit on Nov 2 in Belgium (Delhaize, Carrefour), Sweden (ICA, Coop), Estonia (Selver)</td>
          <td>Confirmed by the retailers to AP; Coop&rsquo;s six stores per Swedish news agency TT</td>
      </tr>
      <tr>
          <td>More than 50 Belgian stores affected</td>
          <td>Attributed: The Record</td>
      </tr>
      <tr>
          <td>Danfoss equipment involved</td>
          <td>Reported: older Danfoss controllers in France (BleepingComputer) and an &ldquo;older Danfoss system&rdquo; in Estonia (a contractor, per The Record)</td>
      </tr>
      <tr>
          <td>Copeland equipment involved</td>
          <td>Reported by Dutch broadcaster NOS, per The Record</td>
      </tr>
      <tr>
          <td>How attackers got in</td>
          <td>Not confirmed. The Record says the French attack compromised internet-exposed remote controllers; no source has published the method for Nov 2</td>
      </tr>
      <tr>
          <td>A specific CVE was exploited</td>
          <td>Not confirmed by any source</td>
      </tr>
      <tr>
          <td>Who did it</td>
          <td>Not claimed and not attributed. Not known whether one actor carried out both waves</td>
      </tr>
      <tr>
          <td>Later incidents in Germany, Italy, Portugal and Romania, and EU emergency meetings</td>
          <td>Reported by <a href="https://www.latintimes.com/eu-emergency-meetings-supermarket-refrigeration-cyberattacks-600921">Latin Times</a>; we have not confirmed these with primary sources</td>
      </tr>
  </tbody>
</table>
<h2 id="what-the-vendors-said">What the vendors said</h2>
<p>According to The Record, both Danfoss and Copeland said after the French attack that the affected devices were mainly discontinued products that no longer received security updates. Stephan Moelans, CEO of the Belgian installer Sabcobel, said he knew of about 20 affected units out of hundreds his company manages, and that they need physical modifications, not just a software update. The Record also cites an earlier Danfoss newsletter saying stores hacked in Israel lacked adequate firewall or VPN protection.</p>
<h2 id="what-the-us-agencies-said">What the US agencies said</h2>
<p>The <a href="https://www.ic3.gov/CSA/2026/261105.pdf">joint document</a>, titled &ldquo;US Government Partners Urge Hardening Industrial Refrigeration and Cold Chain Monitoring Systems&rdquo;, is dated November 5, 2026. It says the agencies are aware of malicious activity targeting &ldquo;electronic temperature controllers and commercial refrigeration controllers&rdquo; in retail grocery and cold storage, across healthcare, chemical, food and agriculture, and transportation. Actors may exploit &ldquo;unpatched or internet-accessible controllers&rdquo; to &ldquo;remotely alter settings and force units into continuous heating and defrost cycles&rdquo;, using authentication bypass, arbitrary code injection and weak configurations. It also warns of &ldquo;denial-of-view&rdquo;, where operators lose sight of real temperatures.</p>
<p>It names no vendor, product, port or CVE. Its eight mitigations, each mapped to CISA&rsquo;s Cross-Sector Cybersecurity Performance Goals:</p>
<ol>
<li>Do not expose controller panels to the internet; put any needed remote access behind an up-to-date firewall or edge device.</li>
<li>Put OT devices on a dedicated VLAN separate from business networks.</li>
<li>Change default passwords, enforce strong passwords, and use phishing-resistant MFA where feasible.</li>
<li>Keep firmware current, and retire end-of-life devices the manufacturer no longer supports.</li>
<li>Allowlist the devices and IP addresses allowed to make changes.</li>
<li>Keep tested offline and offsite backups.</li>
<li>Enable and review logs; where OT logging is poor, capture network traffic between assets.</li>
<li>Define reasonable setpoint ranges and alert on deviations.</li>
</ol>
<h2 id="the-known-danfoss-cves">The known Danfoss CVEs</h2>
<p>No source has tied these attacks to a specific vulnerability. Two published flaws in Danfoss AK-SM 8xxA store controllers are still worth checking if you run that line. From the <a href="https://github.com/CVEProject/cvelistV5">CVE records</a> published by Danfoss as CNA:</p>
<table>
  <thead>
      <tr>
          <th>CVE</th>
          <th>Weakness</th>
          <th>Affected</th>
          <th>Score in record</th>
          <th>CISA-ADP SSVC</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>CVE-2025-41450</td>
          <td>Authentication bypass with privileged access</td>
          <td>AK-SM 8xxA Series before 4.2</td>
          <td>CVSS 3.1 8.2</td>
          <td>Exploitation: poc; Automatable: no</td>
      </tr>
      <tr>
          <td>CVE-2025-41451</td>
          <td>Post-authentication OS command injection via alarm-to-mail configuration fields</td>
          <td>AK-SM8xxA Series before 4.3.1</td>
          <td>CVSS 4.0 8.7</td>
          <td>Exploitation: poc; Automatable: no</td>
      </tr>
  </tbody>
</table>
<p>Neither is in CISA&rsquo;s KEV catalog (version 2026.11.06), and CISA&rsquo;s enrichment still records proof-of-concept rather than active exploitation. That is consistent with what is public: real attacks on refrigeration controllers, but no confirmed link to these CVEs. Our guides to <a href="/posts/cisa-kev-json-feed-what-each-field-means-and-how-to-match-it-against-a-scanner-export/">the KEV JSON feed</a> and <a href="/posts/cisa-vulnrichment-how-to-read-ssvc-values-in-a-cve-record-and-turn-them-into-a-patch-decision/">reading SSVC values in a CVE record</a> show how to alert when either changes.</p>
<h2 id="what-engineers-should-check">What engineers should check</h2>
<p>Retail is the headline, but the joint warning also names healthcare, chemical and transportation cold chains. If your organisation runs refrigeration, HVAC or building-management controllers, or your IT team supports sites that do:</p>
<ul>
<li><strong>Find them from the outside.</strong> Scan your own public IP ranges and check your external attack surface tool for controller web interfaces. Contractors and installers often add remote access without IT knowing; ask them for a list.</li>
<li><strong>Remove direct exposure.</strong> Put remote access behind a VPN or managed gateway with MFA, and allowlist the installer&rsquo;s addresses. Treat a controller panel reachable from the internet as an incident to close today.</li>
<li><strong>Check firmware against the vendor&rsquo;s advisories</strong>, including the AK-SM 8xxA versions above if you run them. Where the vendor says the model is discontinued, plan replacement: the vendors say affected devices were mainly discontinued, and the installer quoted above says some units need physical modifications, not just a software update.</li>
<li><strong>Change default and shared passwords</strong>, especially those set at installation and shared across stores.</li>
<li><strong>Alert on setpoint and defrost-schedule changes</strong>, and set hard limits where the controller supports them.</li>
<li><strong>Keep an independent temperature alarm.</strong> A separate sensor and alerting path is what tells you a freezer is warming when the controller&rsquo;s own display has been altered.</li>
<li><strong>Write the runbook now:</strong> who can go on site to switch units to local or manual control, and how stock decisions get made.</li>
</ul>
<h2 id="limits-of-this-article">Limits of this article</h2>
<p>This is a fast-moving incident. Store counts come from retailers and press reports and differ between outlets. We have not seen technical indicators, a vendor incident report or an official account of initial access. We will add a dated update if a vendor, CERT or prosecutor publishes the method or an attribution.</p>
<h2 id="sources-and-verification">Sources and verification</h2>
<table>
  <thead>
      <tr>
          <th>Important claim</th>
          <th>Source</th>
          <th>Status</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Joint warning text, date, co-sealing agencies and eight mitigations</td>
          <td><a href="https://www.ic3.gov/CSA/2026/261105.pdf">CISA/FBI/HHS/USDA/DoT joint document (IC3)</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>French wave: timing, 250-350 stores, chains, prosecutor investigation</td>
          <td><a href="https://bleepingcomputer.com/news/security/cyberattack-shuts-down-refrigerators-at-french-supermarkets">BleepingComputer, Oct 12, 2026</a></td>
          <td>Qualified (press, citing French outlets and AFP)</td>
      </tr>
      <tr>
          <td>Nov 2 wave: countries, quotes, CCB statement, Sabcobel, Danfoss/Copeland statements, ~700 French victims</td>
          <td><a href="https://therecord.media/cyberattack-grocery-freezers-europe">The Record, Nov 2, 2026</a></td>
          <td>Qualified (press)</td>
      </tr>
      <tr>
          <td>Retailer confirmations: Delhaize, Carrefour Belgium, ICA, Coop, Selver</td>
          <td><a href="https://www.itv.com/news/2026-11-02/freezers-at-supermarkets-across-europe-hit-by-apparent-cyberattacks">AP via ITV, Nov 2, 2026</a></td>
          <td>Verified (company statements quoted)</td>
      </tr>
      <tr>
          <td>Later incidents and EU meetings</td>
          <td><a href="https://www.latintimes.com/eu-emergency-meetings-supermarket-refrigeration-cyberattacks-600921">Latin Times</a></td>
          <td>Not confirmed; listed as reported</td>
      </tr>
      <tr>
          <td>CVE-2025-41450 and CVE-2025-41451 details and SSVC</td>
          <td><a href="https://github.com/CVEProject/cvelistV5">cvelistV5 records</a></td>
          <td>Verified (data)</td>
      </tr>
      <tr>
          <td>Neither CVE in KEV</td>
          <td><a href="https://github.com/cisagov/kev-data">cisagov/kev-data</a>, catalog 2026.11.06</td>
          <td>Verified (data)</td>
      </tr>
  </tbody>
</table>
]]></content:encoded></item></channel></rss>