Search/Check Point, Kaspersky, Tanium Patch Product Vulnerabilities
● Story

Check Point, Kaspersky, Tanium Patch Product Vulnerabilities

Attackers exploited a previously unknown flaw in Check Point's Security Management Server in a handful of targeted attacks on July 23, the company said. The flaw, CVE-2026-93616, allows an attacker who can access the server's web service to run scripts on it without logging in. Check Point released a fix on September 22 for the server that controls firewall policies for the Check Point gateways it manages. Separately, Check Point said attackers have been trying since September 12 to exploit a VPN flaw it fixed on September 9. The attempts, against a flaw tracked as CVE-2026-85102, have targeted customers of Spark, Check Point's firewall line for small businesses. When the fix came out, Check Point had no evidence the flaw was being exploited. CVE-2026-93616 is a path traversal bug in the…

CVEs
39
Highest CVSS
10
In KEV
19
Sources
30
Key vulnerabilities
top 3 of 39 by CVSS
Connections
109 relationships
NCSC-2026-0365 [1.01] [H/H] Kwetsbaarheden verholpen in Check Point VPN-producten
Check Point heeft twee kritieke kwetsbaarheden verholpen in Quantum Security Gateway en Security Management. De kwetsbaarheid met kenmerk CVE-2026-85102 heeft een CVSS-score van 9,8. De kwetsbaarheid bevindt zich in het VPN-onderhandelingsproces van de Quantum Security Gateway en wordt veroorzaakt door onjuiste validatie van certificaatvertrouwen. Hierdoor kan een niet-geauthenticeerde externe aanvaller authenticatiecontroles omzeilen en willekeurige code uitvoeren op de Security Gateway. Exploitatie vindt plaats tijdens de VPN-onderhandeling, waarbij certificaatgegevens onvoldoende worden gevalideerd. De kwetsbaarheid geldt voor Security Gateway en Check Point Spark Firewall wanneer Site-to-Site VPN of Remote Access VPN wordt gebruikt. Voor Site-to-Site VPN adviseert Check Point om implied rules for VPN uit te schakelen en VPN-toegang voor UDP/500 en UDP/4500 alleen expliciet toe te staan voor de specifieke peer-IP-adressen. Deze mitigatie is niet van toepassing op lokaal beheerde Spark Firewalls. De kwetsbaarheid met kenmerk CVE-2026-85103 heeft een CVSS-score van 9,8. Het betreft een heap-based buffer overflow in de ASN.1-decoding van VPN-certificaten, veroorzaakt door onjuiste verwerking van ASN.1-datastructuren tijdens de certificaatverwerking. Een niet-geauthenticeerde externe aanvaller kan deze kwetsbaarheid misbruiken om willekeurige code uit te voeren op het getroffen systeem. De kwetsbaarheid bevindt zich in een component die onderdeel is van de VPN-infrastructuur en kan bij succesvolle exploitatie de vertrouwelijkheid, integriteit en beschikbaarheid van het getroffen systeem beïnvloeden. Het NCSC verwacht dat op korte termijn pogingen tot grootschalig misbruik zullen plaatsvinden en roept organisaties op de advisory van Check Point met spoed op te volgen. Update: Check Point meldt dat misbruik van de kwetsbaarheid met kenmerk CVE-2026-85102 is waargenomen. Het NCSC adviseert de advisory van Check Point met spoed op te volgen. Raadpleeg de blog van Check Point voor aanvullende informatie. De inschaling van deze advisory blijft ongewijzigd.
advisories.ncsc.nlSep 23, 2026extracted
Alerta de Vulnerabilidade - Arista VeloCloud Orchestrator
<div style="width: 100%; overflow-x: auto; -webkit-overflow-scrolling: touch;"> <table style="width: 100%; min-width: 700px; border-collapse: collapse; font-family: Arial, sans-serif; font-size: 14px; border-radius: 8px; overflow: hidden;"> <thead> <tr> <th style="padding: 0; border: none;" colspan="3"> <div style="display: flex; justify-content: space-between; align-items: center; gap: 16px; background-color: #1f4e79; color: white; padding: 12px 16px;"><span style="font-weight: bold; font-size: 14px;">CVSS v4.0 - Resumo Técnico</span> <span style="background-color: #ff4d4d; color: white; padding: 6px 12px; border-radius: 6px; font-weight: bold; font-size: 13px; white-space: nowrap;">CVSS: 9.5 / 10 - Crítico</span></div> </th> </tr> </thead> <tbody> <tr style="background-color: #f4f7fb;"> <td style="padding: 8px; border: 1px solid #ddd;"><strong>CVE</strong></td> <td style="padding: 8px; border: 1px solid #ddd;" colspan="2"><strong>CVE-2026-93952/EUVD-2026-84296</strong></td> </tr> <tr style="background-color: #f4f7fb;"> <td style="padding: 8px; border: 1px solid #ddd;"><strong>Vetor</strong></td> <td style="padding: 8px; border: 1px solid #ddd; font-family: monospace; word-break: break-word; overflow-wrap: anywhere;" colspan="2">CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H</td> </tr> <tr> <td style="padding: 8px; border: 1px solid #ddd;">Vetor de Ataque</td> <td style="padding: 8px; border: 1px solid #ddd;">Rede</td> <td style="padding: 8px; border: 1px solid #ddd;"><span style="background-color: #ff4d4d; color: white; padding: 4px 8px; border-radius: 4px;"><strong>Explorável remotamente através da rede</strong></span></td> </tr> <tr> <td style="padding: 8px; border: 1px solid #ddd;">Complexidade</td> <td style="padding: 8px; border: 1px solid #ddd;">Alta</td> <td style="padding: 8px; border: 1px solid #ddd;">Exige condições adicionais para a exploração</td> </tr> <tr> <td style="padding: 8px; border: 1px solid #ddd;">Requisitos de Ataque</td> <td style="padding: 8px; border: 1px solid #ddd;">Nenhum</td> <td style="padding: 8px; border: 1px solid #ddd;"><span style="background-color: #ff4d4d; color: white; padding: 4px 8px; border-radius: 4px;"><strong>Não requer condições específicas para além do acesso</strong></span></td> </tr> <tr> <td style="padding: 8px; border: 1px solid #ddd;">Privilégios</td> <td style="padding: 8px; border: 1px solid #ddd;">Nenhum</td> <td style="padding: 8px; border: 1px solid #ddd;"><span style="background-color: #ff4d4d; color: white; padding: 4px 8px; border-radius: 4px;"><strong>Sem autenticação</strong></span></td> </tr> <tr> <td style="padding: 8px; border: 1px solid #ddd;">Interação</td> <td style="padding: 8px; border: 1px solid #ddd;">Nenhuma</td> <td style="padding: 8px; border: 1px solid #ddd;"><span style="background-color: #ff4d4d; color: white; padding: 4px 8px; border-radius: 4px;"><strong>Não requer intervenção do utilizador</strong></span></td> </tr> <tr style="background-color: #ffe6e6;"> <td style="padding: 10px; border: 1px solid #ddd;"><strong>Resumo</strong></td> <td style="padding: 10px; border: 1px solid #ddd;" colspan="2">Vulnerabilidade de severidade crítica (CVSS 9.5), identificada como CVE-2026-93952, de validação de input incorreta (CWE-20) no Arista VeloCloud Orchestrator (VCO) on-premises. Um atacante remoto sem credenciais do VCO, com acesso ao interface web, alcança funcionalidade interna privilegiada e compromete o host do orquestrador e os dados que gere. A exposição depende de estar configurada autenticação por certificado dos Edge para o VCO. Exploração ativa confirmada pela Arista. Corrigido no VCO 5.2.3.16 e 6.4.2.8; restantes ramificações por corrigir. Nota: apresenta-se o vetor CVSS v4.0 (9.5); a v3.1 do mesmo vetor atribui 10.0.</td> </tr> </tbody> </table> </div> <div class="alert-detail-title" style="text-align: left;"><br />Descrição</div> Vulnerabilidade de validação de input incorreta (CWE-20) no Arista VeloCloud Orchestrator, com o identificador CVE-2026-93952/EUVD-2026-84296 [1][2][3]. O VeloCloud Orchestrator (VCO) é o servidor que gere e orquestra os dispositivos Edge de uma rede SD-WAN VeloCloud. Por validação insuficiente do input recebido, um atacante remoto alcança funcionalidade interna privilegiada e afeta o host do orquestrador [1].<br /><br />A exposição depende da configuração: o VCO só é vulnerável quando está ativa a autenticação por certificado dos Edge para o VCO. Para explorar, o atacante necessita de acesso de rede ao interface web do VCO e da porção pública de um certificado de autenticação de um Edge, não sendo necessárias credenciais de tenant ou de operador do VCO [1]. A Arista confirma que a vulnerabilidade está a ser ativamente explorada [1].<br /><br />É afetado o VeloCloud Orchestrator on-premises nas seguintes ramificações [1]:<br /> <ul> <li>5.2.x: 5.2.3.15 e anteriores</li> <li>6.1.x: 6.1.3.7 e anteriores</li> <li>6.4.x: 6.4.2.7 e anteriores</li> <li>7.0.x: 7.0.0.2 e anteriores</li> </ul> As versões Hosted e Dedicated do VCO já foram corrigidas pela Arista. O VeloCloud Gateway e o VeloCloud Edge não são afetados [1].<br /><br /> <div class="alert-detail-title">Impacto</div> Um atacante remoto não autenticado, sem credenciais do VCO, que disponha de acesso ao interface web e da porção pública de um certificado de Edge, alcança funcionalidade interna privilegiada no orquestrador [1].<br /><br />A exploração compromete a confidencialidade, integridade e disponibilidade do orquestrador e dos dados que gere. Como o VCO controla a rede SD-WAN, o seu comprometimento pode dar acesso aos dispositivos Edge geridos [1].<br /><br /> <div class="alert-detail-title">Resolução</div> Recomenda-se a atualização do VCO on-premises para uma versão corrigida [1]:<br /> <ul> <li>Ramificação 5.2.3: 5.2.3.16 ou posterior</li> <li>Ramificação 6.4.2: 6.4.2.8 ou posterior</li> <li>Ramificações 6.1.x e 7.0.x: ainda sem correção disponível à data; aplicar quando publicada e contactar o Arista TAC para opções de atualização, incluindo ramificações sem suporte [1][4]</li> </ul> Medidas adicionais de mitigação e deteção [1]:<br /> <ul> <li>Enquanto a correção não é aplicada, restringir o acesso ao interface web do VCO a redes de administração de confiança, monitorizar acessos a partir de IPs maliciosos conhecidos e atividade de saída inesperada do host, bloquear portos de saída desnecessários e vigiar a presença de daemons de backdoor e webshells.</li> <li>Não existe um indicador de comprometimento único. Rever os logs de acesso web do VCO para caminhos de URL invulgares, caracteres codificados, referências a serviços internos ou taxas de pedidos elevadas, e os logs aplicacionais e de sistema para execução de comandos, criação de ficheiros, exportação de base de dados ou acesso a configuração, credenciais, certificados e material de chave não esperados.</li> <li>Indicadores de comprometimento publicados pela Arista: presença dos ficheiros <code>/usr/local/sbin/.vcnode.js</code>, <code>/usr/local/sbin/vc-sysmond</code> (MD5 <code>dc78e206eaeadec59fc5801fe4556bd0</code>) ou <code>/etc/systemd/system/vc-sysmon.service</code>; o cabeçalho HTTP <code>x-vc-opt</code> nos logs do nginx; ligações a partir dos IPs <code>142.93.149.77</code> e <code>104.248.126.159</code>. Perante qualquer destes indicadores, preservar o estado e os logs do VCO e contactar o Arista TAC.</li> <li>Após a correção, e em caso de suspeita de comprometimento, rodar credenciais e material criptográfico, validar o estado dos dispositivos geridos e restaurar ou substituir o orquestrador a partir de uma fonte de confiança, dado que o comprometimento do VCO pode ter exposto os Edge geridos.</li> </ul> <div class="alert-detail-title">Referências</div> [1] - <a href="https://www.arista.com/en/support/advisories-notices/security-advisory/24765-security-advisory-0183" target="_blank" rel="noopener">https://www.arista.com/en/support/advisories-notices/security-advisory/24765-security-advisory-0183</a><br />[2] - <a href="https://www.cve.org/CVERecord?id=CVE-2026-93952" target="_blank" rel="noopener">https://www.cve.org/CVERecord?id=CVE-2026-93952</a><br />[3] - <a href="https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-84296" target="_blank" rel="noopener">https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-84296</a><br />[4] - <a href="https://thehackernews.com/2026/09/new-cvss-100-velocloud-orchestrator.html" target="_blank" rel="noopener">https://thehackernews.com/2026/09/new-cvss-100-velocloud-orchestrator.html</a>
dyn.cncs.gov.ptSep 23, 2026extracted
Cisco drops another exploited zero-day, this time a perfect 10
Cisco admins who have spent their week patching email gateways now face a perfect-10 Identity Services Engine flaw under active attack. Cisco disclosed CVE-2026-76460 on Wednesday, describing it as an authentication bypass affecting Identity Services Engine (ISE) and ISE Passive Identity Connector (ISE-PIC). Successful exploitation can give an unauthenticated remote attacker command execution with root privileges. Product Security Incident Response Team said it was aware of active exploitation and urged customers to install the fixes immediately. CISA has also added the vulnerability to its Known Exploited Vulnerabilities catalog. The warning follows another actively exploited critical vulnerability disclosed days earlier, CVE-2026-76461, affecting its Secure Email Gateway and Secure Email and Web Manager appliances. That 9.8-rated bug could also lead to root access, prompting Cisco to warn admins that attackers may be able to cover their tracks after getting in. The latest problem lies in an API within Cisco ISE, the company's network access control platform. Cisco says insufficient authentication controls on an API endpoint mean an attacker can send a crafted request to bypass the product's web-based management interface. No credentials or user interaction are required, and Cisco says vulnerable versions of ISE and ISE-PIC are affected regardless of configuration. The flaw received the maximum CVSS score of 10.0. Cisco warned that root access could allow attackers to remove or conceal traces of an intrusion, complicating efforts to determine whether an appliance had been breached. Cisco advised admins to review ISE access logs for suspicious usernames on every node in a distributed deployment and to check network and firewall logs held outside the affected device for signs of unexpected uploads or downloads. If admins find evidence of possible exploitation, Cisco "strongly recommends" reimaging affected nodes and restoring their configurations from backup if necessary. No workaround exists, although Cisco said infrastructure access control lists can be used as a temporary mitigation to restrict management and control-plane traffic reaching affected systems. Permanent fixes are available in ISE and ISE-PIC 3.1 Patch 12, 3.2 Patch 11, 3.3 Patch 12, 3.4 Patch 7 and 3.5 Patch 4. ISE 3.0 has reached the end of software maintenance, so customers running it must migrate to a supported release. Cisco discovered CVE-2026-76460 while resolving a Technical Assistance Center support case, but has not disclosed who is exploiting it, how long the attacks have been underway, or what the intruders have done after gaining access. The advisory accompanied a substantial batch of other ISE vulnerabilities published Wednesday. Two other Cisco advisories carried maximum CVSS scores of 10.0, while a separate trio of remote code execution flaws scored as high as 9.9. For admins responsible for Cisco kit, September is shaping up to be quite the patching month. ®
theregister.comSep 17, 2026extracted
NCSC-2026-0382 [1.00] [H/H] Kwetsbaarheden verholpen in Cisco Identity Services Engine (ISE)
Cisco heeft 21 kwetsbaarheden verholpen in Cisco Identity Services Engine (ISE) en Cisco ISE Passive Identity Connector (ISE-PIC). De kwetsbaarheden betreffen verschillende beveiligingsproblemen in Cisco ISE en ISE-PIC, waaronder mogelijkheden voor niet-geauthenticeerde en laaggeprivilegieerde kwaadwillenden om via netwerktoegang ongeautoriseerde acties uit te voeren. De kwetsbaarheden hebben CVSS-scores variërend van middel tot kritiek. Van de in totaal 21 kwetsbaarheden zijn 13 als kritiek aangemerkt. Op basis van de door Cisco gepubliceerde CVSS-scores kunnen vier kwetsbaarheden zonder authenticatie op afstand worden misbruikt. Succesvol misbruik kan onder meer leiden tot het omzeilen van authenticatie- en autorisatiecontroles, het verkrijgen en wijzigen van gevoelige configuratie- en identiteitsgegevens, het uitvoeren van willekeurige code of commando's met rootrechten, SQL-injectie, het uitlezen van bestanden en het verstoren van de beschikbaarheid van getroffen systemen. Sommige kwetsbaarheden vereisen voorafgaande administratieve toegangsrechten of een specifieke configuratie, terwijl andere volledig op afstand en zonder authenticatie kunnen worden misbruikt. Van de 13 kwetsbaarheden die als kritiek zijn aangemerkt, hebben meerdere een CVSS-score van 9,8 of hoger. Vier kwetsbaarheden, CVE-2026-20130, CVE-2026-20192, CVE-2026-76423 en CVE-2026-76460, hebben een CVSS-score van 10,0. De kwetsbaarheid met kenmerk CVE-2026-76423 betreft een kwetsbaarheid in de REST API waarmee een niet-geauthenticeerde kwaadwillende administratieve toegang kan verkrijgen tot Cisco ISE en ISE-PIC. De kwetsbaarheid met kenmerk CVE-2026-76460 betreft een authenticatieomzeiling in een API van Cisco ISE en ISE-PIC waarmee een niet-geauthenticeerde kwaadwillende toegang tot het getroffen systeem kan verkrijgen. Cisco meldt dat deze kwetsbaarheid actief wordt misbruikt. Na succesvolle exploitatie kunnen kwaadwillenden volgens Cisco commando's met rootrechten uitvoeren. De kwetsbaarheden met kenmerk CVE-2026-20130 en CVE-2026-20192 betreffen door Cisco gegroepeerde kwetsbaarheden op het gebied van respectievelijk onvoldoende neutralisatie van invoer en onjuiste toegangscontrole. Cisco heeft voor deze hardening-release meerdere onderliggende kwetsbaarheden per CWE-klasse onder één CVE-ID samengebracht. De CVSS-score vertegenwoordigt daarbij de hoogst scorende onderliggende kwetsbaarheid. Het NCSC adviseert om de beveiligingsupdates voor de kritieke kwetsbaarheden met voorrang toe te passen.
advisories.ncsc.nlSep 17, 2026extracted
Related Stories
3
2026-013: Critical Vulnerability in F5 BIG-IP APM
History: 22/09/2026 --- v1.0 -- Initial publication Summary On 22 September 2026, F5 published an advisory addressing a critical vulnerability affecting its BIG-IP APM product. The vendor confirmed active exploitation in the wild [1]. CERT-EU recommends taking appropriate actions as soon as possible. Technical Details The vulnerability CVE-2026-94127, with a CVSS score of 9.8, is a heap-based buffer overflow vulnerability and allow unauthenticated attacker to achieve remote code execution (RCE) on the affected device [1]. Affected Products The vulnerability affects the following versions of BIG-IP APM if configured with an access policy and an OAuth profile on a virtual server [1]: 17.1.0 - 17.1.3 17.5.0 - 17.5.1 21.1.0 Recommendations CERT-EU recommends taking the following actions as soon as possible: Preserve forensic evidence. Apply the relevant hotfix. Check for signs of compromise (see the compromise assessment section). If any sign of compromise is detected, start the incident response process. Mitigation If patching cannot be applied immediately, F5 provides an iRule-based mitigation for the affected virtual server. To obtain it, F5 BIG-IP clients should contact the F5 support [1]. Compromise Assessment CERT-EU strongly advises to look for the following indicators of compromise provided by the vendor in its advisory [1]: At a high level, multiple OAuth authentication failures, followed by suspicious commands, shortly followed by a TMM SIGABRT is the combination that should lead to human review of the system. OAuth authentication failures: check /var/log/apm for repeated occurrences of the following, especially 10 or more from a single IP in a short window. err tmm1\[30975\]: 01990004:3: : Request UserInfo from Source ID (null) IP failed. Error Code (invalid\_token) Error Description (The access token is invalid.) - Increase of OAuth failure statistics. Run the following and look for an unexplained increase in total_failed : $ tmctl global_oauth_stat -s total_requests,total_userinfo_requests,total_failed - Audit log anomalies: if OAuth failures are observed, review /var/log/audit around those timestamps for suspicious commands. TMM core files: Presence of a TMM core file alone is not an indicator, but core files should be investigated. The vendor indicates that they have observed TMM entering a loop, which causes the SOD daemon to send a SIGABRT.
79 shared
Sep 25, 2026
Ongoing updates on Copy.fail and variants
Check Point Software has released emergency fixes for a critical Check Point Management Server vulnerability (CVE-2026-93616) that has been exploited as far back as July 23, 2026. The company also confirmed that a pre-authentication remote code execution (RCE) vulnerability (CVE-2026-85102) in Check Point (Quantum) Security Gateway for which it released patches on September 9, 2026, started getting probed a few days after. “At the time [of the release of the patches], we had no evidence … More → The post Attackers hit Check Point Management Servers and Spark firewalls, F5 BIG-IP APM instances appeared first on Help Net Security .
44 shared
Sep 29, 2026
Cisco patches actively exploited email gateway zero-day (CVE-2026-76461)
Criminals are exploiting a critical Cisco Secure Email Gateway flaw that can turn a malicious email into root access. The vulnerability, tracked as CVE-2026-76461, carries a 9.8 CVSS score and affects physical and virtual Secure Email Gateway appliances regardless of their configuration. Cisco says there are no workarounds, so patching is the only fix. The bug lies in how Cisco's AsyncOS software handles incoming email. An attacker doesn't need to log in: they can send a booby-trapped message through a vulnerable gateway and, if the exploit works, run commands as root. Which is not exactly what you want from the box tasked with keeping nasty emails out. Cisco's Product Security Incident Response Team said it became aware of active exploitation in September, although the networking giant hasn't said who is behind the attacks, how long they have been going on, or how many organizations have been compromised. Cisco uncovered the bug while resolving a Technical Assistance Center support case. Signs suggest at least some Cisco cloud customers were caught up in the attacks. Cisco said it investigated devices belonging to its Secure Email Cloud service and directly contacted customers whose appliances showed indicators of possible compromise. It is now carrying out remediation and recovery work and says all of its Secure Email Cloud devices have been upgraded to AsyncOS 16.5.0-780. Admins running their own appliances have a little more work to do. Cisco recommends checking logs for signs of suspicious activity, but warns that finding nothing doesn't necessarily mean the system is clean. Once attackers have root access, Cisco says they could tamper with the logs and cover their tracks. Admins are also being told to check network and firewall logs for anything unusual, rather than relying on the gateway itself for answers. For virtual appliances suspected of being compromised, Cisco's recovery advice is fairly drastic: preserve the forensic evidence, deploy a fresh VM running fixed software, rebuild the configuration, and rotate credentials and cryptographic material. Cisco has fixed the bug in AsyncOS releases 15.5.5-014, 16.0.4-302 and 16.5.0-780, with customers strongly encouraged to move to the latter. There's still a decent-sized target pool out there. The Shadowserver Foundation was tracking more than 400 Cisco Secure Email Gateway appliances exposed to the internet as of Monday The flaw has also landed in CISA's Known Exploited Vulnerabilities catalog, with US federal civilian agencies ordered to remediate it by September 17. CVE-2026-76461 comes less than a year after attackers exploited another critical AsyncOS flaw, CVE-2025-20393, to break into Cisco Secure Email Gateway appliances and install persistence mechanisms. That bug eventually scored a perfect 10. For anyone still running an affected gateway, the message is fairly simple: the box designed to inspect hostile email can itself be pwned by one; attackers are already doing it, and there is no workaround to hide behind. ®
36 shared
Sep 18, 2026