Skip to content
VulniPulse
Sign in
Advisory severityCritical9.8Cisco Exploited

Critical [CVE-2026-20267 +6] Cisco IOS XE Software Security Hardening Release: August 2026

This critical-severity Cisco advisory covers CVE-2026-20267 and CVE-2026-20268 and 5 more CVEs affecting IOS XE Software.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations. This bulletin covers 7 CVEs; its score, affected versions and guidance may apply to different issues within that bulletin.

cisco-sa-hardening-iosxe-V8NMuMZJ Source published Source updated

VulniPulse record published Record updated

CVE-2026-20267CVE-2026-20268CVE-2026-20269CVE-2026-20270CVE-2026-20271CVE-2026-20272CVE-2026-20273
Affected products & platforms
CiscoIOS XE
Open source advisory

Android app · Google Play

Monitor future Cisco CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco IOS XE Software engineering team has conducted a comprehensive internal security review. This review resulted in software hardening releases that address multiple internally discovered vulnerabilities.

These vulnerabilities were found during internal testing and are not known to be actively exploited. To assist customers in patching and streamline the disclosure process, Cisco has grouped these issues by their underlying vulnerability class — Common Weakness Enumeration (CWE) — and assigned a single Common Vulnerabilities and Exposures identifier (CVE ID).

Cisco has released software updates that address these vulnerabilities. There are no workarounds that address these vulnerabilities.

Affected versions
  • Scope: These vulnerabilities affect Cisco IOS XE Software when it is running in autonomous or controller mode, regardless of device configuration.
  • Release 17.9 (first fixed: 17.9.10)
  • Release 17.12 (first fixed: 17.12.8)
  • Release 17.15 (first fixed: 17.15.6)
  • Release 17.18 (first fixed: 17.18.4, 17.18.4a)
  • Release 26.1 (first fixed: 26.1.2)

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Fixed versions
  • 17.9.10
  • 17.12.8
  • 17.15.6
  • 17.18.4, 17.18.4a
  • 26.1.2

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Upgrade to the first fixed release for your train per the Fixed Releases table in this advisory.
  • Release 17.9: upgrade to 17.9.10.
  • Release 17.12: upgrade to 17.12.8.
  • Release 17.15: upgrade to 17.15.6.
  • Release 17.18: upgrade to 17.18.4, 17.18.4a.
  • Release 26.1: upgrade to 26.1.2.
Workaround status
  • There are no workarounds that address these vulnerabilities.

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.