<?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>Csaf 2.1 | FirewallSync</title><link>https://firewallsync.com/tags/csaf-2.1/</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>Sun, 22 Nov 2026 04:30:00 +0000</lastBuildDate><atom:link href="https://firewallsync.com/tags/csaf-2.1/index.xml" rel="self" type="application/rss+xml"/><item><title>CSAF 2.1 vs 2.0: Field Changes VEX Consumers Must Handle</title><link>https://firewallsync.com/posts/csaf-2-1-vs-2-0-what-changes-for-vex-consumers/</link><guid>https://firewallsync.com/posts/csaf-2-1-vs-2-0-what-changes-for-vex-consumers/</guid><pubDate>Sun, 22 Nov 2026 04:30:00 +0000</pubDate><dc:creator>Craig Leslie</dc:creator><category>AppSec &amp; APIs</category><description>CSAF 2.1 (Committee Specification 01, 9 November 2026) renames, moves and adds fields a CSAF 2.0 parser relies on: scores becomes metrics, relationships becomes product_paths, cwe becomes cwes, TLP:WHITE becomes TLP:CLEAR, and vendor_fix on a fixed product is now prohibited. Here is the field-by-field diff from the TC's own schemas, the provider-metadata.json transition paths, and a check you can run.</description><enclosure url="https://firewallsync.com/posts/csaf-2-1-vs-2-0-what-changes-for-vex-consumers/cover_hu11763692115389572607.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/csaf-2-1-vs-2-0-what-changes-for-vex-consumers/cover_hu11763692115389572607.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/csaf-2-1-vs-2-0-what-changes-for-vex-consumers/cover_hu11763692115389572607.jpg" alt="A tall stack of printed papers bristling with pink, orange, yellow and green sticky tabs on a desk" width="1200" height="630"></p><p><strong>Short answer:</strong> CSAF 2.1 is not a drop-in update. A CSAF 2.0 parser that reads <code>vulnerabilities[].scores</code>, <code>product_tree.relationships</code>, <code>cwe</code> or <code>release_date</code> will silently miss data in a 2.1 file, because each of those has been replaced. The 2.1 schema also only accepts <code>&quot;csaf_version&quot;: &quot;2.1&quot;</code>, so any parser that validates the version will reject the file before it gets that far.</p>
<p>This guide is for engineers who ingest vendor CSAF VEX or advisory files into a scanner, SBOM pipeline or ticketing flow. It lists what changed between the two official JSON schemas, how vendors are told to run both versions in parallel, and which tools read 2.1 today. Everything below comes from the <a href="https://github.com/oasis-tcs/csaf">OASIS CSAF TC repository</a> at commit <code>e8fdccc7</code> (18 November 2026). Where we ran code against those files, we say so.</p>
<p><strong>Status:</strong> The repository&rsquo;s rendered 2.1 prose is headed &ldquo;Committee Specification 01&rdquo; and dated 9 November 2026. That is a TC-approved stage, not yet an OASIS Standard, so text can still change. CSAF 2.0 remains the current standard.</p>
<h2 id="the-field-level-diff">The field-level diff</h2>
<p>We walked both schemas (<code>csaf_2.0/json_schema/csaf_json_schema.json</code> and <code>csaf_2.1/json_schema/csaf.json</code>) with a short Python script. It resolves <code>$ref</code>s and compares property names and enums at every path. These are the changes a consumer has to handle:</p>
<table>
  <thead>
      <tr>
          <th>CSAF 2.0 path</th>
          <th>CSAF 2.1 path</th>
          <th>What to change in your parser</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><code>document.csaf_version</code> enum <code>[&quot;2.0&quot;]</code></td>
          <td>const <code>&quot;2.1&quot;</code></td>
          <td>Branch on the version before parsing anything else</td>
      </tr>
      <tr>
          <td>no <code>$schema</code> property</td>
          <td>required, const <code>https://docs.oasis-open.org/csaf/csaf/v2.1/schema/csaf.json</code></td>
          <td>Use it to choose the schema to validate against</td>
      </tr>
      <tr>
          <td><code>vulnerabilities[].scores[]</code> (<code>cvss_v2</code>, <code>cvss_v3</code>, <code>products</code>)</td>
          <td><code>vulnerabilities[].metrics[]</code> (<code>content</code>, <code>products</code>, <code>source</code>)</td>
          <td>Read <code>content.cvss_v4</code>, <code>content.epss</code>, <code>content.ssvc_v2</code>, <code>content.qualitative_severity_rating</code> as well as v2/v3</td>
      </tr>
      <tr>
          <td><code>product_tree.relationships[]</code> (<code>product_reference</code>, <code>relates_to_product_reference</code>, <code>category</code>)</td>
          <td><code>product_tree.product_paths[]</code> (<code>beginning_product_reference</code>, <code>subpaths[].next_product_reference</code>, <code>subpaths[].category</code>)</td>
          <td>Rewrite product-ID resolution (see below)</td>
      </tr>
      <tr>
          <td><code>vulnerabilities[].cwe</code> (one object)</td>
          <td><code>vulnerabilities[].cwes[]</code> with <code>id</code>, <code>name</code>, <code>version</code></td>
          <td>Treat CWE as a list</td>
      </tr>
      <tr>
          <td><code>vulnerabilities[].release_date</code></td>
          <td><code>vulnerabilities[].disclosure_date</code></td>
          <td>Rename</td>
      </tr>
      <tr>
          <td><code>vulnerabilities[].involvements[]</code></td>
          <td><code>document.involvement</code> (<code>actions</code>, <code>entities</code>, <code>entity_groups</code>)</td>
          <td>Coordination history moves to document level</td>
      </tr>
      <tr>
          <td>—</td>
          <td><code>vulnerabilities[].first_known_exploitation_dates[]</code></td>
          <td>New exploitation signal per product</td>
      </tr>
      <tr>
          <td><code>product_status</code> (8 groups)</td>
          <td>adds <code>unknown</code></td>
          <td>Map it explicitly; don&rsquo;t let it fall through</td>
      </tr>
      <tr>
          <td>remediation <code>category</code> (5 values)</td>
          <td>adds <code>fix_planned</code>, <code>optional_patch</code></td>
          <td>Map both; see the next section</td>
      </tr>
      <tr>
          <td><code>document.distribution.tlp.label</code> incl. <code>WHITE</code></td>
          <td><code>CLEAR</code>, <code>AMBER+STRICT</code> added, <code>WHITE</code> removed</td>
          <td>TLP v2.0 labels</td>
      </tr>
      <tr>
          <td><code>document.publisher.contact_details</code> (string)</td>
          <td><code>document.publisher.contact</code> (<code>details</code>, <code>email</code>, <code>public_openpgp_key_url</code>, <code>url</code>)</td>
          <td>Rename and restructure</td>
      </tr>
      <tr>
          <td>branch <code>category</code> incl. <code>legacy</code></td>
          <td><code>legacy</code> removed, <code>platform</code> added</td>
          <td></td>
      </tr>
      <tr>
          <td>—</td>
          <td><code>x_extensions</code> at document, vulnerability and product level</td>
          <td>Ignore unknown extensions rather than failing</td>
      </tr>
  </tbody>
