CyberComplianceAI
InicioNoticiasIntel Center
CyberForoPrecios
Acceder
The Pulse · Live Intelligence Feed

Intel Center

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 gravedad, actualidad y coincidencias con tu perfil personal de inteligencia.

Para análisis editorial y noticias generales visita Noticias.

Priorizado con IA

La priorizacion, resumen y accion recomendada pueden estar enriquecidos por IA y heuristicas. La fuente original permanece visible para verificacion.

Señales registradas · last 7d
Señales (ventana)5
Última detecciónhace 4 h
Monitorizado porintelligence scouter
1signals
Acción Requerida
Explotados & KEV
Ventana24h7d30d7d / 30d solo en ProSeveridadCríticaAltaLimpiar filtros
Fabricante mencionadoMicrosoft22Siemens16Google12Palo Alto Networks11Check Point8Linux8GitHub8PHP7GitLab5Apache4

Priority Command Strip

What your team should look at right now

1 señal críticas
  1. Action RequiredImmediate6d

    GitLab Patch Release: 19.5.5, 19.4.7

    Severidad crítica con vector accionable a corto plazo.

    GitLab Security Releases · GitLab · KubernetesReview signal
All5Action Required1Altas y críticas0Vendor Advisories1Monitor3
INMEDIATOCríticoAviso de fabricanteACTION REQUIREDInteligencia operacional

GitLab Patch Release: 19.5.5, 19.4.7

On November 12, 2026, we released versions 19.5.5, 19.4.7 for GitLab Community Edition and Enterprise Edition. These versions resolve a number of regressions and bugs. This patch release does not include any security fixes. GitLab Orbit is now available in GitLab 19.4 and 19.5 Due to popular demand, this patch release brings GitLab Orbit to GitLab 19.4 and 19.5, so you can start using Orbit without upgrading to 19.6 first. Patch releases normally contain only bug and security fixes. Adding Orbit is a one-time exception, so it ships on its own in this out-of-band patch release. Orbit is off by default, so nothing changes for instances that don’t turn it on. To use Orbit, install it as a separate service on Kubernetes, turn it on in your GitLab configuration, and then turn it on for each top-level group. For details, see Set up GitLab Orbit. If you turn on Orbit on GitLab 19.4.7 and then later upgrade to 19.5, upgrade to 19.5.5 or later. Earlier 19.5 releases do not include these Orbit changes. Later patch releases for 19.4 and 19.5, including security releases, also include them. GitLab Community Edition and Enterprise Edition 19.5.5 Backport of ‘Retry GCS default credentials after a latched metadata timeout’ Backport of ‘Skip code navigation lookups when a project has no LSIF artifacts’ into 19.5 [19.5] Backport of ‘Update oj to 3.17.8 to fix native memory-safety bugs’ Backport of ‘Stop relation batch export spec leaking a foo directory’ Backport of ‘Map sast_iac scanner to sast in approval policy rules’ Backport of ‘Bump premailer to 1.27.0 to stop css_parser deprecation warnings’ (19.5) [19.5] Reapply the Orbit feature backports 19.4.7 Backport of ‘Skip code navigation lookups when a project has no LSIF artifacts’ into 19.4 Backport of ‘Retry GCS default credentials after a latched metadata timeout’ [19.4] Backport of ‘Update oj to 3.17.8 to fix native memory-safety bugs’ Backport of ‘Map sast_iac scanner to sast in approval policy rules’ Backport of ‘Stop relatio

Filtered for operational relevance. Powered by a curated catalog of vulnerability, CERT, vendor and threat-intelligence sources.View methodology →

CyberComplianceAI

¿Quieres esto priorizado para tu rol cada mañana?

El Morning Brief Pro filtra estas señales por tu rol (CISO, SecOps, risk), sector y framework prioritario, y las convierte en acciones recomendadas listas a las 7:00.

Probar Morning Brief Pro →Ver precio

¿Aún no quieres Pro? Recibe el resumen de cumplimiento gratis cada semana.

Sin señales clasificadas en esta categoría dentro de la ventana seleccionada. Catálogo histórico abajo.

Altas y críticas

Sin señales clasificadas en esta categoría dentro de la ventana seleccionada.

1signals
Advisories de Vendor
También en el Intel CenterMonitor3
Apple4
Zoom4
Cisco3
Node.js3

