Modern networks are increasingly dependent on centralized platforms to manage hundreds or thousands of devices; this convenience, however, makes management panels high-value targets. Cisco Catalyst SD-WAN Manager - the management solution that brings together in one board the control of hundreds or thousands of SD-WAN elements - is back at the center of the news because Cisco itself confirmed that two additional security failures are being exploited in real environments, and has asked administrators to update their equipment as soon as possible.
The problems reported are not theoretical: there is active exploitation in nature According to the company's recent update. Cisco extended the warning he launched in February and noted that the vulnerabilities identified as CVE-2026-20122 and CVE-2026-20128 have been used by attackers. The official note is available at the Cisco Security Centre at this link: Cisco Security Advisory.

In order to understand gravity, it is appropriate to set on access vectors: the vulnerability listed as CVE-2026-20122 allows arbitrary overwriting of files and, although its remote operation requires reading-only credentials with access to the API, this does not make it harmless; by manipulating critical files an attacker can alter configurations, plant back doors or prepare further steps to scale privileges. The technical description of this failure is available in the NVD: CVE-2026-20122 (NVD).
The other active vulnerability, CVE-2026-20128, is less severe according to classification but equally worrying because it allows the filtration of sensitive information if a local attacker has valid credentials in vManage. Details can be reviewed in the NIST vulnerability register: CVE-2026-20128 (NVD). Cisco points out that both failures affect the software of Catalyst SD-WAN Manager regardless of how the devices are configured, which extends the risk surface.
This notice comes in context: recently the exploitation sustained from at least 2023 of a critical vulnerability in the same management suite, identified as CVE-2026-20127, which allowed sophisticated attackers to add "rogue" pairs (false peers) to compromised SD-WAN networks and thus insert malicious devices that seem legitimate. Information on this violation is also provided in the public databases: CVE-2026-20127 (NVD).
The sensitivity of the problem prompted responses from the authorities. In the United States, the Infrastructure and Cybersecurity Security Agency (CISA) launched the Emergency Directive ED 26-03, which forces federal agencies to invent Cisco SD-WAN devices, preserve forensic devices, outsource records, deploy patches and review possible incidents related to these vulnerabilities. The full text of the directive is available here: CISA ED 26-03.
At the same time, Cisco has published updates for other sensitive products, such as its Secure Firewall Management Center, where errors were corrected that could allow from avoiding authentication to running remote code with root privileges (CVE-2026-20079 and CVE-2026-20131); the references in the vulnerability catalogue allow to follow the technical track of these problems: CVE-2026-20079 (NVD) and CVE-2026-20131 (NVD).
What should an administrator do now? The first step is to apply the corrected versions of the software that Cisco has made available: the company insists that updating is the most reliable way to remove these attack vectors. In addition, it is advisable to restrict access to management APIs, review and rotate credentials with priority, and segment the network to separate the management plan from the other production traffic, so that a break in the user environment does not allow a direct jump to the central controller.

It is not enough to install patches: it is appropriate to investigate the possible previous activity. Cisco and the agencies have recommended collecting and keeping records, looking for signs of unauthorised peer creation, unexpected changes in templates or policies, new certificates issued without control and unusual outgoing traffic to unknown destinations. This forensic work is key to distinguishing a preventive update from a response to an already consumed intrusion. Cisco provides guides and technical details in his safety note: Cisco Security Advisory, and the CISA directive explains minimum operating steps for federal environments: CISA ED 26-03.
The lesson left by this episode is clear: the pieces that centralize control on critical infrastructure concentrate risk. A failure in the manager not only compromises an isolated device, but potentially opens the door to the entire network that depends on it. Therefore, combining timely updates with good safety hygiene - access control, external records, segmentation and continuous monitoring - is the only way to reduce the impact of such failures.
If you manage Catalyst SD-WAN Manager, plan a maintenance window to apply the patches and launch a comprehensive check of your environment. It takes over the official documentation of Cisco and the recommendations of authorities such as CISA so that the intervention is complete and does not leave loose ends. Useful links to start with: Cisco's own note ( advisory), the NVD entries on the above-mentioned EQs ( CVE-2026-20122, CVE-2026-20128, CVE-2026-20127) and the CISA Directive ( ED 26-03).
Related
More news on the same subject.

18-year-old Ukrainian youth leads a network of infostealers that violated 28,000 accounts and left $250,000 in losses
The Ukrainian authorities, in coordination with US agents. They have focused on an operation of infostealer which, according to the Ukrainian Cyber Police, was allegedly adminis...

RAMPART and Clarity redefine the safety of IA agents with reproducible testing and governance from the start
Microsoft has presented two open source tools, RAMPART and Clarity, aimed at changing the way the safety of IA agents is tested: one that automates and standardizes technical te...

The digital signature is in check: Microsoft dismands a service that turned malware into apparently legitimate software
Microsoft announced the disarticulation of a "malware-signing-as-a-service" operation that exploited its device signature system to convert malicious code into seemingly legitim...

A single GitHub workflow token opened the door to the software supply chain
A single GitHub workflow token failed in the rotation and opened the door. This is the central conclusion of the incident in Grafana Labs following the recent wave of malicious ...

WebWorm 2025: the malware that is hidden in Discord and Microsoft Graphh to evade detection
The latest observations by cyber security researchers point to a change in worrying tactics of an actor linked to China known as WebWorm: in 2025 it has incorporated back doors ...

Identity is no longer enough: continuous verification of the device for real-time security
Identity remains the backbone of many security architectures, but today that column is cracking under new pressures: advanced phishing, real-time proxyan authentication kits and...

The dark matter of identity is changing the rules of corporate security
The Identity Gap: Snapshot 2026 report published by Orchid Security puts numbers to a dangerous trend: the "dark matter" of identity - accounts and credentials that are neither ...