CISA Adds Four Known Exploited Vulnerabilities to Catalog
Reporting by CISA Known Exploited VulnerabilitiesRead the original at cisa.gov
Executive Summary
CISA has expanded its Known Exploited Vulnerabilities (KEV) Catalog by adding four specific vulnerabilities, including issues affecting SAP NetWeaver, Cisco Expressway Series, VMWare vCenter, and Apache Roller. This catalog entry is based on confirmed evidence of active exploitation, signaling that these weaknesses are currently being leveraged by malicious actors. Federal Civilian Executive Branch (FCEB) agencies are bound by Binding Operational Directive (BOD) 26-04, which mandates that they prioritize the rapid remediation of such high-risk, publicly exposed vulnerabilities that grant total control upon exploitation.
While the directive is limited to FCEB agencies, CISA advises all organizations to adopt a similar risk-based approach to vulnerability management. The agency encourages entities to submit any newly identified, exploited vulnerabilities lacking a KEV entry via a formal nomination process, provided they include a CVE ID, proof of exploitation, and clear mitigation guidance. The continuous addition of vulnerabilities reflects an evolving threat landscape requiring proactive defense strategies across sectors.
Facts Only
CISA added four vulnerabilities to the Known Exploited Vulnerabilities (KEV) Catalog.
The added vulnerabilities are:
CVE-2025-42884 (SAP NetWeaver Improper Neutralization of Special Elements in Data Query Logic)
CVE-2026-76466 (Cisco Expressway Series Use of Hard-coded Credentials)
CVE-2026-123890 (VMWare vCenter Authentication Bypass Using an Alternate Path or Channel)
CVE-2026-129448 (Apache Roller Deserialization of Untrusted Data)
BOD 26-04 establishes vulnerability management requirements for Federal Civilian Executive Branch (FCEB) agencies.
BOD 26-04 requires FCEB agencies to prioritize rapid remediation for high-risk KEV Catalog vulnerabilities on publicly exposed assets that grant total control post-exploitation.
CISA encourages all organizations to adopt risk-based vulnerability management and prioritize KEV Catalog vulnerabilities.
Organizations can submit known exploited vulnerabilities to CISA via the KEV Nomination Form if they have a CVE ID, exploitation evidence, and mitigation guidance.
Full Take
The framing here centers on bureaucratic urgency meeting technical reality: the recognized danger of actively exploited flaws. The strongest narrative is that the federal security apparatus is actively translating technical findings (the CVEs) into enforceable policy (BOD 26-04), thereby raising the baseline expectation of defensive rigor across critical infrastructure. The risk posed by these flaws—gaining "total control" post-exploitation—demands an immediate, rather than cyclical, response.
The pattern at play is the **Normalization of Constant Threat**, where the addition of four new, specific, high-impact exploits serves less as a discrete alert and more as a systemic affirmation that threat actors are relentlessly targeting established, complex software layers (NetWeaver, VMWare, etc.). The implied assumption underpinning this notification is that compliance with governmental mandates (BOD 26-04) is the primary lever for security improvement, which risks creating a compliance-driven perimeter defense rather than fostering true resilience.
The deeper implication concerns the asymmetry of defense: government agencies are explicitly directed toward remediation, whereas the encouragement offered to the broader sector is framed as a best practice adoption, creating a tier-two vulnerability in governance. Who benefits is the defender, incentivized by the visibility of the KEV catalog; who bears the cost is the organization whose remediation lags behind the active exploitation window.
How might the emphasis shift from reactive patching (responding to the KEV catalog) to proactive hardening against attack surfaces before the vulnerability is publicized or actively exploited? What non-CVE-based controls—architectural shifts or segmentation—could reduce the consequence of successful exploitation, regardless of the flaw's presence in the catalog?
Counterstrike Scan: A coordinated influence campaign might employ the pattern of **Manufactured Urgency via Authority Game**, presenting the KEV catalog as the sole arbiter of necessary action, thereby discouraging nuanced risk assessment in favor of immediate, costly patching cycles endorsed by the governing body. The actual content aligns closely with this by heavily tying remediation necessity to the governmental directive, though it is balanced by the invitation to submit non-listed vulnerabilities.
Autonomy check: No autonomy signals.
From the original · CISA Known Exploited Vulnerabilities
CISA has added four new vulnerabilities to its Known Exploited Vulnerabilities (KEV) Catalog, based on evidence of active exploitation. - CVE-2025-42884 SAP NetWeaver Improper Neutralization of Special Elements in Data Query Logic Vulnerability - CVE-2026-76466 Cisco Expressway Series Use of Hard-coded Credentials Vulnerability - CVE-2026-123890 VMWare vCenter Authentication Bypass Using an…Read the full story at cisa.gov
Sentinel unavailable
The automated check of the source article's wording did not complete, so no result is shown.
This looks only at the wording of the original source article, not at this page's AI-written sections. A small local AI model made this estimate. It has not been checked against known human and machine texts, so treat it as provisional. It cannot show who wrote an article.