</table>
<p><code>document.notes</code>, <code>vulnerabilities[].notes</code> and <code>vulnerabilities[].ids</code> can now also carry <code>product_ids</code> and <code>group_ids</code>. A note or an ID can therefore apply to only some of the products in the file.</p>
<h3 id="product_paths-replaces-relationships">product_paths replaces relationships</h3>
<p>This matters most if you follow our <a href="/posts/csaf-vex-product-tree-product-status-purl-sbom-matching/">CSAF VEX product_tree guide</a> to resolve product IDs to purls. In 2.0, a relationship joined two references. The CS01 converter rules say how that maps to 2.1: &ldquo;The value of <code>product_reference</code> is set as the value of <code>beginning_product_reference</code>.&rdquo; The first <code>subpaths</code> item then gets the old <code>category</code> and takes <code>relates_to_product_reference</code> as its <code>next_product_reference</code>.</p>
<p>So the 2.0 relationship &ldquo;component X is <code>default_component_of</code> platform Y&rdquo; becomes a path that starts at X with one hop to Y. The new combined product ID still lives in <code>full_product_name.product_id</code>. In the TC&rsquo;s converted Red Hat example (<code>rhsa-2022_0011.json</code>), IDs such as <code>7Server-7.6.AUS:telnet-1:0.17-65.el7_6.x86_64</code> survive unchanged. Only the structure around them moves.</p>
<p>A 2.1 path can hold several subpaths, so one product path can describe a chain rather than a single pair.</p>
<h2 id="remediations-the-change-that-affects-tickets">Remediations: the change that affects tickets</h2>
<p>CSAF 2.1 adds two remediation categories. It also prohibits combinations that 2.0 allowed, and that is the change most likely to show up in your triage numbers.</p>
<p>The CS01 definitions:</p>
<ul>
<li><strong><code>optional_patch</code></strong>: a patch from the product&rsquo;s author whose &ldquo;application is not necessary, but might be desired by the user, e.g. to calm a security scanner&rdquo;. Unless noted otherwise, &ldquo;it is assumed that this does not change the state regarding the vulnerability.&rdquo;</li>
<li><strong><code>fix_planned</code></strong>: &ldquo;there is a fix for the vulnerability planned but not yet ready.&rdquo; The <code>details</code> field SHOULD give a date when customers can expect the fix.</li>
</ul>
<p>The spec adds a table of remediation categories and the product-status groups they may appear with. A mandatory test, 6.1.36 &ldquo;Contradicting Product Status Remediation Combination&rdquo;, enforces the prohibited cells. Among them:</p>
<table>
  <thead>
      <tr>
          <th>Remediation</th>
          <th>Not Affected</th>
          <th>Fixed</th>
          <th>Affected</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><code>vendor_fix</code></td>
          <td>prohibited</td>
          <td>prohibited</td>
          <td>allowed</td>
      </tr>
      <tr>
          <td><code>optional_patch</code></td>
          <td>allowed</td>
          <td>discouraged</td>
          <td>prohibited</td>
      </tr>
      <tr>
          <td><code>fix_planned</code></td>
          <td>discouraged</td>
          <td>prohibited</td>
          <td>allowed</td>
      </tr>
      <tr>
          <td><code>none_available</code></td>
          <td>prohibited</td>
          <td>prohibited</td>
          <td>allowed</td>
      </tr>
  </tbody>
