Una señal es cualquier evento operacional detectado en las últimas 24h–30d: CVEs en KEV explotados activamente, advisories de vendor, exposición cloud, ransomware y avisos regulatorios. Cada señal se prioriza por severidad, freshness y match con tu Digital Twin.
Para análisis editorial y noticias generales visita Noticias.
Discover muestra 8 señales operativas recientes. Sube a Consultant Pro o Professional Pro para abrir el feed completo, histórico ampliado y el catálogo KEV.
The Netherlands' National Cyber Security Centre (NCSC) is warning that hackers are actively exploiting a macOS authentication bypass vulnerability after public exploit code emerged. [...] CVEs: CVE-2026-65400. CISA KEV/exploitation signal detected. Vendors: Microsoft, Palo Alto Networks, Google, SAP, Adobe, Apple, Docker, Check Point. DORA relevance: medium.
Por qué importa
Filtered for operational relevance. Powered by a curated catalog of vulnerability, CERT, vendor and threat-intelligence sources.View methodology →
Oil giant Shell has confirmed it is investigating a potential security incident after the Clop ransomware gang claimed it stole 89GB of data. [...] CVEs: CVE-2026-12569. CISA KEV/exploitation signal detected. Vendors: Microsoft, SAP, Adobe, Salesforce, ServiceNow. DORA relevance: medium.
Por qué importa
Explotación activa confirmada. Riesgo material para entornos expuestos.
Acción recomendada
Comprueba la exposición a CVE-2026-12569 en el inventario de activos y las herramientas de vulnerabilidades.
A maximum-severity SAP Commerce Cloud remote code execution vulnerability patched three days ago is already being targeted in attacks, according to threat intelligence company Defused. [...] CVEs: CVE-2026-58231, CVE-2026-44761, CVE-2026-22732, CVE-2026-34263. CISA KEV/exploitation signal detected. Vendors: Microsoft, Cisco, VMware, SAP, Adobe, Node.js. DORA relevance: medium.
Por qué importa
Explotación activa confirmada. Riesgo material para entornos expuestos.
Acción recomendada
Comprueba la exposición a CVE-2026-58231, CVE-2026-44761, CVE-2026-22732 en el inventario de activos y las herramientas de vulnerabilidades.
Cybersecurity teams should be responsible for risk oversight, rather than for executing every corrective action. Assigning security teams the tasks of finding, prioritizing, assigning, implementing, tracking and validating every remediation does not foster accountability. Instead, it results in an organizational repository for unresolved issues. A more effective model distinguishes roles clearly: security functions as the overseer, while technology and business operations execute remediation. Security should maintain the authoritative risk inventory, determine priorities, establish remediation standards, escalate missed commitments and verify closure. Owners of the affected infrastructure, cloud environment, application, identity platform or business process are responsible for implementing fixes. Executives are tasked with resolving resource conflicts and explicitly accepting risks that the organization elects not to remediate. This distinction is substantive, as it determines whether a vulnerability management program effectively reduces risk or simply generates remediation tickets. An increasing backlog indicates a failure in the operating model Security teams often become the default owners of any issue labeled as a security concern. For example, when a scanner identifies an outdated package, security is expected to patch the server. If a cloud security platform detects an exposed storage bucket, security is tasked with redesigning the deployment. Similarly, when an audit reveals excessive privileges in a business application, security is expected to negotiate access changes with the department responsible for the workflow. This dynamic arises because discovery is highly visible, while remediation is often inconvenient. When the security team produces a report, the organization may assume that the team is also responsible for implementing the solutions. Over time, infrastructure, engineering and business owners come to expect that security will initiate tickets, CISA KEV/exploitation signal detected. Vendors: Microsoft. DORA relevance: high.
Por qué importa
Explotación activa confirmada. Riesgo material para entornos expuestos.
Acción recomendada
Prioriza la remediación por explotación in-the-wild; no esperes al ciclo mensual de parcheo.
CISA has added three new vulnerabilities to its Known Exploited Vulnerabilities (KEV) Catalog, based on evidence of active exploitation. CVE-2026-20349 Cisco Secure Firewall Adaptive Security Appliance (ASA) and Firewall Threat Defense (FTD) Heap Inspection Vulnerability CVE-2026-68820 Microsoft Windows Ancillary Function Driver for WinSock Use-After-Free Vulnerability CVE-2026-72898 Metabase SQL Injection Vulnerability These types of vulnerabilities are a frequent attack vector for malicious cyber actors and pose significant risks to the federal enterprise. Binding Operational Directive (BOD) 26-04: Prioritizing Security Updates Based on Risk establishes vulnerability management requirements for Federal Civilian Executive Branch (FCEB) agencies. BOD 26-04 reinforces the importance of the KEV Catalog and requires federal agencies to prioritize rapid remediation of high-risk vulnerabilities, specifically those identified by Common Vulnerabilities and Exposures (CVEs) listed in CISA’s KEV Catalog on publicly exposed assets that grant total control of the asset post-exploitation, while deferring action for lower-risk vulnerabilities. BOD 26-04 further establishes basic expectations for when agencies must check whether threat actors compromised the system before the patch was applied. While BOD 26-04 applies only to FCEB agencies, CISA encourages all organizations to adopt risk-based vulnerability management and prioritize remediation of KEV Catalog vulnerabilities. CISA will continue to add vulnerabilities to the catalog that meet the specified criteria. Aware of an exploited vulnerability not currently listed in the KEV Catalog? Submit it for potential addition through CISA’s KEV Nomination Form. Potential KEV additions must have a CVE ID, evidence of exploitation, and clear mitigation guidance CVEs: CVE-2026-20349, CVE-2026-68820, CVE-2026-72898. CISA KEV/exploitation signal detected. Vendors: Microsoft, Cisco, GitHub. DORA relevance: medium.
Por qué importa
Explotación activa confirmada. Riesgo material para entornos expuestos.
Acción recomendada
Comprueba la exposición a CVE-2026-20349, CVE-2026-68820, CVE-2026-72898 en el inventario de activos y las herramientas de vulnerabilidades.
[CISA KEV actively exploited] Vendor: Microsoft | Product: Windows Ancillary Function Driver for WinSock | Microsoft Windows Ancillary Function Driver for WinSock contains a use-after-free vulnerability that allows an authorized attacker to elevate privileges locally. | Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. | Due date: 2026-08-25 | Ransomware use: Unknown | Added: 2026-08-11 CVEs: CVE-2026-68820. CISA KEV/exploitation signal detected. Vendors: Microsoft. DORA relevance: medium.
Por qué importa
Explotación activa confirmada. Riesgo material para entornos expuestos.
Acción recomendada
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Advisory at a Glance Title #StopRansomware: Gunra Ransomware Original Publication August 10, 2026 Executive Summary Gunra is a ransomware-as-a-service (RaaS) used by affiliates to target government, critical infrastructure, and other organizations. The Gunra ransomware variant first appeared in 2025 and expanded to RaaS operations in 2026. The actors leverage a double-extortion model, both encrypting data and threatening to publish exfiltrated data to a dedicated leak site (DLS) if the ransom is not paid. This advisory provides technical details of the activity, as well as tailored detection and mitigation guidance to protect at-risk organizations from Gunra. Key Actions Prioritize patching known exploited vulnerabilities in internet-facing systems, including virtual private network (VPN) gateways and remote desktop protocol (RDP)-exposed infrastructure. Implement and test offline, immutable backups stored in a physically separate, segmented location to ensure recoverability without ransom payment. Segment networks to restrict lateral movement from an initially compromised device to other systems in the organization. Indicators of Compromise For a downloadable copy of indicators of compromise, see: AA26-222A STIX XML (54 KB) AA26-222A STIX JSON (61 KB) Intended Audience Organizations: Government, Critical Infrastructure Sectors: Healthcare and public health, financial services and insurance, critical manufacturing and construction, transportation systems and logistics, government services and facilities, utilities, academia, media and communications, retail, and professional and nonprofit services. Roles: Cybersecurity architects, defensive cybersecurity analysts, vulnerability analysts, systems administrators, and security systems managers. Introduction Note: This joint Cybersecurity Advisory is part of an ongoing #StopRansomware effort to publish advisories for network defenders that detail various ransomware variants and ransomware threat actors. These #StopRanso CVEs: CVE-2024-55591, CVE-2025-24472. CISA KEV/exploitation signal detected. Vendors: Microsoft, Fortinet, GitHub. DORA relevance: high.
Por qué importa
Explotación activa confirmada. Riesgo material para entornos expuestos.
Acción recomendada
Comprueba la exposición a CVE-2024-55591, CVE-2025-24472 en el inventario de activos y las herramientas de vulnerabilidades.
August 2026 Patch Tuesday: Updates and Analysis | CrowdStrike Blog Featured August 2026 Patch Tuesday: One Exploited Zero-Day and 62 Critical Vulnerabilities Among 415 CVEs Aug 11, 2026 CrowdStrike Threat Hunts for Shell Command Obfuscation on VMware ESX Aug 07, 2026 Expanding AI Benchmarks in Cybersecurity Beyond Vulnerability Discovery Aug 06, 2026 Secure Agent Harness Execution: Preventing Escape Aug 04, 2026 Recent August 2026 Patch Tuesday: One Exploited Zero-Day and 62 Critical Vulnerabilities Among 415 CVEs Aug 11, 2026 CrowdStrike Threat Hunts for Shell Command Obfuscation on VMware ESX Aug 07, 2026 Expanding AI Benchmarks in Cybersecurity Beyond Vulnerability Discovery Aug 06, 2026 Secure Agent Harness Execution: Preventing Escape Aug 04, 2026 Video Video Highlights the 4 Key Steps to Successful Incident Response Dec 02, 2019 Helping Non-Security Stakeholders Understand ATT&CK in 10 Minutes or Less [VIDEO] Feb 21, 2019 Analyzing Targeted Intrusions Through the ATT&CK Framework Lens [VIDEO] Jan 22, 2019 Qatar’s Commercial Bank Chooses CrowdStrike Falcon®: A Partnership Based on Trust [VIDEO] Aug 20, 2018 Category Agentic SOC Agentic SOC How AI-leading Security Teams Are Building the Agentic SOC 07/06/26 New Claude Integration Brings Audit Data into the Falcon Platform 05/21/26 How Charlotte AI AgentWorks Fuels Security's Agentic Ecosystem 03/25/26 CrowdStrike Services and Agentic MDR Put the Agentic SOC in Reach 03/24/26 Cloud & Application Security Cloud & Application Security Falcon Cloud Security July 2026 Release: Helping Security Teams Move Faster in the Cloud 07/29/26 Falcon Cloud Security June 2026 Release: Updates for Azure and Google Cloud 06/29/26 94% of Organizations Report Cloud Breaches: CrowdStrike State of CDR Survey 06/22/26 CrowdStrike Named an Innovation and Growth Leader in the 2026 Frost Radar™: Cloud and Application Runtime Security 06/11/26 Threat Hunting & Intel Threat Hunting & Intel CrowdStrike 2026 Threat Hunting Report: Exploit CVEs: CVE-2026-68820, CVE-2026-62832, CVE-2026-62737, CVE-2026-72971, CVE-2026-62815. CISA KEV/exploitation signal detected. Vendors: Microsoft, Google, CrowdStrike, VMware, Apple. DORA relevance: high.
Por qué importa
Explotación activa confirmada. Riesgo material para entornos expuestos.
Acción recomendada
Comprueba la exposición a CVE-2026-68820, CVE-2026-62832, CVE-2026-62737 en el inventario de activos y las herramientas de vulnerabilidades.