ConnectWise completed restoration of its former SkyKick service on November 19. Backups for a Microsoft 365 tenant resume only after its partner reauthorizes the connection.
Actuar ahoraIncidente confirmado por el proveedor
Reauthorize each outstanding Microsoft 365 tenant in the Cloud Services portal. Verify a successful new snapshot for each tenant and record the interval between its last backup before the interruption and its first backup after recovery.
Oracle lists 17.0.21.0.3 as affected on this line.
Corrección: 17.0.21.1+4
Oracle JDK 21
Oracle lists 21.0.13.0.3 as affected on this line.
Corrección: 21.0.13.1+4
Oracle JDK 25
Oracle lists 25.0.5.0.3 as affected on this line.
Corrección: 25.0.5.1+4
Oracle JDK 27
Oracle lists 27.0.1.0.3 as affected on this line.
Corrección: 27.0.1.1+4
Oracle Java SE 8 performance release
8u511b33-perf listed by Oracle.
Corrección: November 2026 Oracle patch for the installed edition and release line
Oracle GraalVM for JDK
17.0.21.0.3 and 21.0.13.0.3 listed by Oracle.
Corrección: November 2026 Oracle patch for the installed edition and release line
Oracle GraalVM Enterprise Edition
21.3.20.0.3 listed by Oracle.
Corrección: November 2026 Oracle patch for the installed edition and release line
Cisco appliances with bundled OpenJDK
Cisco confirms Catalyst Center, Secure Workload, Intersight Virtual Appliance and other listed products on susceptible hardware. Optical Network Planner is affected starting with 26.4.1. IOS XE and UCS Central are unaffected.
Corrección: Check the Cisco product table and bug ID. Revision 1.2 names planned releases for several products, including Secure Network Analytics 7.6.0, with availability still to be determined.
Revisar esta semanaAtaques no establecidos
Identify exposed Java services on processors with AVX-512 VBMI. Patch standalone runtimes and verify the running JVM. For Cisco appliances, match the product to its own release status before scheduling maintenance.
Requiere acciones adicionales · Depende de la aplicación o configuraciónVer aviso
HTTP/2 enabled on upstream releases from 1.9.5 through 1.30.6, or from 1.31.0 through 1.31.8.
Corrección: 1.30.7 or later on the stable branch · 1.31.9 or later on the mainline branch · For distribution packages, verify the backport for this CVE.
NGINX Plus
HTTP/2 enabled on an affected Plus build. F5 lists separate corrections for 37.0.x and the branch starting at 37.1.0.
Corrección: 37.0.8.1 on the 37.0.x branch · 37.3.0.1 on the newer branch · For older Plus releases, confirm the supported upgrade path with F5.
Actuar ahoraAtaques no establecidosExploit demostrado
Identify where NGINX accepts HTTP/2. Apply the corrected release for your branch or the distribution package that fixes this CVE, then verify the workers serving traffic.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Identify applications that bundle axis:axis. Migrate to a supported SOAP engine or use a build with Apache’s referenced patch applied. Verify the deployed library.
Requiere acciones adicionales · No requiere autenticaciónVer aviso
Follow BerriAI’s recommendation to upgrade to 1.83.11 or later. If an upgrade must wait, block the custom code test endpoint at the reverse proxy or API gateway.
Corrección disponible · Requiere acceso a una cuentaVer aviso
Identify public survey servers and confirm the corrected build for the installed branch with the consortium. Restrict access to vulnerable surveys until the server is updated.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
New research identifies six flaws in Danfoss AK-SM800A through firmware 5.3.2; passwords and Strict Mode alone are insufficient. Remove public administration access and replace unsupported XWEB EVO systems while investigating the separately confirmed refrigeration attacks.
Actuar ahoraIncidente documentado por múltiples fuentes
Remove public administration access. Verify safe setpoints, actual temperatures and alert delivery with operations; secure maintenance access and plan recovery for the exact equipment.
Update the installed Puppet Enterprise branch to 2023.8.13, 2025.12.1 or 2026.0.1 and restart Puppet Server. Review certificate issuance and suspicious service activity.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Builds from 16.0.0 before 16.0.20326.20278. The attacker needs site read access and membership in the relevant Secure Store target application.
Corrección: KB5002945 — 16.0.20326.20278
Revisar esta semanaSin ataques reportados
Apply KB5002945 to SharePoint Server Subscription Edition after checking Workflow Manager prerequisites. Verify build 16.0.20326.20278 and review Secure Store target application membership.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
18.x before 18.7. Exploitation requires permission to create database objects.
Corrección: 18.7
PostgreSQL 17
17.x before 17.12. Exploitation requires permission to create database objects.
Corrección: 17.12
PostgreSQL 16
16.x before 16.16. Exploitation requires permission to create database objects.
Corrección: 16.16
PostgreSQL 15
15.x before 15.20. Exploitation requires permission to create database objects.
Corrección: 15.20
PostgreSQL 14
14.x before 14.25. Exploitation requires permission to create database objects. PostgreSQL 14 is now outside upstream support.
Corrección: 14.25
Revisar esta semanaAtaques no establecidos
Install the corrected minor release for your PostgreSQL branch, restart the server and verify its running version. Review which application accounts can create database objects.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
2012.2.710 through 2026.3.1015. Crafted filter parameters reach affected parsing code; anonymous access is possible where the application exposes that endpoint.
Corrección: 2026.4.1111
Telerik UI for ASP.NET Core
2015.1.318 through 2026.3.1015. An accessible endpoint uses DataSourceRequest model binding; deeply nested filters can trigger uncontrolled recursion.
Corrección: 2026.4.1111
Revisar esta semanaAtaques no establecidos
Update the affected Telerik server package to 2026.4.1111 or later, align client assets with that version and redeploy. Test filter endpoints and review parsing failures.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
ConnectWise says its investigation is complete, but partner action remains required. Disable the identified extensions, update ScreenConnect servers and verify technician clients run 26.6.5 or later; existing compromise still needs investigation.
Actuar ahoraIncidente confirmado por el proveedorCISA KEV
Keep the identified extensions disabled, update ScreenConnect to the latest supported version and verify every technician client is at least 26.6.5. Review activity and invalidate sessions using the vendor guidance.
Plaid marked its Chase connection incident resolved on November 17 at 00:34 UTC, following transaction delays Chase attributed to a technical issue. Plaid’s recovery does not verify every banking function or uncertain transaction.
Actuar ahoraIncidente confirmado por el proveedor
Validate Chase connections and account data freshness. Reconcile uncertain transaction results before retrying, then resume dependent automation after checking its inputs and queued operations.
Servers without HF3, including HF2 build 2026.4.1.26. Older versions may require an intermediate upgrade through the vendor’s supported path.
Corrección: 2026.4 HF3, build 2026.4.1.39. Includes HF2 fixes and the additional HF3 corrections.
Agents and Probes, including hosted deployments
Agents and Probes not yet upgraded to 2026.4.1 HF3, including components previously upgraded to HF2 and those connected to hosted servers.
Corrección: Upgrade all Agents and Probes to 2026.4.1 HF3. When coming from before HF2, retain the HF2 Agent-before-Probe compatibility requirements.
Legacy API, Intune integration and later N-central disclosures
Legacy API abuse requires that API enabled. N-able describes endpoint access as a prerequisite for Agent impersonation. Remaining permission issues require authenticated access.
Corrección: HF3 permanently blocks Legacy APIs. Intune remains blocked and remote control other than Take Control remains disabled; installing HF3 does not restore those functions.
Actuar ahoraIntentos de ataque observados
Upgrade servers you operate to 2026.4.1.39 through the supported path, then update every Agent and Probe to HF3. Review inactive Agents after reconnection. Legacy API remains blocked; Intune and remote control limitations remain.
Requiere acciones adicionales · Depende de la aplicación o configuraciónVer aviso
Affected 6.12 kernels before 6.12.117; distribution backports must be checked separately
Corrección: 6.12.117 or later in this branch
Upstream Linux 6.18
Affected 6.18 kernels before 6.18.61; distribution backports must be checked separately
Corrección: 6.18.61 or later in this branch
Upstream Linux 7.2
Affected 7.2 kernels before 7.2.15; distribution backports must be checked separately
Corrección: 7.2.15 or later in this branch
Upstream Linux 7.3
Affected 7.3 kernels before 7.3.2; distribution backports must be checked separately
Corrección: 7.3.2 or later in this branch
Debian trixie linux source package
Earlier packages without the distribution correction
Corrección: 6.12.115-1; security package 6.12.117-1 is listed fixed at this review
Debian bookworm linux source package
6.1.176-1 and security package 6.1.192-2 are listed vulnerable at this review
Corrección: No correction listed for bookworm’s linux 6.1 source package; assess linux-6.12 separately
Debian bookworm linux-6.12 source package
Earlier packages without the distribution correction
Corrección: 6.12.115-2~deb12u1; security package 6.12.117-1~deb12u1 is listed fixed at this review; DLA-4904-1
Revisar esta semanaAtaques no establecidos
Install the correction for the exact distribution package and kernel branch, reboot and verify the running kernel. Debian lists linux-6.12 6.12.115-2~deb12u1 as fixed for bookworm; its linux 6.1 packages remain vulnerable.
Requiere acciones adicionales · Depende de la aplicación o configuraciónVer aviso
CNA identifies releases through 3.1.4, with ADMIN_PASSWORD configured and website access available to an attacker.
Corrección: 3.1.5 includes the authorization correction; maintainer commit 28c27e30f6d3a10e38fe9c54bb52f57ccf70d027 remains an alternative for supported builds.
Revisar esta semanaSin ataques reportados
Update the Modules website to 3.1.5 or apply the verified maintainer correction through your supported deployment process. Restrict access and confirm anonymous users cannot change external tools.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Installed kernels without the applicable CVE-2026-98432 security update.
Corrección: Apply the kernel update for the installed branch and reboot. Locked AL2023 releases must use 2023.12.20261102 or later.
EKS / ECS on EC2
Instances running affected host kernels; a corrected image configuration alone does not update existing nodes.
Corrección: EKS-optimized AL2023 AMI v20261031 · ECS-optimized AMI 20261031 · Replace affected nodes or apply the supported kernel update and reboot.
RHEL 8 / 9 / 10
Affected kernel packages; choose the erratum for the exact product, minor branch and support stream.
Corrección: RHEL 8 kernel: RHSA-2026:93414; kernel-rt: RHSA-2026:93415 · RHEL 9 kernel: RHSA-2026:93412 · RHEL 10 kernel: RHSA-2026:93413 · RHEL 10.3: RHSA-2026:98608, kernel-0:6.12.0-264.14.1.el10_3 · Extended streams have separate errata; verify the Red Hat CVE package table before applying a correction.
Amazon MQ for RabbitMQ / ActiveMQ
Existing brokers before the updated host-image rollout.
Corrección: Brokers created after November 2, 2026, 12:16 UTC use the patched kernel; existing brokers update at maintenance.
Amazon GameLift Servers managed Linux fleets
Container fleets created before November 2, 2026, 21:06 UTC; managed EC2 fleets created before November 3, 2026, 01:55 UTC. Existing fleets retain their creation AMI.
Corrección: AWS confirms corrected Amazon Linux 2/2023 AMIs in all Regions. Create replacement fleets and migrate traffic. Windows fleets are unaffected; Anywhere operators must patch their own OS and reboot.
Red Hat OpenShift 4.12 / CoreOS
Deployments without the RHSA-2026:95416 correction.
Corrección: RHSA-2026:95416: openshift/ose-rhel-coreos-8:412.86.202611041725-0. Apply the supported cluster update for this branch and verify running nodes.
Red Hat OpenShift 4.13 / CoreOS
Deployments without the RHSA-2026:95745 correction.
Corrección: RHSA-2026:95745: openshift/ose-rhel-coreos-9:413.92.202611041925-0. Apply the supported cluster update for this branch and verify running nodes.
Red Hat OpenShift 4.14 / CoreOS
Deployments without the RHSA-2026:95508 correction.
Corrección: RHSA-2026:95508: openshift/ose-rhel-coreos-9:414.92.202611040941-0. Apply the supported cluster update for this branch and verify running nodes.
Red Hat OpenShift 4.15 / CoreOS
Deployments without the RHSA-2026:95755 correction.
Corrección: OpenShift 4.15.71; RHSA-2026:95755 CoreOS image openshift/ose-rhel-coreos-9:415.92.202611051005-0. RHSA-2026:95754 covers release RPMs; installing conmon or cri-o alone does not establish that the running kernel is corrected. Complete the supported cluster update and verify nodes.
Red Hat OpenShift 4.16 / CoreOS
Deployments without the RHSA-2026:95229 correction.
Corrección: RHSA-2026:95229: openshift/ose-rhel-coreos-9:416.94.202611031928-0. Apply the supported cluster update for this branch and verify running nodes.
Red Hat OpenShift 4.17 / CoreOS
Deployments without the RHSA-2026:96282 correction.
Corrección: RHSA-2026:96282: openshift/ose-rhel-coreos-9:417.94.202611061051-0. Apply the supported cluster update for this branch and verify running nodes.
Red Hat OpenShift 4.18 / CoreOS
Deployments without the RHSA-2026:95104 correction.
Corrección: OpenShift 4.18.60 container images under RHSA-2026:95104; CoreOS package openshift/ose-rhel-coreos-9:418.94.202611030931-0. Apply the supported cluster update when offered in the appropriate channel and verify running nodes. RPM packages are covered separately by RHSA-2026:95103.
Red Hat OpenShift 4.19 / CoreOS
Deployments without the RHSA-2026:95523 correction.
Corrección: RHSA-2026:95523: openshift/ose-rhel-coreos-9:4.19.9.6.202611041921-0. Apply the supported cluster update for this branch and verify running nodes.
Red Hat OpenShift 4.20 / CoreOS
Deployments without the RHSA-2026:95377 correction.
Corrección: RHSA-2026:95377: openshift/ose-rhel-coreos-9:4.20.9.6.202611042002-0. Apply the supported cluster update for this branch and verify running nodes.
Red Hat OpenShift 4.21 / CoreOS
Deployments without the RHSA-2026:95408 correction.
Corrección: RHSA-2026:95408: openshift/ose-rhel-coreos-9:4.21.9.6.202611042115-0. Apply the supported cluster update for this branch and verify running nodes.
Red Hat OpenShift 4.22 / CoreOS 9
Deployments without the RHSA-2026:95346 correction.
Corrección: OpenShift 4.22.22 (RHSA-2026:95346); corrected image openshift/ose-rhel-coreos-9:4.22.9.8.202611032353-0. Verify the completed cluster update and running nodes.
Red Hat OpenShift 5.0 / CoreOS
Deployments without the RHSA-2026:94537 correction.
Corrección: RHSA-2026:94537: openshift/ose-rhel-coreos-9:5.0.10.2.202611022203-0. Apply the supported cluster update for this branch and verify running nodes.
Red Hat Enterprise Linux AI 3
Kernel remains listed as affected in the reviewed Red Hat CVE data.
Corrección: No corrected package is listed for RHEL AI 3 in the reviewed data. Track this product separately; the RHEL and OpenShift corrections do not establish a fix for it.
AWS Elastic Beanstalk on Amazon Linux 2023
Environments on platform versions preceding the November 4 security release.
Corrección: November 4, 2026 platform release using AMI 2023.12.20261102. Managed updates apply during maintenance; otherwise update the platform.
Bottlerocket
Images preceding the corrected release.
Corrección: Bottlerocket 1.68.1 AMIs, released October 31, 2026.
Amazon RDS / Aurora
Database hosts covered by AWS bulletin 2026-160.
Corrección: AWS confirms worldwide mitigation and an available database OS patch. Apply the patch and keep database ports inaccessible from the internet. Mitigation does not establish that a customer's OS patch is installed.
Amazon ElastiCache
Clusters covered by AWS bulletin 2026-160; worldwide mitigation deployment remains in progress.
Corrección: elasticache-20261106-arm or elasticache-20261106-intel, as applicable, is available. Apply the service update; availability does not mean the update is installed on your cluster.
Amazon MemoryDB
Clusters covered by AWS bulletin 2026-160; worldwide mitigation deployment remains in progress.
Corrección: memorydb-20261106-arm is available. Apply the service update; availability does not establish customer installation or worldwide mitigation completion.
Amazon Neptune / Redshift
Managed database services covered by the AWS bulletin.
Corrección: Neptune: keep database ports inaccessible from the internet. · Redshift: AWS reports all customers mitigated; this is not a claim about every other database service.
AWS Storage Gateway
Supported gateways awaiting the updated release.
Corrección: Updates are available through the console or API. AWS recommends updating manually now rather than waiting for maintenance.
AWS CodeBuild Linux build hosts
Standard hosts before the completed rollout, and customer fleets using an uncorrected custom AMI.
Corrección: Standard on-demand x86 hosts: all commercial Regions November 5; ARM November 6. Reserved x86/ARM container and EC2 compute: November 9. Rebuild custom AMIs with the corrected kernel and update the fleet. Build images and buildspecs do not need replacement for this kernel fix.
AWS Deep Learning AMIs
Instances using an uncorrected kernel; availability differs by OS.
Corrección: Amazon Linux 2023: corrected DLAMIs available; replace instances or update the kernel and reboot. · Ubuntu 22.04/26.04: rollout in progress, not yet confirmed in all Regions. Ubuntu 24.04 corrected DLAMIs remain pending.
Amazon FSx
Affected file systems created before November 12, 2026, 16:00 UTC that have not yet received the patch.
Corrección: AWS confirms worldwide patch availability. New file systems launched after the cutoff include it; existing systems update during their next weekly maintenance window. Move the window earlier to apply it sooner.
AWS Parallel Computing Service (PCS)
Compute and login nodes with an affected kernel; controller remediation does not update these instances.
Corrección: AWS patched all PCS Slurm controllers by November 1. For AL2023 compute node groups, use the corrected x86_64 or arm64 sample AMIs released October 29. Rebuild custom AMIs with the fix, or update running kernels and reboot. · PCS DLAMIs based on Ubuntu 24.04 remain pending in the reviewed bulletin; do not treat the AL2023 sample AMI release as an Ubuntu correction.
AWS RTB Fabric and customer endpoints
AWS managed infrastructure is corrected; Linux instances sending or receiving traffic through RTB Fabric require separate kernel verification.
Corrección: AWS reports infrastructure updates complete with no action for RTB Fabric itself. Customers remain responsible for patching their own Linux endpoints.
Revisar esta semanaAtaques no establecidosExploit demostrado
Identify affected running kernels and reachable listeners. Apply the correction for the installed distribution and branch, reboot where required, and verify the active kernel or replacement nodes.
Requiere acciones adicionales · No requiere autenticaciónVer aviso
Microsoft’s public dashboard reports Available, and both AI connector incidents are resolved. Microsoft also observed phishing emails impersonating outage notices; reconcile queued work and verify recovery messages through trusted channels.
Actuar ahoraIncidente confirmado por el proveedor
Reconcile uncertain mail, calendar and connector operations before retrying. Verify recovery notices in the Microsoft 365 admin center and investigate clicks on suspicious restore links.
Before 1.29, according to the CNA records; hosting-account access can reach remaining user API escalation paths.
Corrección: 1.29 completes the ten-CVE fixes; use 1.30.1 or a later supported security release
Actuar ahoraAtaques no establecidosExploit demostrado
Install the current supported CWP release, restrict panel access and verify the installed code. Include the OAuth protections introduced in 1.30.14 and verify completion of the automatic client-secret rotation.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Malicious LiteLLM 1.107.0 artifacts require credential rotation and clean rebuilds. Newer releases use keyless cosign; earlier images retain key signatures, including compromised images signed with the old key.
Actuar ahoraAtaques confirmados
Identify affected executions, replace accessible credentials and rebuild from a clean environment.
Cursor traced the incident to a vendor access key and credentials in historical agent traces. Notified customers need credential rotation as well as investigation of the two malicious extension versions.
Actuar ahoraIntentos de ataque observados
Review Cursor notifications and rotate the identified credentials. Investigate affected extension installations, SSH persistence and accessible sessions; uninstalling alone does not clear the host.
Microsoft, Google and Mandiant document ARTEX use in intrusions involving exposed credentials, cloud permission checks and data access. Cisco Talos adds evidence of associated infrastructure and connected tools; these reports cover different actors and outcomes.
Actuar ahoraInforme de investigación
Revoke exposed credentials and tokens, check for added application credentials and roles, and investigate cloud activity and affected hosts.
2.0.0 through 2.0.2; wrapper releases from April 6 through before July 29, 2026. Requires object creation in a schema on another connecting user’s search_path.
Corrección: 2.0.3 / wrapper release 2026-07-29
Companion modules
Check each installed module against the package ranges in the maintainer advisory.
Corrección: auth-helpers, federated-auth, iam, mysql-driver, okta and pgx-driver: 1.1.3 · aws-secrets-manager: 1.1.4; custom-endpoint: 1.0.6 · otlp and xray: 1.0.9
Revisar esta semanaSin ataques reportados
Update awssql/v2 to 2.0.3 or later and review companion module versions. Until corrected, restrict schema CREATE privileges to trusted database users.
Corrección disponible · Requiere acceso a una cuentaVer aviso
3.3.3 through releases before 7.8.0, using mongodb+srv connection strings. An attacker must be able to forge or modify the DNS SRV response.
Corrección: 7.8.0 or later
Revisar esta semanaSin ataques reportados
Update the Node.js driver to 7.8.0 or later and redeploy applications using mongodb+srv. Check DNS integrity and investigate unexpected database destinations.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
6.0.0 through 6.2.7, with labeled-response on networks of at least two linked servers.
Corrección: 6.2.7.1 · Supported Unix systems: bundle-20261107 on every server; verify the module status.
UnrealIRCd 5
The maintainer also identifies version 5 as affected and out of support.
Corrección: Migrate to a supported corrected release. Temporary guidance requires disabling labeled-response on every server and restarting; rehashing is insufficient.
Update affected 7.4 clients to 7.4.8 or later; update Windows and Windows PAM 7.2 clients to 7.2.15 or later. Check the edition and running version on each endpoint, not only the deployment console.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Dedicated Kubernetes API server proxy or standalone k8s-proxy
Deployments before 1.104.7 using a ProxyGroup with spec.type: kube-apiserver (or standalone k8s-proxy), accepting subnet routes with spec.tailscale.acceptRoutes: true and an ACL grant allowing hosts behind those routes to connect. The host exploiting this path has no Tailscale identity.
Corrección: Tailscale 1.104.7 or later in the affected proxy deployment. The operator’s in-process proxy is outside this issue; enrolled tailnet clients do not trigger the fallback.
Revisar esta semanaAtaques no establecidos
Update affected proxy deployments to Tailscale 1.104.7 or later. If subnet hosts could reach the proxy, review Kubernetes audit logs for unexpected impersonated identities.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Update NetScaler Console 14.1 to 14.1-74.34 or later. Restrict access to the console IP and review unexpected administrative access; ADC and Gateway updates use different builds.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Update 14.1 to 14.1-73.57 or 13.1 to 13.1-64.39. Use 14.1-73.58 for FIPS or 13.1-37.293 for FIPS/NDcPP; check the separate NetScaler Console correction independently.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Upgrade to 8.0.1, 7.6.8, 7.4.6 or 7.2.9 or a later corrected release in the applicable branch. Restrict FGFM access to required management peers and verify the active version.
Corrección disponible · No requiere autenticaciónVer aviso
Apply Faspex 5.0.19 PL1 and verify faspex-core is 5.0.19 (1ce4b13, Fix Pack: 1). IBM lists no workaround; review unexpected changes to administrator privileges.
Install the corrected Jumbo Hotfix for your Gaia branch and verify the socket permissions. Review DynamicCLI and authentication logs for earlier abuse; patching does not remove an existing compromise.
Requiere acciones adicionales · Requiere acceso a una cuentaVer aviso
Identify Webtop Media Transcoder versions below 1.1.22.0 and arrange the vendor’s supported Media Server upgrade. Review conversion activity and investigate possible information exposure.
Corrección disponible · Requiere acceso a una cuentaVer aviso
Update listed Gen7 devices to 7.3.4-7013 or later, and Gen8 devices to 8.2.3-8015 or later. Verify SSLVPN authentication and review earlier sessions, including use of alternate login methods.
Corrección disponible · Requiere acceso a una cuentaVer aviso
Upgrade affected BroadWorks components to RI.2026.07 or a later corrected release. Restrict OCI-P reachability and review earlier requests for signs of configuration disclosure.
Corrección disponible · No requiere autenticaciónVer aviso
AWS confirms ALB trust updates completed, while Lambda email and object signature checks have a separate rollout. Google lists corrected Firebase SDKs and plugins; affected installed apps require rebuilt releases.
Actuar ahoraCambio de confianza anunciadoFecha clave · 27 oct 2026
Replace affected certificate chains, verify trust stores and update the SDK for each platform. Rebuild and distribute affected apps; verify Lambda runtime updates and ALB authentication separately.
Brotli decompression enabled on 1.31.0–1.31.1, 1.30.0–1.30.5 or 1.29.0–1.29.8. The 1.29 branch is end of life.
Corrección: 1.31.2 · 1.30.6 · 1.29.9 (end of life)
Perl IO::Compress::Brotli
Module builds incorporating a vulnerable Brotli library; 0.023 updates the bundled library to 1.2.1.
Corrección: 0.023
PAN-OS — builds listed as corrected
PA-Series and VM-Series dataplane with both Brotli inspection and TLS/SSL decryption enabled. PAN-OS 11.1 and 10.2, Panorama and management interfaces are outside this scope. Confirm download availability for the exact branch.
Before 0.2.9; no special configuration is required for exposure.
Corrección: 0.2.9
PHP Windows builds
Windows packages with the vulnerable bundled decoder, reachable through cURL when automatic HTTP response decompression is enabled. PHP runtime version alone does not identify the dependency rebuild.
Affected runtimes; the managed service is unaffected. Node 18/20 receive no security updates.
Corrección: Base images updated: rebuild and redeploy. AWS reports both ZIP Brotli patch phases completed; verify deployed runtime and update mode.
AWS Lambda — .NET 8, 9, 10
.NET 9 is container only.
Corrección: Base images updated: rebuild and redeploy. AWS reports both ZIP Brotli patch phases completed; verify deployed runtime and update mode.
Solace Schema Registry
Versions 1.0.0–1.1.2.
Corrección: 1.1.3
Solace Micro-Integrations
Releases predating the vendor corrections completed November 1, 2026.
Corrección: Vendor reports corrected releases for all Micro-Integrations; verify the applicable integration build.
Solace Event Portal
All versions per the reviewed advisory.
Corrección: Solace reports that Event Portal exposure was resolved on October 28, 2026.
Solace Cloud console components
Multiple console components affected.
Corrección: Provider reports all affected services patched November 2, 2026.
CloudLinux OS / CentOS ELS — system Brotli
CloudLinux 7 and CentOS 7 ELS system packages. CloudLinux 8/9 fixes come from AlmaLinux repositories; check the installed distribution build. CentOS 6 has no system Brotli package.
Corrección: CloudLinux 7 / CentOS 7 ELS: brotli-1.0.9-10.el7.tuxcare.els1 · CloudLinux 8/9: verify the vendor backport in the AlmaLinux package changelog
EasyApache 4 — ea-brotli
Separate cPanel package. Decoding is reachable through EasyApache PHP cURL when CURLOPT_ENCODING is set. Apache mod_brotli output compression does not use the vulnerable decoder.
Corrección: ea-brotli-1.0.10-1: stable channel for CloudLinux 7; restart PHP-FPM and Apache. Do not remove ea-brotli: mod_security2 depends on it.
CloudLinux 7 — alt-php Brotli extensions
Static Brotli copies in brotli.so, independent of the system library. Check alt-php54–56 and alt-php70–85 separately. alt-php53-brotli-0.5.0 is unaffected: it bundles Brotli 1.0.1.
Corrección: alt-php70–85-pecl-brotli: 0.21.1-1 (Brotli 1.2.1), beta / updates-testing only · alt-php54–56-pecl-brotli: 0.14.2-7, beta / updates-testing only · Stable release pending. Evaluate beta through change control; do not enable it indiscriminately.
CloudLinux 8/9 — alt-php Brotli extensions
Affected static copies in the alt-php extensions. Updating system Brotli does not replace them.
Corrección: No corrected builds or release date published in the October 30 advisory. Track the vendor package changelog.
Palo Alto Networks — remediated SaaS services
Provider-managed services; this excludes the customer-installed Transporter Client and PAN-OS.
Corrección: Vendor reports Prisma Cloud, Strata Cloud Manager, Cortex XCor, IoT Security and Prisma SaaS remediated; no customer action for those services. This does not replace PAN-OS or Transporter Client updates.
Microsoft .NET
Affected Brotli copies in .NET runtimes; self-contained applications retain their bundled runtime.
Corrección: 8.0.33 / 9.0.22 / 10.0.14 for the corresponding branch; rebuild and redeploy self-contained applications.
AWS CloudWatch Synthetics — Python Selenium
Canary runtime includes Brotli, unlike the base Lambda Python runtime.
Corrección: syn-python-selenium-14.0 includes Brotli 1.2.1. Update affected canaries to this or a later corrected runtime.
AWS CodeBuild
Affected curated or derived images and pinned image references.
Corrección: Corrected curated images deployed in all regions. Update pinned references and rebuild custom images from corrected bases.
AWS SageMaker — XGBoost and scikit-learn
Images with vulnerable Brotli dependencies; newly available images do not update existing jobs or endpoints.
Corrección: XGBoost 3.2-0 and 3.0-5; scikit-learn 1.9-0. Use corrected images for training and redeploy endpoints. · XGBoost 3.0-5 has corrected pyarrow but its Ubuntu 20.04 system library requires Ubuntu Pro for a fix. AWS recommends 3.2-0.
AWS SageMaker — components still being corrected
Autopilot training images, Canvas, Data Wrangler and Spark processing images described in the November 9 AWS update.
Corrección: Corrections remain in progress or review. Autopilot rejects Brotli compressed columns as mitigation; that is not a completed image update.
Patch affected decoders by product and branch. Verify runtime patches and rebuilt containers. On CloudLinux, check system Brotli, ea-brotli and static alt-php copies separately.
Requiere acciones adicionales · Depende de la aplicación o configuraciónVer aviso
PA-Series, VM-Series and Panorama. No special configuration is required; internet-exposed management increases risk. Match the installed release branch.
Apply the correction for each affected product and branch, restrict exposed administration and investigate earlier activity. Update PHP runtimes and appliance firmware separately.
Requiere acciones adicionales · No requiere autenticaciónVer aviso
Versions before 26.06 when extracting specially crafted CAB archives with multiple volumes.
Corrección: 26.06
Revisar esta semanaAtaques no establecidos
Update deployed 7-Zip copies to 26.06 or a later corrected release. Verify portable copies and archive processing jobs before resuming untrusted CAB extraction.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Update Chrome to 157.0.8103.78 or later on Linux, or 157.0.8103.78/.79 or later on Windows and macOS. Relaunch and verify the executable actually running.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Before 2.1.3, with grpc-go 1.39 or later and the leader forwarding conditions in the advisory.
Corrección: 2.1.3
Docker and other Moby integrations
The maintainer lists docker/docker >=23.0.0, moby/moby/v2 <=2.0.0-beta.28 and the older swarmkit module from v1.12.1-0.20220307221335-616e8db4c3b0.
Corrección: No corrected integration version is listed in the reviewed advisory. Verify a downstream release or backport; the library fix is not evidence that an installed Docker Engine is corrected.
Revisar esta semanaAtaques no establecidos
Update Swarmkit v2 to 2.1.3 where directly embedded. For Docker deployments, verify a release or backport covering this CVE and restrict access to worker credentials and cluster management paths.
Requiere acciones adicionales · Requiere acceso a una cuentaVer aviso
Identify enabled modules and update Apache HTTP Server to 2.4.71 or a vendor package containing the fixes. Verify the running server and separately installed HTTP/2 modules.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Affected Outlook installations on 32 bit and x64 systems; corrections differ by deployed channel.
Corrección: November 10 security build for the installed channel; Current Channel 2610: 20527.20196. Consult the Microsoft release table for enterprise channels.
Microsoft Office LTSC 2021
16.0.1 up to but not including 16.0.14334.21048; 32 bit and x64 systems.
Corrección: 16.0.14334.21048
Microsoft Office LTSC 2024
16.0.0 up to but not including 16.0.17932.21140; 32 bit and x64 systems.
Apply the November 10 Office security update for each affected edition and channel. Verify the client build and investigate suspicious messages or access using your incident response process.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Chainalysis reports Reactor, KYT and Address Screening restored on November 7, followed by Data Solutions on November 10. Service recovery does not remove the need to reset affected passwords, rotate API keys and review account activity.
Actuar ahoraIncidente confirmado por el proveedor
Follow the vendor’s verified reconnection instructions, complete password resets and API key rotation, and review account activity and dependent integrations.
9.0.0 up to but not including 9.0.7 when deployed as replica set members, including shards and config servers.
Corrección: 9.0.7
MongoDB Server 8.3
8.3.0 up to but not including 8.3.16 when deployed as replica set members, including shards and config servers.
Corrección: 8.3.16
MongoDB Server 8.0
8.0.0 up to but not including 8.0.37 when deployed as replica set members, including shards and config servers.
Corrección: 8.0.37
MongoDB Server 7.0
7.0.0 up to but not including 7.0.48 when deployed as replica set members, including shards and config servers.
Corrección: 7.0.48
MongoDB Server 6.0
6.0.0 up to but not including 6.0.30 when deployed as replica set members, including shards and config servers.
Corrección: 6.0.30
MongoDB Server 5.0
5.0.0 up to but not including 5.0.35 when deployed as replica set members, including shards and config servers.
Corrección: 5.0.35
MongoDB Server 4.4
4.4.0 up to but not including 4.4.32 when deployed as replica set members, including shards and config servers.
Corrección: 4.4.32
Revisar esta semanaAtaques no establecidos
Identify replica set members, including shards and config servers. Install the corrected version for each branch, verify running versions and restrict database access to trusted networks.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Versions before 6.9.2; Xen Orchestra Appliance is affected.
Corrección: 6.9.2 stable; xo-server 5.211.2. This correction addresses VSA-2026-062 only.
VSA-2026-062: Xen Orchestra latest
Versions before 6.10.1; Xen Orchestra Appliance is affected.
Corrección: 6.10.1 latest; xo-server 5.213.1. Vates advises installations built from source to update to current master.
VSA-2026-063: Xen Orchestra and Appliance
6.10.1 and earlier, including the releases correcting VSA-2026-062.
Corrección: No fix is listed in stable or latest in the reviewed advisory. Allow VM import only to administrators and disable users with the permissions identified by Vates.
Actuar ahoraAtaques confirmados
Update the affected Xen Orchestra branch, isolate management access and restrict imports to administrators. Apply the separate permission restrictions for VSA-2026-063, which remains unpatched.
Requiere acciones adicionales · Depende de la aplicación o configuraciónVer aviso
Earlier releases in this branch; individual flaws depend on the protocol and APIs in use.
Corrección: 22.23.5
Node.js 24.x
Earlier releases in this branch; individual flaws depend on the protocol and APIs in use.
Corrección: 24.22.3
Node.js 26.x
Earlier releases in this branch; individual flaws depend on the protocol and APIs in use.
Corrección: 26.13.1
Revisar esta semanaAtaques no establecidos
Update supported runtimes to 22.23.5, 24.22.3 or 26.13.1, rebuild images and restart applications. Prioritize reachable HTTP/2 and HTTPS services; verify the runtime actually serving traffic.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Check deployed react-server-dom packages and update the affected branch to 19.0.9, 19.1.10, 19.2.9 or 19.3.1. Rebuild and redeploy the server; prioritize applications matching the response conditions.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Restrict administration access to trusted networks, install the latest firmware and verify the applicable security patch. Investigate prior exposure separately from patching.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Upgrade GPUStack to 2.2.0 or later and restrict API access. Review unexpected administrator keys, custom backends and workers; revoke credentials affected by unauthorized access.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Install OpenSSH 10.6p2 or the corrected distribution package, restart sshd and test a new connection. Preserve and review earlier logins, account changes and authorized keys on exposed systems.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Update FreeSWITCH to 1.11.3 or later. Disable inbound chat on profiles that do not need it and review earlier service activity; an inbound ACL change alone does not close this path.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Update Plex Media Server to 1.43.3.10861 or later and restrict remote access. Investigate previously exposed installations; updating alone does not remove a prior compromise.
Corrección disponible · No requiere autenticaciónVer aviso
Corrección: Remote Support 26.3.1 or later. · Alternatively, apply BT26-05-RS to 24.3.1–26.2.3. Earlier versions must upgrade first; 24.3.1 alone is not a fix.
OPSSHIELD confirms malicious cPGuard updates and exposure of server secrets. Its latest disclosure reports about 2,950 servers ran the update; this is the provider’s count.
Actuar ahoraAtaques confirmados
Install the latest corrective update, rotate exposed credentials and revoke old SSH trust. Cleanup alone does not invalidate stolen secrets.
Sekoia recovered three mobile exploit chains delivered through compromised or impersonated websites, with payloads capable of stealing cookies and private data. The report attributes Poisoned Source to APT29 with moderate to high confidence; it does not establish a count of compromised phones.
Revisar esta semanaInforme de investigaciónCISA KEV · 8
Verify OS, browser and device security updates. If evidence indicates compromise, preserve logs and coordinate session revocation and credential recovery from a trusted device; installing updates alone does not invalidate stolen sessions.
1.0 and later, before 7.6.0. Check the prerequisites for each CVE described below.
Corrección: 7.6.0
Revisar esta semanaSin ataques reportados
Update AuthPoint Authentication Gateway to 7.6.0 or a later corrected release, restrict gateway access and verify authentication and directory synchronization afterward.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
COLCERT warns about Amatera, also tracked as ACR Stealer, in Latin America. Documented campaigns use fake verification prompts and impersonated software pages to steal credentials, session cookies and development secrets from Windows systems.
Revisar esta semanaInforme de investigación
Treat requests to paste commands for a CAPTCHA as suspicious. If infection is suspected, isolate the device, preserve evidence and revoke affected sessions and rotate exposed secrets from a trusted device.
Install the firmware correction for the exact switch model, restrict access to its management interface and review available logs for unexpected activity.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Amadeus and airline notices confirm unauthorized access to reservation data, including names, booking references and itineraries. Some subsets also include contact or passport details; the provider says it found no evidence of payment or financial data access.
Revisar esta semanaIncidente confirmado por el proveedor
Check your airline’s notice and affected bookings. Verify unexpected travel messages through official channels and follow any instructions to replace booking references.
Kaspersky observed attacks using AI on education organizations in Latin America and Africa during September–October 2026. In one investigated case, attackers compromised domain administrator accounts 3–4 days after deploying the CyberStrikeAI implant.
Revisar esta semanaInforme de investigación
Check whether a compromised database host could reach privileged accounts; correlate endpoint, identity and network evidence, and confirm who will respond outside working hours.
Install WordPress 7.1.4 or a corrected release for your branch. Verify each deployed site and investigate suspicious activity around earlier core upgrades.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
BTCPay reports hot-wallet thefts targeting 2.4.1 and earlier. Its recovery guidance also covers servers upgraded from those versions after the November 1 warning.
Actuar ahoraIncidente confirmado por el proveedor
Rebuild affected hosts on a fresh VM with a new wallet and seed; updating alone is insufficient.
Binance’s preliminary findings link a malicious interview assignment and compromised internal AI tooling to wallet access; the investigation remains open. It now reports 98% replenishment of affected assets, not recovery of stolen funds.
Revisar esta semanaIncidente documentado por múltiples fuentes
Isolate interview code, review access from internal AI tools to deployment tokens and signing services, and test revocation of persistent delegations.
Mercado Bitcoin confirms a security incident and a temporary suspension of deposits and withdrawals. The provider says customers suffered no losses and no data leaked; those statements have not been independently established.
Revisar esta semanaIncidente confirmado por el proveedor
Check the official service status before scheduling transfers, reconcile pending movements and track MB’s investigation and reopening notices.
German officials received Apple alerts about targeted mercenary spyware, with notifications reported from October 29. Successful compromise, the spyware family and the attacker have not been publicly established.
Revisar esta semanaActividad de amenazas reportada
Verify any notification directly at account.apple.com and escalate immediately to specialist response. Follow Apple’s protection guidance, including Lockdown Mode; an iPhone alone does not establish exposure to this incident.
GitHub identifies npm local-commander-agent 0.3.52 as malware, with no patched version. If installed or run, treat the host as compromised and rotate secrets from a separate trusted computer.
Actuar ahoraAtaques no establecidos
Isolate affected hosts, preserve evidence and rotate reachable secrets from a trusted computer; investigate before restoring service.
Install the latest supported branch patch, verify the running version and investigate the CI/CD indicators in the vendor advisory. Do not downgrade to an older minimum fix.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
All versions according to Sophos; the stated execution path requires email proxy scanning.
Corrección: Exceptional manual patch referenced by Sophos KBA-000049692; package identifier and installation steps not verified.
Actuar ahoraAtaques no establecidos
Follow Sophos KBA-000049692 to obtain and manually install the exceptional patch, and plan migration to a supported firewall. The installation procedure still needs verification.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Install the ESX correction for the deployed branch and platform. Review administrative access and available external telemetry; missing host log entries do not rule out malicious activity.
Corrección disponible · Requiere acceso a una cuentaVer aviso
Apply the kernel fix for your distribution, preserve evidence where compromise is suspected and activate the corrected kernel using the distributor procedure. Verify the running kernel after remediation.
Corrección disponible · Depende de la aplicación o configuraciónVer aviso
Update to 0.8.6 or later and rotate credentials present in environments of agents that loaded the environment tool. If upgrading is not possible immediately, remove the tool.
Requiere acciones adicionales · Depende de la aplicación o configuraciónVer aviso
APSB26-73 lists 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, 2.4.6-p15 and earlier, 2.4.5-p17 and earlier, and 2.4.4-p18 and earlier. These base levels are not proof that the isolated fix is applied.
Corrección: Applicable July 2026 isolated security patch for the installed branch and components; verify application, including delivery through cloud-patches.
Magento Open Source
APSB26-73 lists 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, and 2.4.6-p15 and earlier. Do not infer that unsupported releases are safe.
Corrección: Applicable July 2026 isolated security patch for the installed branch and components; verify application.
Adobe Commerce B2B
APSB26-73 lists 1.5.3, 1.5.2-p5 and earlier, 1.4.2-p10 and earlier, 1.3.4-p17 and earlier, and 1.3.3-p18 and earlier.
Corrección: Applicable July 2026 B2B component patch, with the required CE/EE patches for the installation.
Adobe Commerce Events
Affected range requires clarification: APSB26-73 lists 1.6.0–1.20.0; the CNA record lists versions through 1.20.0 with a different lower bound. Confirm older versions with Adobe.
Railway’s preliminary report confirms that some encrypted environment variables were decrypted. It recommends replacing sensitive variables stored before October 21.
Actuar ahoraIncidente confirmado por el proveedor
Replace reachable secrets, revoke old access and review provider activity.
Straiker reports AI supported attack operations targeting banks and payment providers in Latin America. Its reported target inventory is not a count of confirmed compromises.
Seguir evoluciónInforme de investigación
Review exposed services, privileged access and model provider credentials.
PingCAP confirms an internal systems incident and exported customer records. Its customer guidance calls for replacing active TiDB Cloud management keys.
Actuar ahoraIncidente confirmado por el proveedor
Replace active management keys and verify unexpected account requests.
La última actualización indica cambios editoriales, no el inicio de un ataque. La prioridad es independiente de la fecha y de la categoría.Cómo asignamos prioridades
Priorizar vulnerabilidades
Explotación confirmada primero. EPSS ordena las demás vulnerabilidades.
Identify applications that bundle axis:axis. Migrate to a supported SOAP engine or use a build with Apache’s referenced patch applied. Verify the deployed library.
Follow BerriAI’s recommendation to upgrade to 1.83.11 or later. If an upgrade must wait, block the custom code test endpoint at the reverse proxy or API gateway.
Identify public survey servers and confirm the corrected build for the installed branch with the consortium. Restrict access to vulnerable surveys until the server is updated.
Update the installed Puppet Enterprise branch to 2023.8.13, 2025.12.1 or 2026.0.1 and restart Puppet Server. Review certificate issuance and suspicious service activity.
Apply Faspex 5.0.19 PL1 and verify faspex-core is 5.0.19 (1ce4b13, Fix Pack: 1). IBM lists no workaround; review unexpected changes to administrator privileges.
Install the corrected Jumbo Hotfix for your Gaia branch and verify the socket permissions. Review DynamicCLI and authentication logs for earlier abuse; patching does not remove an existing compromise.
Identify Webtop Media Transcoder versions below 1.1.22.0 and arrange the vendor’s supported Media Server upgrade. Review conversion activity and investigate possible information exposure.
Update listed Gen7 devices to 7.3.4-7013 or later, and Gen8 devices to 8.2.3-8015 or later. Verify SSLVPN authentication and review earlier sessions, including use of alternate login methods.
Upgrade affected BroadWorks components to RI.2026.07 or a later corrected release. Restrict OCI-P reachability and review earlier requests for signs of configuration disclosure.
Patch affected decoders by product and branch. Verify runtime patches and rebuilt containers. On CloudLinux, check system Brotli, ea-brotli and static alt-php copies separately.
Apply the correction for each affected product and branch, restrict exposed administration and investigate earlier activity. Update PHP runtimes and appliance firmware separately.
Apply the correction for each affected product and branch, restrict exposed administration and investigate earlier activity. Update PHP runtimes and appliance firmware separately.
Update Chrome to 157.0.8103.78 or later on Linux, or 157.0.8103.78/.79 or later on Windows and macOS. Relaunch and verify the executable actually running.
Identify applications that bundle axis:axis. Migrate to a supported SOAP engine or use a build with Apache’s referenced patch applied. Verify the deployed library.
Follow BerriAI’s recommendation to upgrade to 1.83.11 or later. If an upgrade must wait, block the custom code test endpoint at the reverse proxy or API gateway.
Identify public survey servers and confirm the corrected build for the installed branch with the consortium. Restrict access to vulnerable surveys until the server is updated.
Update the installed Puppet Enterprise branch to 2023.8.13, 2025.12.1 or 2026.0.1 and restart Puppet Server. Review certificate issuance and suspicious service activity.
Keep the identified extensions disabled, update ScreenConnect to the latest supported version and verify every technician client is at least 26.6.5. Review activity and invalidate sessions using the vendor guidance.
Apply Faspex 5.0.19 PL1 and verify faspex-core is 5.0.19 (1ce4b13, Fix Pack: 1). IBM lists no workaround; review unexpected changes to administrator privileges.
Install the corrected Jumbo Hotfix for your Gaia branch and verify the socket permissions. Review DynamicCLI and authentication logs for earlier abuse; patching does not remove an existing compromise.
Identify Webtop Media Transcoder versions below 1.1.22.0 and arrange the vendor’s supported Media Server upgrade. Review conversion activity and investigate possible information exposure.
Update listed Gen7 devices to 7.3.4-7013 or later, and Gen8 devices to 8.2.3-8015 or later. Verify SSLVPN authentication and review earlier sessions, including use of alternate login methods.
Upgrade affected BroadWorks components to RI.2026.07 or a later corrected release. Restrict OCI-P reachability and review earlier requests for signs of configuration disclosure.
Patch affected decoders by product and branch. Verify runtime patches and rebuilt containers. On CloudLinux, check system Brotli, ea-brotli and static alt-php copies separately.
Apply the correction for each affected product and branch, restrict exposed administration and investigate earlier activity. Update PHP runtimes and appliance firmware separately.
Update Chrome to 157.0.8103.78 or later on Linux, or 157.0.8103.78/.79 or later on Windows and macOS. Relaunch and verify the executable actually running.
Apply the November 10 Office security update for each affected edition and channel. Verify the client build and investigate suspicious messages or access using your incident response process.
Restrict administration access to trusted networks, install the latest firmware and verify the applicable security patch. Investigate prior exposure separately from patching.
Update FreeSWITCH to 1.11.3 or later. Disable inbound chat on profiles that do not need it and review earlier service activity; an inbound ACL change alone does not close this path.
Upgrade GPUStack to 2.2.0 or later and restrict API access. Review unexpected administrator keys, custom backends and workers; revoke credentials affected by unauthorized access.
Install OpenSSH 10.6p2 or the corrected distribution package, restart sshd and test a new connection. Preserve and review earlier logins, account changes and authorized keys on exposed systems.
Update Plex Media Server to 1.43.3.10861 or later and restrict remote access. Investigate previously exposed installations; updating alone does not remove a prior compromise.
Install the firmware correction for the exact switch model, restrict access to its management interface and review available logs for unexpected activity.
Install WordPress 7.1.4 or a corrected release for your branch. Verify each deployed site and investigate suspicious activity around earlier core upgrades.
Install the latest supported branch patch, verify the running version and investigate the CI/CD indicators in the vendor advisory. Do not downgrade to an older minimum fix.
Apply the kernel fix for your distribution, preserve evidence where compromise is suspected and activate the corrected kernel using the distributor procedure. Verify the running kernel after remediation.
Install the ESX correction for the deployed branch and platform. Review administrative access and available external telemetry; missing host log entries do not rule out malicious activity.
Upgrade servers you operate to 2026.4.1.39 through the supported path, then update every Agent and Probe to HF3. Review inactive Agents after reconnection. Legacy API remains blocked; Intune and remote control limitations remain.
Replace affected certificate chains, verify trust stores and update the SDK for each platform. Rebuild and distribute affected apps; verify Lambda runtime updates and ALB authentication separately.
Identify where NGINX accepts HTTP/2. Apply the corrected release for your branch or the distribution package that fixes this CVE, then verify the workers serving traffic.
Install the current supported CWP release, restrict panel access and verify the installed code. Include the OAuth protections introduced in 1.30.14 and verify completion of the automatic client-secret rotation.
Follow Sophos KBA-000049692 to obtain and manually install the exceptional patch, and plan migration to a supported firewall. The installation procedure still needs verification.
Verify OS, browser and device security updates. If evidence indicates compromise, preserve logs and coordinate session revocation and credential recovery from a trusted device; installing updates alone does not invalidate stolen sessions.
Identify exposed Java services on processors with AVX-512 VBMI. Patch standalone runtimes and verify the running JVM. For Cisco appliances, match the product to its own release status before scheduling maintenance.
Install the corrected minor release for your PostgreSQL branch, restart the server and verify its running version. Review which application accounts can create database objects.
Apply KB5002945 to SharePoint Server Subscription Edition after checking Workflow Manager prerequisites. Verify build 16.0.20326.20278 and review Secure Store target application membership.
Update the affected Telerik server package to 2026.4.1111 or later, align client assets with that version and redeploy. Test filter endpoints and review parsing failures.
Identify affected running kernels and reachable listeners. Apply the correction for the installed distribution and branch, reboot where required, and verify the active kernel or replacement nodes.
Update the Node.js driver to 7.8.0 or later and redeploy applications using mongodb+srv. Check DNS integrity and investigate unexpected database destinations.
Update deployed 7-Zip copies to 26.06 or a later corrected release. Verify portable copies and archive processing jobs before resuming untrusted CAB extraction.
Update Swarmkit v2 to 2.1.3 where directly embedded. For Docker deployments, verify a release or backport covering this CVE and restrict access to worker credentials and cluster management paths.
Update supported runtimes to 22.23.5, 24.22.3 or 26.13.1, rebuild images and restart applications. Prioritize reachable HTTP/2 and HTTPS services; verify the runtime actually serving traffic.
Check deployed react-server-dom packages and update the affected branch to 19.0.9, 19.1.10, 19.2.9 or 19.3.1. Rebuild and redeploy the server; prioritize applications matching the response conditions.
Update AuthPoint Authentication Gateway to 7.6.0 or a later corrected release, restrict gateway access and verify authentication and directory synchronization afterward.
Update to 0.8.6 or later and rotate credentials present in environments of agents that loaded the environment tool. If upgrading is not possible immediately, remove the tool.
Install the correction for the exact distribution package and kernel branch, reboot and verify the running kernel. Debian lists linux-6.12 6.12.115-2~deb12u1 as fixed for bookworm; its linux 6.1 packages remain vulnerable.
Update the Modules website to 3.1.5 or apply the verified maintainer correction through your supported deployment process. Restrict access and confirm anonymous users cannot change external tools.
Update affected 7.4 clients to 7.4.8 or later; update Windows and Windows PAM 7.2 clients to 7.2.15 or later. Check the edition and running version on each endpoint, not only the deployment console.
Update NetScaler Console 14.1 to 14.1-74.34 or later. Restrict access to the console IP and review unexpected administrative access; ADC and Gateway updates use different builds.
Update 14.1 to 14.1-73.57 or 13.1 to 13.1-64.39. Use 14.1-73.58 for FIPS or 13.1-37.293 for FIPS/NDcPP; check the separate NetScaler Console correction independently.
Upgrade to 8.0.1, 7.6.8, 7.4.6 or 7.2.9 or a later corrected release in the applicable branch. Restrict FGFM access to required management peers and verify the active version.
Identify enabled modules and update Apache HTTP Server to 2.4.71 or a vendor package containing the fixes. Verify the running server and separately installed HTTP/2 modules.
Identify replica set members, including shards and config servers. Install the corrected version for each branch, verify running versions and restrict database access to trusted networks.
0.42% de probabilidad estimada de explotación en los próximos 30 días. No es la probabilidad de un ataque a tu organización.
Puntaje del 19 nov 2026 · Superior al 36.7% de las vulnerabilidades evaluadas.Sin cambios desde 18 nov 2026.Datos de FIRST EPSS
FIRST EPSS · Revisado 2026-11-19 21:12 UTC
La prioridad corresponde al aviso, no a cada producto o CVE por separado. Cada fila muestra solo la evidencia atribuida a ese CVE. La falta de evidencia de ataques no permite descartar una vulnerabilidad. Tu entorno no fue escaneado.