</table>
<p>In plain terms, a 2.1 file can no longer say &ldquo;vendor fix&rdquo; against a product it also lists as fixed or not affected. A patch offered for a not-affected product has to be <code>optional_patch</code>. For a <a href="/posts/vex-explained-what-a-not-affected-statement-means-and-how-to-read-one/">VEX consumer</a>, that is useful: <code>optional_patch</code> on a <code>known_not_affected</code> product is a hygiene update, not a fix ticket.</p>
<p>Our <a href="/posts/csaf-vex-remediations-threats-category-product-ids-trivy/">CSAF remediations and threats post</a> covers the 2.0 categories and how they map to ticket actions. Under 2.1, add two rules:</p>
<ol>
<li><code>fix_planned</code> means &ldquo;affected, no fix yet&rdquo;. Open or keep the ticket, and record the date from <code>details</code>.</li>
<li><code>optional_patch</code> means &ldquo;no exposure change&rdquo;. Do not raise priority because of it.</li>
</ol>
<h3 id="what-the-converter-does-to-old-vendor_fix-entries">What the converter does to old vendor_fix entries</h3>
<p>The CS01 &ldquo;CSAF 2.0 to CSAF 2.1 Converter&rdquo; conformance clause sets the migration rules. Of a <code>vendor_fix</code> on a product in the Not Affected or Fixed group, it says the converter &ldquo;SHALL convert&rdquo; it &ldquo;into the category <code>optional_patch</code>&rdquo;. It turns <code>none_available</code> into <code>fix_planned</code> if the same product also has a <code>vendor_fix</code> with a future date or no date. And if a <code>csaf_security_advisory</code> can&rsquo;t be made valid under 2.1, the converter &ldquo;SHALL set the <code>category</code> value to <code>csaf_deprecated_security_advisory</code>&rdquo;. The spec says that profile &ldquo;matches the definition of profile &lsquo;Security Advisory&rsquo; in CSAF 2.0.&rdquo;</p>
<p>So expect to see <code>csaf_deprecated_security_advisory</code> in real feeds. Treat it as a 2.0-era advisory, not as a withdrawal. The TC&rsquo;s own examples show this. Three of the six converted non-VEX advisories in <code>csaf_2.1/examples/csaf/</code> (the Red Hat RHSA-2021:5186, 2021:5217 and 2022:0011 files) carry that category.</p>
<h2 id="a-check-you-can-run-schema-plus-test-6136">A check you can run: schema plus test 6.1.36</h2>
<p>We validated every 2.1 example in the TC repository offline against the CS01 schema. We used Python <code>jsonschema</code> 4.26 with a <code>referencing</code> registry that maps the FIRST CVSS and CERT/CC SSVC schema URLs to the copies in <code>csaf_2.1/referenced_schema/</code>. We also ran our own port of mandatory test 6.1.36. The port is illustrative: it covers that one test, not the full 2.1 test suite. Its core:</p>
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-python" data-lang="python"><span style="display:flex;"><span><span style="color:#75715e"># Port of CSAF 2.1 CS01 mandatory test 6.1.36 (illustrative; Python 3.13)</span>
</span></span><span style="display:flex;"><span>GROUP <span style="color:#f92672">=</span> {<span style="color:#e6db74">&#34;first_affected&#34;</span>: <span style="color:#e6db74">&#34;Affected&#34;</span>, <span style="color:#e6db74">&#34;known_affected&#34;</span>: <span style="color:#e6db74">&#34;Affected&#34;</span>, <span style="color:#e6db74">&#34;last_affected&#34;</span>: <span style="color:#e6db74">&#34;Affected&#34;</span>,
</span></span><span style="display:flex;"><span>         <span style="color:#e6db74">&#34;known_not_affected&#34;</span>: <span style="color:#e6db74">&#34;Not Affected&#34;</span>, <span style="color:#e6db74">&#34;first_fixed&#34;</span>: <span style="color:#e6db74">&#34;Fixed&#34;</span>, <span style="color:#e6db74">&#34;fixed&#34;</span>: <span style="color:#e6db74">&#34;Fixed&#34;</span>,
</span></span><span style="display:flex;"><span>         <span style="color:#e6db74">&#34;under_investigation&#34;</span>: <span style="color:#e6db74">&#34;Under Investigation&#34;</span>, <span style="color:#e6db74">&#34;unknown&#34;</span>: <span style="color:#e6db74">&#34;Unknown&#34;</span>, <span style="color:#e6db74">&#34;recommended&#34;</span>: <span style="color:#e6db74">&#34;Recommended&#34;</span>}
</span></span><span style="display:flex;"><span>PROHIBITED <span style="color:#f92672">=</span> {<span style="color:#e6db74">&#34;workaround&#34;</span>: {<span style="color:#e6db74">&#34;Not Affected&#34;</span>, <span style="color:#e6db74">&#34;Fixed&#34;</span>}, <span style="color:#e6db74">&#34;mitigation&#34;</span>: {<span style="color:#e6db74">&#34;Not Affected&#34;</span>, <span style="color:#e6db74">&#34;Fixed&#34;</span>},
</span></span><span style="display:flex;"><span>              <span style="color:#e6db74">&#34;vendor_fix&#34;</span>: {<span style="color:#e6db74">&#34;Not Affected&#34;</span>, <span style="color:#e6db74">&#34;Fixed&#34;</span>}, <span style="color:#e6db74">&#34;optional_patch&#34;</span>: {<span style="color:#e6db74">&#34;Affected&#34;</span>},
</span></span><span style="display:flex;"><span>              <span style="color:#e6db74">&#34;none_available&#34;</span>: {<span style="color:#e6db74">&#34;Not Affected&#34;</span>, <span style="color:#e6db74">&#34;Fixed&#34;</span>}, <span style="color:#e6db74">&#34;fix_planned&#34;</span>: {<span style="color:#e6db74">&#34;Fixed&#34;</span>},
</span></span><span style="display:flex;"><span>              <span style="color:#e6db74">&#34;no_fix_planned&#34;</span>: {<span style="color:#e6db74">&#34;Fixed&#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">test_6_1_36</span>(doc):
</span></span><span style="display:flex;"><span>    groups <span style="color:#f92672">=</span> {g[<span style="color:#e6db74">&#34;group_id&#34;</span>]: g[<span style="color:#e6db74">&#34;product_ids&#34;</span>] <span style="color:#66d9ef">for</span> g <span style="color:#f92672">in</span> doc<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;product_tree&#34;</span>, {})<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;product_groups&#34;</span>, [])}
</span></span><span style="display:flex;"><span>    failures <span style="color:#f92672">=</span> []
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">for</span> i, v <span style="color:#f92672">in</span> enumerate(doc<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;vulnerabilities&#34;</span>, [])):
</span></span><span style="display:flex;"><span>        status <span style="color:#f92672">=</span> {}
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">for</span> key, ids <span style="color:#f92672">in</span> v<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;product_status&#34;</span>, {})<span style="color:#f92672">.</span>items():
</span></span><span style="display:flex;"><span>            <span style="color:#66d9ef">for</span> pid <span style="color:#f92672">in</span> ids:
</span></span><span style="display:flex;"><span>                status<span style="color:#f92672">.</span>setdefault(pid, set())<span style="color:#f92672">.</span>add(GROUP[key])
</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">for</span> j, r <span style="color:#f92672">in</span> enumerate(v<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;remediations&#34;</span>, [])):
</span></span><span style="display:flex;"><span>            ids <span style="color:#f92672">=</span> set(r<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;product_ids&#34;</span>, []))
</span></span><span style="display:flex;"><span>            <span style="color:#66d9ef">for</span> gid <span style="color:#f92672">in</span> r<span style="color:#f92672">.</span>get(<span style="color:#e6db74">&#34;group_ids&#34;</span>, []):
</span></span><span style="display:flex;"><span>                ids <span style="color:#f92672">|=</span> set(groups<span style="color:#f92672">.</span>get(gid, []))
</span></span><span style="display:flex;"><span>            <span style="color:#66d9ef">for</span> pid <span style="color:#f92672">in</span> ids:
</span></span><span style="display:flex;"><span>                <span style="color:#66d9ef">if</span> status<span style="color:#f92672">.</span>get(pid, set()) <span style="color:#f92672">&amp;</span> PROHIBITED[r[<span style="color:#e6db74">&#34;category&#34;</span>]]:
</span></span><span style="display:flex;"><span>                    failures<span style="color:#f92672">.</span>append((i, j, r[<span style="color:#e6db74">&#34;category&#34;</span>], pid))
</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">return</span> failures
</span></span></code></pre></div><p>Results across the 20 example files (6 advisories, 14 VEX):</p>
<ul>
<li>All 20 validate against the CS01 schema with zero errors.</li>
<li>All 14 <code>csaf_vex</code> examples pass the 6.1.36 port.</li>
<li>The three files marked <code>csaf_deprecated_security_advisory</code> fail it: 6, 1 and 15 product-level hits. Each is a <code>vendor_fix</code> on a product also listed as fixed or known_not_affected. That is the pattern the converter can&rsquo;t resolve without guessing, which is consistent with those files being downgraded rather than converted.</li>
</ul>
<p>The point for your pipeline: once you accept 2.1, run 6.1.36 (or a validator that implements it) before you act on remediations. A contradicting file tells you the vendor&rsquo;s data needs human review.</p>
<h2 id="two-versions-in-parallel-provider-metadatajson-paths">Two versions in parallel: provider-metadata.json paths</h2>
<p>The CS01 section &ldquo;Transition between CSAF 2.0 and CSAF 2.1&rdquo; describes how a provider SHOULD run both versions during migration. The provider announces three dates: when 2.1 serving begins, a roll-over date when 2.1 becomes authoritative, and an end date after which 2.0 is no longer maintained.</p>
<table>
  <thead>
      <tr>
          <th>Path</th>
          <th>Content</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><code>/.well-known/csaf/v2.0/provider-metadata.json</code></td>
          <td>2.0 metadata, <code>canonical_url</code> pointing at this path</td>
      </tr>
      <tr>
          <td><code>/.well-known/csaf/v2.1/provider-metadata.json</code></td>
          <td>2.1 metadata, optional <code>maintained_from</code></td>
      </tr>
      <tr>
          <td><code>/.well-known/csaf/provider-metadata.json</code></td>
          <td>equal to the v2.0 file until roll-over, then equal to the v2.1 file; &ldquo;Redirects SHALL NOT be used&rdquo; (a symlink is allowed)</td>
      </tr>
      <tr>
          <td><code>/.well-known/csaf/archive/v2.0.tar.zst</code> (or <code>.tar.bz2</code>, <code>.tar.xz</code>)</td>
          <td>optional archive of retired 2.0 documents, with a hash</td>
      </tr>
  </tbody>
</table>
<p>Both versioned URLs SHALL also be listed in <code>security.txt</code> if the provider uses one. 2.1 provider metadata adds <code>maintained_from</code> and <code>maintained_until</code>. 2.0 had neither, so you can&rsquo;t read an end date from a 2.0 metadata file. Aggregators follow the same pattern under <code>/.well-known/csaf-aggregator/</code>, and &ldquo;A CSAF 2.1 aggregator SHALL only sync and list CSAF 2.1 publishers and providers.&rdquo;</p>
<p>For a downloader, this means one rule. If you need a specific version, ask for the versioned path. Don&rsquo;t rely on the unversioned one, because its content will change under you on the roll-over date.</p>
<h2 id="which-tools-read-21-today">Which tools read 2.1 today</h2>
<table>
  <thead>
      <tr>
          <th>Tool</th>
          <th>Version checked</th>
          <th>CSAF 2.1</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>gocsaf (<code>csaf_downloader</code>, <code>csaf_validator</code>, <code>csaf_provider</code>)</td>
          <td>v5.0.0-pre.1 (tag dated 5 Nov 2026)</td>
          <td>Yes. README: &ldquo;Version 5 adds support for CSAF 2.1 alongside CSAF 2.0&rdquo;. Downloader takes <code>--csaf_version=2.0</code> or <code>2.1</code> and warns when <code>maintained_until</code> is within 90 days; remote validation is 2.0 only</td>
      </tr>
      <tr>
          <td>gocsaf</td>
          <td>v3.7.1 (latest stable tag)</td>
          <td>No. The library defines only <code>CSAFVersion20 = &quot;2.0&quot;</code></td>
      </tr>
      <tr>
          <td>Trivy</td>
          <td>v0.76.2</td>
          <td>No. It decodes CSAF VEX with gocsaf v3.7.0, which rejected a 2.1 file in our <a href="/posts/csaf-vex-remediations-threats-category-product-ids-trivy/">21 November test</a></td>
      </tr>
  </tbody>
</table>
<p>We read the gocsaf source and docs at the v5 tag. We didn&rsquo;t run the v5 binaries.</p>
<p>The gocsaf v5 downloader docs say it uses &ldquo;the first valid <code>provider-metadata.json</code> that is found from well-known URL, security.txt or DNS in that order without version specificity&rdquo;. By default it rejects documents whose <code>csaf_version</code> doesn&rsquo;t match the metadata version. During a vendor&rsquo;s transition, pin <code>--csaf_version</code> if your downstream tooling only understands one version.</p>
<h2 id="what-to-do-now">What to do now</h2>
<ol>
<li><strong>Branch on <code>csaf_version</code> first.</strong> Route <code>2.1</code> files to a 2.1 parser, or quarantine them, rather than letting a 2.0 parser read them and silently drop scores.</li>
<li><strong>Read <code>metrics[]</code>, not just CVSS.</strong> 2.1 files can carry a vendor&rsquo;s EPSS and SSVC values next to CVSS v4. Feed them into the same decision flow you use for CVE-level signals. Our <a href="/posts/vulnerability-prioritization-workflow-cve-record-to-patch-ticket/">prioritization workflow from CVE record to ticket</a> shows where each one fits.</li>
<li><strong>Map <code>unknown</code>, <code>fix_planned</code> and <code>optional_patch</code> explicitly.</strong> Unknown status is not the same as not affected.</li>
<li><strong>Run test 6.1.36 before acting on remediations.</strong> Contradictions mean manual review.</li>
<li><strong>Pin versioned metadata URLs</strong> for scheduled downloads during vendor transitions.</li>
<li><strong>Expect <code>csaf_deprecated_security_advisory</code>.</strong> Handle it like a 2.0 security advisory.</li>
</ol>
<h2 id="limits-of-this-article">Limits of this article</h2>
<ul>
<li>CSAF 2.1 is at Committee Specification 01. Field names and test numbers could change before it becomes an OASIS Standard.</li>
<li>Our schema diff compares property names and enums. It does not cover every pattern, <code>minItems</code> or format change; read the schemas before you ship a validator.</li>
<li>Our test port covers one mandatory test out of many. It is not a conformant CSAF validator.</li>
<li>We haven&rsquo;t checked which vendors publish 2.1 files in production today.</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>2.1 prose is &ldquo;Committee Specification 01&rdquo;, dated 09 November 2026</td>
          <td><a href="https://github.com/oasis-tcs/csaf/blob/master/csaf_2.1/prose/share/csaf-v2.1-draft.md">csaf-v2.1-draft.md (rendered CS01) in oasis-tcs/csaf</a></td>
          <td>Verified (TC repository; OASIS publication page not checked)</td>
      </tr>
      <tr>
          <td>Field renames, new enums, removed <code>legacy</code> and <code>WHITE</code></td>
          <td><a href="https://github.com/oasis-tcs/csaf/blob/master/csaf_2.1/json_schema/csaf.json">CSAF 2.1 csaf.json</a> vs <a href="https://github.com/oasis-tcs/csaf/blob/master/csaf_2.0/json_schema/csaf_json_schema.json">CSAF 2.0 schema</a></td>
          <td>Verified by our schema diff</td>
      </tr>
      <tr>
          <td>optional_patch / fix_planned definitions, remediation-status table, test 6.1.36</td>
          <td>CS01 prose, vulnerabilities property and mandatory tests sections</td>
          <td>Verified (verbatim)</td>
      </tr>
      <tr>
          <td>Converter rules: vendor_fix to optional_patch, deprecated category, relationships to product_paths, default TLP:CLEAR</td>
          <td>CS01 Conformance Clause 18</td>
          <td>Verified (verbatim)</td>
      </tr>
      <tr>
          <td>Transition paths, no redirects, aggregator rule</td>
          <td>CS01 &ldquo;Transition between CSAF 2.0 and CSAF 2.1&rdquo;</td>
          <td>Verified (verbatim)</td>
      </tr>
      <tr>
          <td>20 examples validate; 3 deprecated files fail the 6.1.36 port (6, 1, 15 hits)</td>
          <td>Our run against <a href="https://github.com/oasis-tcs/csaf/tree/master/csaf_2.1/examples/csaf">csaf_2.1/examples/csaf</a> at commit e8fdccc7</td>
          <td>Verified (our test)</td>
      </tr>
      <tr>
          <td>gocsaf v5.0.0-pre.1 supports 2.1; v3.7.1 is 2.0 only</td>
          <td><a href="https://github.com/gocsaf/csaf">gocsaf/csaf</a> README and <code>csaf/advisory.go</code> at those tags</td>
          <td>Verified (source read, binaries not run)</td>
      </tr>
  </tbody>
</table>
]]></content:encoded></item></channel></rss>