cisco-sa-ise-mult-vul-ymSsTLCc

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

Cisco has released software updates that address this vulnerability.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

CVE-2026-20282 and CVE-2026-20284: There are no workarounds that address these vulnerabilities. CVE-2026-20283: There is a workaround that addresses this vulnerability. The vulnerability is present only when an IPsec VTI tunnel is created using the API. However, using the Cisco ISE web interface to create an IPsec VTI tunnel does not allow the vulnerability to be configured. If a vulnerable configuration is present, do the following: Return to Administration > System > Settings > Protocols > IPsec > Native IPsec. Choose the tunnel with the vulnerable configuration and remove it. Add the tunnel back using the web interface. While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.