CVE-2025-20352MalwarePublished 16 Oct 2025

Cisco Routers Hacked for Rootkit Deployment

Source SecurityWeek

Authoritative record:CVE-2025-20352· High 7.7

Exploited in the wild · KEV due 20 Oct 2025 : block it and hunt for it in your logs now.

Data as of 17 Oct 2025, 05:40 UTC

CVSS base score

7.7High

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 20 Oct 2025 US federal agencies must patch by this date; a sensible deadline for everyone else.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 24 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 5 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by cisco
2024-10-1019:15Z, 349 days before disclosure
CVE published
on cve.org
2025-09-2417:10Z, t = 0
In Threat Radar
record ingested
2025-09-2417:20Z, 10 minutes after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
2025-09-29, 5 days after disclosure
KEV remediation due
US federal deadline
2025-10-20, 26 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

Description

Threat actors are exploiting CVE-2025-20352, a recent Cisco zero-day, to deploy a rootkit on older networking devices. The post Cisco Routers Hacked for Rootkit Deployment appeared first on SecurityWeek .

Impact

For European organizations, the exploitation of this zero-day on Cisco routers could lead to significant network security breaches. Compromised routers can allow attackers to intercept sensitive communications, manipulate network traffic, and create persistent backdoors, undermining confidentiality, integrity, and availability of data flows. Critical sectors such as telecommunications, finance, government, and large enterprises that rely heavily on Cisco networking equipment are at heightened risk. The rootkit’s stealthy nature complicates detection and remediation, potentially allowing prolonged unauthorized access and data exfiltration. Disruption of network services due to compromised routing devices could also impact business continuity and critical infrastructure operations. The impact is exacerbated in environments where legacy Cisco devices remain in use without timely updates or replacements. European organizations with complex network topologies and interconnected systems may face cascading effects if compromised routers facilitate lateral movement within networks.

Defensive guidance

1. Conduct an immediate inventory of all Cisco networking devices to identify older models potentially affected by CVE-2025-20352. 2. 3. Implement network segmentation to isolate legacy routers from critical network segments and sensitive data flows. 4. Enhance network monitoring and logging to detect anomalous router behavior indicative of rootkit activity, such as unexpected configuration changes or unusual traffic patterns. 5. Use intrusion detection/prevention systems (IDS/IPS) tuned to detect known attack signatures or suspicious activities related to router compromise. 6. Limit administrative access to routers using strong authentication methods and restrict management interfaces to trusted networks. 7. Plan for phased replacement of outdated Cisco hardware with supported models receiving regular security updates. 8. Conduct regular security audits and penetration testing focused on network infrastructure to identify potential compromises early. 9. Establish incident response procedures specifically addressing network device compromises, including forensic analysis and recovery steps.

References

securityweek.com/cisco-routers-hacked-for-rootkit-deployment/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

Timeline

Description

AI analysisMachine-generated, updated 16 Oct 2025, 11:14 UTC

References

Community reviews

Related threats