Mitigation vs remediation in vendor advisories

Vendors use the same words for different things. OASIS CSAF 2.0 defines five remediation categories. Of 50 Fortinet advisories read on 19 Nov 2026, 47 list a vendor fix and 1 also lists a mitigation. Fifty Red Hat errata files for a single CVE all list a fix and a workaround, and none uses the mitigation category.

  1. Remediate
  2. Mitigate now, fix laterThis page is about it
  3. Accept with a dated exception

The shared vocabulary: CSAF 2.0

OASIS CSAF Version 2.0, Section 3.2.3.12.1, gives machine-readable advisories five remediation categories: workaround, mitigation, vendor_fix, none_available and no_fix_planned. Each is defined below in the standard's words.

OASIS CSAF Version 2.0, Section 3.2.3.12.1, https://docs.oasis-open.org/csaf/csaf/v2.0/os/csaf-v2.0-os.html, read 19 Nov 2026.
CategoryCSAF 2.0 meaning
workaround"a configuration or specific deployment scenario that can be used to avoid exposure to the vulnerability"; typically the "first line of defense" before a mitigation or fix
mitigation"helps to reduce the risk of the vulnerability but that does not resolve the vulnerability on the affected product"; may use "devices or access controls external to the affected product"
vendor_fix"an official fix that is issued by the original author of the affected product", assumed to fully resolve it
none_available"currently no fix or other remediation available"
no_fix_planned"no fix for the vulnerability and it is not planned to provide one at any time", often because the product is "orphaned, declared end-of-life, or otherwise deprecated"

The specification makes vendor_fix exclusive with none_available and no_fix_planned for the same product. An advisory that lists both a fix and a mitigation for one product is telling the reader what to do until the fix is installed. The prose side, how twelve advisories word workaround and mitigation, is on workaround versus mitigation. This page covers the machine-readable categories and what to record from them.

Advisories where the label and the action differ

The rows below ask who acts and what a label tells the reader to record.

Advisories and Microsoft's October 2026 CVRF file read 19 Nov 2026; sources are listed below. Dates are the vendors' publication dates, except the Fortinet cloud date, which is the date the advisory gives for the vendor's own change.
Vendor and recordWording in the advisoryWhat the label tells the reader
Cisco ISE, CVE-2026-76460 (16 Sep 2026)Header: "No workarounds available". Body: "There are no workarounds that address this vulnerability. However, there is a mitigation."The header counts only steps that avoid exposure; the infrastructure access control list that limits who can reach the flaw is filed as a mitigation. The case with owners and dates is on mitigate versus manage risk
Fortinet FortiMail, FG-IR-26-175 (1 Oct 2026)"Fortinet has remediated this issue on oct 05, 2026 in FortiMail Cloud", so "FortiMail Cloud customers need not perform any action"; self-managed units get a workaroundRemediated is the vendor's own act on its hosted service; the workaround is the customer's step elsewhere
Microsoft Azure Pipelines, CVE-2026-105014 (published 22 Oct 2026)"This vulnerability has already been fully mitigated by Microsoft. There is no action for users of this service to take." The entry carries no remediation items. 13 of the 3,876 entries in the October 2026 CVRF file carry the same sentence.Vendor-side resolution with no customer step and no fix to install; see mitigation in cloud and SaaS

Cisco's Fixed Software section states its own policy: "Cisco considers any workarounds and mitigations (if applicable) to be temporary solutions until an upgrade to a fixed software release is available." Control first, fix on a date, control removed.

What 50 Fortinet advisories show

Fortinet publishes a CSAF file per advisory, linked from its PSIRT RSS feed. The 50 advisories in the feed on 19 Nov 2026 split as follows by remediation category.

Fortinet PSIRT RSS feed https://filestore.fortinet.com/fortiguard/rss/ir.xml and the 50 linked CSAF files, read 19 Nov 2026.
Remediation categories in the fileAdvisories
vendor_fix only46
vendor_fix and mitigation1
No vulnerabilities block3
Total50

So 47 advisories list a vendor_fix, and the one with a mitigation is among them. It is FG-IR-26-273, a FortiOS flaw in high availability traffic. Its mitigation entry reads "A virtual patch is available" and names an IPS signature package, while the vendor_fix entry lists FortiOS 8.0.1, 7.6.8, 7.4.13 and 7.2.14 and says "FortiOS 7.0: Migrate to a fixed release". A signature that blocks traffic is filed as a mitigation, not a fix, which matches the IPS signature entry.

What 50 Red Hat errata for one CVE show

Red Hat publishes one CSAF file per security advisory. The 50 files counted here are RHSA errata first released between 22 Oct and 13 Nov 2026, and every one of them carries the same CVE, CVE-2026-116591 (a zstd decoder flaw, shipped in many images). They show how Red Hat files one flaw, not its mix across flaws, so no comparison with the Fortinet count is drawn.

Red Hat CSAF files for CVE-2026-116591 listed in https://security.access.redhat.com/data/csaf/v2/advisories/changes.csv, read 19 Nov 2026.
Remediation categories in the fileAdvisories
vendor_fix and workaround50
mitigation0
Total50

The two vendors file steps under different categories. Fortinet puts a virtual patch under mitigation. Red Hat's files use workaround for text such as "Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability", and for configuration steps that begin "To mitigate this issue". A script that counts only the mitigation category finds one Fortinet advisory and none of the Red Hat files, so read the text of every remediation entry.

One advisory worked into a record

RHSA-2026:88185 (Red Hat Hardened Images RPMs, first released 22 Oct 2026, rated Important) covers CVE-2026-116591, a denial of service in the klauspost/compress zstd decoder (CVSS 3.1 base score 7.5 in Red Hat's file). Its CSAF file carries a vendor_fix entry pointing to the errata and a workaround entry. The workaround entry says: "Reject or filter untrusted Zstandard-compressed payloads at ingress proxies, or restrict decompression endpoints to authenticated, trusted clients." The entry also carries guidance dated 3 Nov 2026 whose label says it was generated with AI tools and that customers should "independently evaluate and test these temporary mitigations". Using the reading rule below, the record for a team that runs an affected image reads:

Advisory facts from Red Hat's CSAF file for RHSA-2026:88185, read 19 Nov 2026. The control, test and removal rows are the record a team would write.
Record fieldEntry
Vendor labelsvendor_fix (RHSA-2026:88185) and workaround
Treat asMitigate now, fix on a date, because both categories are present
ControlIngress proxy rejects or filters untrusted zstd-compressed request bodies; the vendor text does not name a product setting, so the team writes its own
What it leaves openApplications that decompress zstd data fetched from elsewhere, and any path that does not pass the proxy
TestDated test by a second person that an untrusted zstd request is refused on the production path
FixInstall the fixed Red Hat build from RHSA-2026:88185 and record the version and date; Red Hat's text names klauspost/compress 1.20.2 or later as the upstream fix
RemovalDelete the proxy rule on the day the fixed build is confirmed in production

Reading rule for a decision record

Mapping drawn up for this page; the labels are the vendors'. For industrial products see ICS vulnerability mitigation.
Vendor labelTreat asRecord
vendor_fix or Vendor fixRemediateVersion installed and date
mitigation or workaroundMitigate now, fix on a dateControl, tester and the date the fix is due
none_availableMitigate, track the vendorLast vendor contact date
"Migrate to a fixed release"Remediate by moving to the fixed branchTarget version and migration date
no_fix_plannedReplace, remove or accept with a dated exceptionReplacement date or signed exception

Sources

Last reviewed