Urgent.News

What's breaking now, across thousands of outlets.

Tech

The Cisco FMC Authentication Bypass Shows Why Management Planes Are the Real Perimeter

The Cisco FMC Authentication Bypass Shows Why Management Planes Are the Real Perimeter Cisco Secure Firewall Management Center (FMC) is the console that pushes policy to every managed firewall in a large network. When an authentication bypass there reaches root, the blast radius is not one device. It is every device the console controls. That is what happened with CVE-2026-20079, a…

The Cisco Secure Firewall Management Center (FMC) is the central console that pushes security policies to large networks of managed firewalls. When an authentication bypass in FMC reaches the root level, the impact extends beyond the single device controlled by the console, affecting all devices it manages. This is precisely what occurred with CVE-2026-20079, a pre-authentication bypass vulnerability rated with a CVSS score of 10.0.

Cisco Talos confirmed active exploitation of CVE-2026-20079 on 9 September 2026, noting three distinct intrusion clusters utilizing the flaw. The root cause stems from an improperly created system process that exists during boot, providing an unauthenticated remote attacker with a path to execute scripts with root privileges on the underlying operating system.

Cisco addressed the vulnerability in March 2026, but evidence of exploitation emerged in August 2026, leading to an updated advisory and the addition of CVE-2026-20079 to the Known Exploited Vulnerabilities catalog on 9 September 2026.

The FMC's significance extends beyond the firewall itself. As it stores configuration policy, rule sets, log data, and management credentials for the governed firewalls, an attacker controlling the FMC can rewrite rules, open pathways through the perimeter, delete log evidence, and push malicious configurations to managed devices.

Three intrusion clusters were identified: UAT-12197 deployed a JSP web shell, UAT-11823 chained both vulnerabilities, and UAT-11988 utilized static credentials to deploy ransomware. These clusters highlight various motivations, including espionage, credential theft, and ransomware attacks.

Cisco fixed the flaw in March 2026, but exploitation was observed in August 2026, and the KEV listing was released in September 2026. Despite the availability of a patch, the vulnerability remains a concern due to the patch's requirement for a maintenance window on a security control. Organizations should assess how many management interfaces are exposed to the internet, apply Cisco's hotfix for the specific release branch, restrict management interfaces to VPNs or jump hosts, and rotate credentials reachable from FMC.

Additionally, monitoring for indicators of compromise and inspecting critical files can help identify compromised systems. The incident underscores the importance of treating centralized management platforms with the same security diligence as the assets they control.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Integrity-OS: Promise --> Proof

Integrity-OS: Promise → Proof This is a submission for the Sanity Challenge, Path Two: Vibe-Code Something Strange What I Built Integrity-OS is an AI-native accountability system built around a simple…

Thumbs Up with a Twist - Correction and Smoothing of Grip

📝 Originally published (in Japanese) at forge.workstyle.tech . Introduction to the Fifth Article in the Series This is the fifth article in a series on creating VRM animations from live-action…

  • Define thumb position as 18mm from index finger's middle towards palm
  • Smooth gate over time to eliminate spikes and fill gaps
  • Apply gate to correct hand pose for accurate thumb movement

Building a Temporary Message Sharing API with NestJS, PostgreSQL, Prisma & Redis

I recently built a temporary message-sharing API from scratch using NestJS, PostgreSQL, Prisma and Redis . The idea is simple: Create a message, generate a short code, share it, and let the message…

  • Built using NestJS, PostgreSQL, Prisma, and Redis
  • Allows configurable message rules like length and expiration
  • Implements caching with Redis and rate limiting with @nestjs/throttler

Integrity-OS: Promise Proof

Integrity-OS: Promise → Proof This is a submission for the Sanity Challenge, Path Two: Vibe-Code Something Strange What I Built Integrity-OS is an AI-native accountability system built around a simple…

  • Integrity-OS tracks promises through evidence
  • Promises broken: 500 students promised, 312 verified
  • AI accountability agent available for exploration

More from Saturday 19 September →