Skip to main content
Mallory
HighVulnerability

CVE-2026-20276: Cisco IOS XR Insufficient Control Flow Management Vulnerabilities

Published Sep 2, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.6High · v3.1
EPSS0.47%41st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Cisco Systems
IdentifiersCVE-2026-20276CWE-691 · Insufficient Control Flow Management

CVE-2026-20276 tracks multiple internally discovered insufficient control-flow-management vulnerabilities in Cisco IOS XR Software. The issues are classified as CWE-691 and were identified during an internal security review. Cisco addressed them through IOS XR software-hardening releases. The assigned CVSS v3.1 vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation has a high availability impact and may cause a denial-of-service condition on an affected Cisco IOS XR device. The assigned vector indicates no direct confidentiality or integrity impact, with scope changed.

Mitigation

If you can’t patch tonight, do this now.

No workaround is available. Prioritize expedited maintenance for Cisco IOS XR deployments, including IOS XR7 (LNT), because all releases are affected. Until updates are deployed, restrict network reachability to IOS XR devices and exposed management or service interfaces to trusted networks where operationally feasible, and monitor for device instability or denial-of-service events.

Remediation

Patch, then assume compromise.

Upgrade Cisco IOS XR Software to release 26.2.2 or 26.3.1, which are identified as fixed releases not requiring Security Maintenance Updates. For other supported IOS XR releases, install all applicable Cisco Security Maintenance Updates for the deployed platform and enabled functional areas. Contact Cisco TAC or the relevant support organization when required SMUs are not listed for a release.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Cisco SystemsIos Xroperating_system
FAQ

Frequently asked questions

Is CVE-2026-20276 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-20276 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-20276?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-20276.
Is there a patch for CVE-2026-20276?
Upgrade Cisco IOS XR Software to release 26.2.2 or 26.3.1, which are identified as fixed releases not requiring Security Maintenance Updates. For other supported IOS XR releases, install all applicable Cisco Security Maintenance Updates for the deployed platform and enabled functional areas.
What products are affected by CVE-2026-20276?
Cisco Systems Ios Xr.
How severe is CVE-2026-20276?
CVE-2026-20276 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 0.47% (41st percentile) as of Sep 25, 2026.
Activity feed

Recent activity

12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.