Por qué importa

Severidad crítica con vector accionable a corto plazo.

Acción recomendada

Avisa a los owners de los stacks GitLab, Kubernetes.

Vendors:GitLabKubernetesCISO · SecOps · Incident Response · Vulnerability Management
Publicado
12 nov 2026, 00:00
Actualizado
12 nov 2026, 12:00
Detectado
12 nov 2026, 12:00
Fuente
GitLab Security Releases
Referencia técnica
Original advisory
GitLab Security Releases
Prioridad · 37/100published <7d (+25) · critical severity (+25) · source authority (+2) · updated <7d (+3 cap)
hace 6 días
Vendor AdvisoriesMEDIAMedioAviso de fabricanteNEWInteligencia operacional

GitLab Patch Release: 19.5.6, 19.4.8, 19.3.9

On November 16, 2026, we released versions 19.5.6, 19.4.8, 19.3.9 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here. For security fixes, the issues detailing each vulnerability are made public on our issue tracker 90 days after the release in which they were patched. We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post. Recommended Action We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible. When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected. Security fixes Table of security fixes Title Severity Cross-site Scripting issue in wiki pages impacts GitLab CE/EE High Cross-site Scripting issue in Error Tracking impacts GitLab CE/EE High Incorrect Authorization issue in CI/CD pipeline jobs impacts GitLab CE/EE High Incorrect Authorization issue in workspaces impacts GitLab CE/EE High NULL Point

Por qué importa

Advisory oficial de GitLab. Validar versiones desplegadas.

Acción recomendada

Avisa a los owners de los stacks GitLab.

Vendors:GitLabVulnerability Management · IT Ops
Mapeo regulatorio · riesgo 40

El aviso identifica vulnerabilidades altas en GitLab y recomienda aplicar parches de inmediato, por lo que debe evaluarse como información relevante para la gestión de vulnerabilidades TIC.

DORA · Art. 13 Learning and evolving (direct)
Publicado
16 nov 2026, 00:00
Actualizado
17 nov 2026, 04:00
Detectado
17 nov 2026, 04:00
Fuente
GitLab Security Releases
Referencia técnica
Original advisory
GitLab Security Releases
Prioridad · 24/100published <7d (+25) · medium severity (+5) · source authority (+2) · updated <7d (+3 cap)
hace 1 día
MonitorMONITORAltoIncidente (prensa)NEWInteligencia operacional

Optimizely confirms massive cyberattack on customer websites injected stealer malware

Attackers apparently from China used an authentication security hole within the popular Optimizely AI platform for marketers to steal from at least 178 sites owned by some of the planet’s largest companies. Named victims featured vendors including Zoom, Paychex, Equifax, and GitLab, and end-user enterprises including Starbucks, IKEA, Mattel, American Eagle, Air France, Mutual of Omaha, Heineken, Home Chef, Cinnabon, American Eagle, Levi, Costco and HSBC. Salesforce issued a statement confirming that it had also been impacted by the attack. “Salesforce is investigating unauthorized modifications to scripts provided by Optimizely and used on certain Salesforce websites,” it wrote in an email statement. “As a precaution, Salesforce is confirming that Optimizely scripts are disabled across preview and production instances.” The attacks were discovered by UK-based security researcher Scott Helme, the founder of Report URI, who said in an interview that his team had confirmed 178 victims, but that there could be more. “That’s the number that we directly observed and that all carried the same infection,” he said. Helme published a report about the attacks on Monday, in which he described an attack methodology where an Optimizely capability in its Web Experimentation product facilitating adding members to a site’s development team was leveraged to insert malware into the sites. “The malware was a multi-purpose kit. It swapped cryptocurrency wallet addresses for the attacker’s, skimmed payment cards, stole cookies and screenshots, and on iPhones and iPads it delivered the Coruna and DarkSword iOS exploit kits,” Helme wrote. “The important lesson here is that trusted JavaScript doesn’t always remain trustworthy. A website can be compromised through a third-party dependency without its own code or infrastructure ever being breached.” Optimizely customers load a JavaScript “snippet” from Optimizely’s CDN onto their sites which contains Optimizely code, the customer’s A/B tests,

Por qué importa

Señal informativa — sin acción inmediata.

