Workaround vs mitigation

Advisories do not use the two words alike. Fortinet and LiteLLM call a feature switch a workaround, Red Hat files the same kind of step under mitigation, and Cisco prints "no workarounds" beside a listed mitigation. On 19 Nov 2026 CISA's KEV feed used mitigations in 795 of 1,786 required actions and workaround in one.

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

The definitions vendors rarely quote

OASIS CSAF 2.0, the format many vendors publish advisories in, defines a workaround as remediation information about "a configuration or specific deployment scenario that can be used to avoid exposure to the vulnerability". It defines a mitigation as information that "helps to reduce the risk of the vulnerability but that does not resolve the vulnerability on the affected product" (CSAF 2.0, remediation category). The general meaning is in the difference between remediation and mitigation.

Microsoft once defined the words the other way round. Bulletin MS10-046 (2010) says a mitigation is a setting or common configuration "existing in a default state, that could reduce the severity of exploitation of a vulnerability", and a workaround "does not correct the underlying vulnerability but would help block known attack vectors before you apply the update" (MS10-046). In Microsoft's August 2026 CVRF file the entry for CVE-2026-56179 (Windows Network Address Translation spoofing) says: "The mitigation is disabled by default. To enable it, apply the following registry keys and reboot the machine." A 2026 Microsoft mitigation is something the administrator switches on, not a default that already helps (MSRC CVRF 2026-Aug).

How twelve 2026 advisories word it

Eleven of the twelve rows are CVEs in this site's data, read again on 19 Nov 2026 at the vendor's own page or data feed; the Microsoft row is from the MSRC file. Vendors are listed alphabetically; the right column describes the step, in this site's words.

Quoted from the vendor pages and data feeds linked under Sources; read 19 Nov 2026.
AdvisoryWording, quotedWhat the step does
BerriAI LiteLLM, GHSA-7488-6r32-c95q (CVE-2026-59822)"Workarounds If upgrading is not immediately possible, disable MCP routes or block access to /mcp/ and related MCP endpoints at your reverse proxy or API gateway."Closes the vulnerable path by turning off a set of routes.
Broadcom, VMSA-2026-0006.2 (includes CVE-2026-41709)"Workarounds: None"Offers nothing besides the patch.
Cisco, cisco-sa-asaftd-tunnel-dos-s6mgkb75 (CVE-2026-76418)"There are no workarounds that address this vulnerability. However, there is a mitigation, which is to disable secondary authentication on any user-configured tunnel group list or on the default tunnel group, DefaultWEBVPNGroup."A configuration change that Cisco files under mitigation while stating that no workaround exists.
Citrix, CTX696939 (CVE-2026-19490)"Workarounds/ Mitigating Factors None"One heading covers both words; no step is offered.
F5, K000162605 (CVE-2026-94127), CVE record field "workarounds""An iRule is available upon request. Open a ticket with F5 support to request this."A traffic rule that sits in front of the flaw, supplied on request.
Fortinet, FG-IR-26-175 (CVE-2026-104286)"customers are urged to apply the workaround below"; "Workaround: Disable the IBE feature support via the GUI"Turns off the feature that contains the flaw.
Microsoft, CVRF 2026-Aug (CVE-2026-56179)"The mitigation is disabled by default. To enable it, apply the following registry keys and reboot the machine."A hardening setting that stays off until an administrator sets it.
Palo Alto Networks (CVE-2026-0322)"Workarounds and Mitigations No known workarounds exist for this issue. Customers with a Threat Prevention subscription are provided with limited coverage against this vulnerability by enabling Threat ID 510046 and 510047"One heading for both words; a detection signature is described as limited coverage, not as a workaround.
PHP Group, GHSA-w8hw-w9fx-j79w (CVE-2026-109618)"Updating to a PHP release containing the patch to this vulnerability is the only complete mitigation." "...setting and enforcing memory_limit=-1 administratively is the primary configuration mitigation." "This is not a complete mitigation."Counts the patch as a mitigation and the configuration change as a partial one.
Red Hat, CVE-2026-53266, field "mitigation""Disable ARP hardware address rewriting in ebtables SNAT rules, or remove ebtables SNAT rules that operate on ARP traffic on bridge interfaces."Turns off the kernel feature path the flaw sits in.
Red Hat, CVE-2026-80521, field "mitigation""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."The field holds a statement that nothing meets Red Hat's bar.
SonicWall, SNWLID-2026-0014 (CVE-2026-19868), field "workaround""If SAML authentication is in use and upgrading the firmware is not possible, disable or delete any active LDAP, RADIUS, and TACACS+ authentication server configured on the firewall."Removes the alternate sign-in paths the flaw uses.

The label does not say what the step does

Fortinet, SonicWall and LiteLLM each call a step that turns off a feature or a path a workaround. Red Hat calls a step of the same kind a mitigation, and Cisco calls its step a mitigation in the same sentence that denies any workaround exists. PHP goes further and names the patch itself a mitigation. A reader who sorts findings by the vendor's label will sort the same kind of step into two piles.

Sort by effect instead. A step that removes the vulnerable path (a disabled feature, a blocked route) changes whether the flaw can be reached. A step that narrows who can reach it (an access list, a jump host) changes exposure. A signature or alert changes detection or likelihood. Each can be a compensating control; none is the fix. The wording for a configuration change is on configuration change.

When the vendor lists nothing, say so in the record and mark any step you add as your own. Broadcom's "Workarounds: None" and Citrix's "None" leave the patch as the only vendor instruction, so access limits placed in front of those products are your decision and carry your name. Mitigation when no patch exists covers the case where even the patch is absent.

CISA's KEV entries say mitigations

In the KEV feed (catalogVersion 2026.11.18, 1,786 entries) the required action of 795 entries contains "mitigat" and one contains "workaround". The one is CVE-2026-0300, a Palo Alto Networks entry that repeats the vendor's text: "Until the vendor releases an official fix, the following workaround should be implemented". Entries with a vendor workaround still use CISA's word. CVE-2026-94127 (F5, due 25 Sep 2026) and CVE-2026-104286 (Fortinet, due 4 Oct 2026) both read: "Apply mitigations in accordance with vendor instructions" and end "discontinue use of the product if mitigations are unavailable". For a KEV item, the vendor's workaround is the mitigation CISA means. What follows if none exists is on KEV required actions: mitigate or discontinue.

What to write in the exception record

Quote the vendor's label and then say what the step does in your own terms, so a later reader can compare vendors without learning each one's vocabulary.

Vendor label and wording: "<quote>" (advisory ID, revision date)
Effect, in our words: removes the vulnerable path / narrows who can reach it / reduces impact / detects only
Function lost while in place: <what stops working>
Set by: <vendor instruction or our own decision>
Verified by: <test, owner, date>
Ends when: <fix installed, planned date>
Status of the finding: open until the vendor fix is installed

The "set by" line matters most when the vendor lists no workaround. The rest of the record follows the Risk Acceptance Form.

Sources

Last reviewed