Acción recomendada

Avisa a los owners de los stacks Apple, GitLab, Salesforce, Zoom.

Vendors:AppleGitLabSalesforceZoomCISO · SecOps
Mapeo regulatorio · riesgo 78

El ataque a un proveedor TIC comprometió scripts de numerosos sitios y pudo exponer datos, por lo que las entidades financieras afectadas deben gestionar, detectar y clasificar el incidente conforme a DORA.

DORA · Art. 10 Detection (direct) · Art. 17 ICT-related incident management process (direct) · Art. 18 Classification of ICT-related incidents and cyber threats (direct)
Publicado
18 nov 2026, 01:22
Actualizado
18 nov 2026, 02:00
Detectado
18 nov 2026, 02:00
Fuente
CSO Online
Referencia técnica
Original advisory
CSO Online
Prioridad · 42/100published <24h (+40) · high severity (+15) · source authority (+2) · updated <24h (+5 cap)
hace 4 horas
MonitorMONITORAltoIncidenteNEWInteligencia operacional

Optimizely hack infected CNN, Fox News, BBC, Salesforce sites with malware

A suspected supply chain attack targeting Optimizely has led to malicious JavaScript being loaded on numerous popular websites, including Zoom, CNN, Fox News, BBC, Salesforce, and GitLab, exposing visitors to scripts designed to steal cryptocurrency and payment information and exploit vulnerabilities in iOS devices. [...]

Por qué importa

Señal informativa — sin acción inmediata.

Acción recomendada

Avisa a los owners de los stacks Apple, GitLab, Salesforce, Zoom.

Vendors:AppleGitLabSalesforceZoomCISO · SecOps
Mapeo regulatorio · riesgo 55

El ataque a la cadena de suministro y la carga de scripts maliciosos pueden exigir detección, gestión y clasificación de incidentes DORA, aunque no se confirma el impacto en una entidad financiera concreta.

DORA · Art. 1 Subject matter (direct) · Art. 10 Detection (direct) · Art. 13 Learning and evolving (direct)
Publicado
17 nov 2026, 02:12
Actualizado
17 nov 2026, 09:01
Detectado
17 nov 2026, 09:01
Fuente
BleepingComputer
Referencia técnica
Original advisory
BleepingComputer
Prioridad · 32/100published <7d (+25) · high severity (+15) · source authority (+2) · updated <24h (+5 cap)
hace 21 horas
MonitorMONITORAltoIncidenteNEWInteligencia operacional

Optimizely supply chain attack infects major brands' sites with malware

A suspected supply chain attack targeting Optimizely has led to malicious JavaScript being loaded on numerous popular websites, including Zoom, CNN, Fox News, BBC, Salesforce, and GitLab, exposing visitors to scripts designed to steal cryptocurrency and payment information and exploit vulnerabilities in iOS devices. [...]

Por qué importa

Señal informativa — sin acción inmediata.

Acción recomendada

Avisa a los owners de los stacks Apple, GitLab, Salesforce, Zoom.

Vendors:AppleGitLabSalesforceZoomCISO · SecOps
Mapeo regulatorio · riesgo 45

El ataque a la cadena de suministro y el posible robo de información requieren valorar la gestión y clasificación del incidente conforme a DORA si afecta a una entidad financiera.

DORA · Art. 1 Subject matter (direct) · Art. 17 ICT-related incident management process (direct) · Art. 18 Classification of ICT-related incidents and cyber threats (direct)
Publicado
17 nov 2026, 02:12
Actualizado
17 nov 2026, 04:00
Detectado
17 nov 2026, 04:00
Fuente
BleepingComputer
Referencia técnica
Original advisory
BleepingComputer
Prioridad · 31/100published <7d (+25) · high severity (+15) · source authority (+2) · updated <7d (+3 cap)
hace 1 día

Cobertura de fuentes degradada

64 de 72 fuentes elegibles del scouter tienen una lectura correcta en las últimas 24 h. 8 registran fallos; 0 no tienen un éxito registrado. Estas categorías pueden solaparse.

El scouter está programado cada hora. Una ejecución o la ausencia de señales no garantiza cobertura completa ni ausencia de exposición.

Estado consultado: 18/11/2026, 5:52:14 UTC · catálogo del scouter; otros conectores se actualizan por separado.