Reporting Period: November 14, 2026 – November 20, 2026
Threat Landscape
1. Apache Roller XML-RPC Deserialization Remote Code Execution Vulnerability CVE-2026-129448 (CVSS 9.8, actively exploited)
Overview
- Critical unauthenticated deserialization vulnerability in Apache Roller’s XML-RPC endpoint.
- Allows remote attackers to execute arbitrary code by submitting malicious serialized data before authentication.
- Confirmed active exploitation observed in the wild.
- CVE-2026-129448 is the same issue as CVE-2026-82384, previously noted against Apache Roller 6.1.5.
Impact
- Unauthenticated remote code execution leading to potential system compromise.
- Unauthorized access, data theft, and service disruption possible.
Affected / Fixed Versions
- Affected: Apache Roller 4.0.0 through 6.1.5.
- Fixed: Apache Roller 6.1.6 and later.
Recommendations
- Immediately upgrade to Apache Roller version 6.1.6 or later.
- Review server logs for anomalous XML-RPC requests.
- Monitor systems for unusual processes, unauthorized modifications, and suspicious network activity.
Reference link: https://www.cve.org/CVERecord?id=CVE-2026-129448
2. F5 BIG-IP and NGINX Critical Vulnerabilities Including Arbitrary Code Execution in NGINX HTTP/2 Module CVE-2026-123007 (PoC Published)
Overview
- Multiple critical and high severity vulnerabilities disclosed in F5 BIG-IP (including APM, DNS, PEM, SSL Orchestrator), BIG-IQ, BIG-IP Cloud-Native Edition, BIG-IP Next for Kubernetes, NGINX Open Source, NGINX Plus, NGINX Instance Manager, and related WAF and DoS modules.
- Key critical issues include CVE-2026-123007 in the NGINX HTTP/2 module with a public proof of concept available.
- Vulnerabilities allow arbitrary code execution, denial of service (DoS), memory corruption, security bypass, and system compromise.
Impact
- Exploitation can result in remote code execution, service disruption, and full compromise of affected platforms.
Affected / Fixed Versions
- Detailed affected and fixed software versions and modules are documented in the official F5 advisory.
Recommendations
- Immediately apply official F5 security updates and hotfixes.
- Prioritize remediation of critical vulnerabilities on internet-facing systems.
- Review and audit configurations to identify vulnerable services and modules.
- Restrict and monitor access to management interfaces and exposed services.
- Continuously monitor logs for indicators of exploitation or suspicious activity.
Reference links:
3. Atlassian Multiple Products Remote Code Execution and Critical Vulnerabilities Including CVE-2026-4800 (CVSS 9.8)
Overview
- Atlassian addressed 318 vulnerabilities across Bamboo, Bitbucket, Confluence, Crowd, Fisheye/Crucible, and Jira (including Jira Service Management).
- Highest severity vulnerabilities scored CVSS 9.8.
- Key issues include remote code execution (RCE), path traversal, broken authentication and session management, server-side template injection, and third-party library flaws in Spring, Tomcat, Lodash, and Jackson Databind.
- No active exploitation or public exploit code confirmed to date.
Impact
- Critical RCE vulnerability in Lodash used by Confluence Data Center allows unauthenticated or low-privileged attackers to execute arbitrary code (CVE-2026-4800).
- RCE via CRLF sequence injection in Spring Server-Sent Events streams affects Bamboo and Crowd (CVE-2026-47890).
- Path traversal and file inclusion flaws in Spring WebMVC and other Spring packages impact Bamboo and Crowd.
- Broken authentication and session management issues in Apache Tomcat affect multiple products.
- Weak cryptographic certificates in Atlassian Data Center Docker images compromise container security.
- Additional vulnerabilities include Server-Side Template Injection in Bamboo, OS command execution in Fisheye/Crucible, stored XSS in Jira, and broken access control in Jira Service Management.
- Unpatched instances risk exposure of source code repositories, build systems, internal wikis, and authentication services.
Affected / Fixed Versions
- Bamboo affected: 12.1.0-12.1.12 (LTS), 12.0.x, 11.0.x, 10.2.0-10.2.24 (LTS), and earlier branches; fixed in 13.0.1, 12.1.13 (LTS), 10.2.26 (LTS).
- Bitbucket affected includes multiple 10.x and 9.x branches; fixed in 10.5.2, 10.2.9 (LTS), 9.4.27 (LTS).
- Confluence affected: 11.0.0, 10.2.0-10.2.19 (LTS), 9.2.x LTS, 8.5.x LTS, others; fixed in 11.0.1, 10.2.20 (LTS), 9.2.27/9.2.28 (LTS).
- Crowd affected: 7.2.x, 7.1.x, 7.0.x, 6.x branches; fixed in 7.2.6.
- Fisheye/Crucible affected: 4.9.0-4.9.15; fixed in 4.9.16.
- Jira/Jira Service Management affected: 11.3.0-11.3.12 (LTS), 10.3.x LTS, earlier 10.x/9.x branches; fixed in 11.3.13 (LTS), 10.3.27 (LTS).
- Official Atlassian Docker images require updating to fix weak cryptographic certificates (CVE-2026-91403).
Recommendations
- Upgrade all affected Atlassian products to the latest fixed versions immediately.
- Prioritize remediation of critical severity vulnerabilities, especially systems accessible from the internet.
- Update Docker container images to the latest official versions to address certificate vulnerabilities.
Reference link: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html
4. Puppet Enterprise deserialization RCE vulnerability CVE-2026-115731 actively exploited
Overview
- Critical remote code execution vulnerability in Puppet Enterprise and Puppet Core due to improper deserialization of untrusted data in Puppet Server’s report-processing feature.
- Allows an attacker with a CA-signed agent certificate to submit a crafted report, resulting in arbitrary code execution under the Puppet Server service account.
- Environments with certificate authority autosigning without strong verification are at increased risk, as unauthenticated attackers may obtain valid certificates to exploit the flaw.
- CVSS v4.0 score of 9.4 (Critical).
- Included in Known Exploited Vulnerabilities (KEV) Catalog, confirming active exploitation.
Impact
- Remote code execution on Puppet Server with service account privileges.
- Potential full control over affected Puppet Server instances.
Affected / Fixed Versions
- Affected:
- Puppet Enterprise 2026.0.0 before 2026.0.1
- Puppet Enterprise 2025.0.0 before 2025.12.1
- Puppet Enterprise 2023.8.0 before 2023.8.13
- Puppet Core 9.0.0 before 9.1.3
- Puppet Core 8.x before 8.22.2
- Fixed:
- Puppet Enterprise 2026.0.1 (Puppet Core 9.1.3)
- Puppet Enterprise 2025.12.1 (Puppet Core 8.22.2)
- Puppet Enterprise 2023.8.13 (Puppet Core 8.22.2)
- Puppet Core 9.1.3
- Puppet Core 8.22.2
Recommendations
- Immediately upgrade all affected Puppet Enterprise and Puppet Core installations to the latest fixed versions.
- Review and restrict CA autosigning configurations to enforce strong verification of agent certificate requests.
- Audit Puppet Server logs and certificate activities for signs of compromise or unauthorized code execution.
- Prioritize remediation for internet-facing and critical Puppet Server deployments due to active exploitation.
Reference link: https://portal.perforce.com/s/cve/a91Qi000003IaHpIAK/report-deserialization-code-execution
5. ARTEX autonomous penetration testing framework weaponization and supply-chain compromise campaigns
Overview
- ARTEX is an open-source LLM-driven multi-agent autonomous penetration testing framework written in Go, weaponized since at least August 2026 to automate cyber intrusions from reconnaissance through data exfiltration with minimal human intervention.
- Enables rapid multi-target operations, often reaching privileged access in under three hours, lowering complexity barriers.
- Used globally across financial services, government, technology, defense, semiconductor, energy, healthcare, manufacturing, telecommunications, and legal sectors.
- Notable attacks include data exfiltration of 67,000 individuals from South Korean financial institutions and supply-chain compromises impacting over 2,250 ConnectWise Cloud Backup tenants.
- Original GitHub repository removed October 2026 due to abuse reports, but forks, mirrors, and a commercial variant (ARTEX PRO) remain widely accessible.
- Over 1,600 publicly exposed ARTEX console instances identified as of early November 2026, with likely higher unobserved deployments.
Impact
- Accelerated, large-scale multi-target cyber intrusions.
- Exploitation of overlooked peripheral attack surfaces such as partner/supplier portals, mobile backends, employee apps, legacy services, and third-party integrations.
- Supply-chain exploitation enabling lateral movement from weaker vendors to high-value enterprise networks.
- Compressed detection and response windows due to rapid attack progression.
- Significant data exfiltration and attempted credential abuse campaigns linked to ARTEX usage.
Technical Details and Tactics:
- ARTEX uses external LLMs (Anthropic Claude, OpenAI GPT, DeepSeek, GLM, Grok, Kimi) to translate natural language goals into automated attack steps executed by specialized "super intelligence" agents.
- Reconnaissance tactics include:
* Automated Azure permission mapping (SAS tokens, Service Principals, Kudu, Storage Account keys) with permission testing via DryRun flags.
* Web directory fuzzing (>500 requests), WHOIS lookups, active vulnerability scanning.
* Geolocation queries through api.db-ip.com.
- Techniques map to MITRE ATT&CK frameworks including T1595 (Active Scanning), T1580 (Collect Application Access Tokens), T1087.004 (Cloud Account Discovery), T1069.003 (Permission Groups Discovery), T1526 (Cloud Service Discovery).
Indicators of Compromise (IOCs):
- ARTEX hosts, proxy IPs, and C2 servers identified, including IPs linked to South Korean financial campaigns and ConnectWise supply-chain compromise.
- Domains such as xcai.pro used as LLM API reseller in campaigns.
- Specific IPs include 38.244.50[.]120, 144.172.64[.]60-199-128, 187.15.88[.]186-217-89, and 199.19.95[.]66-68 among others detailed in public telemetry sources.
Recommendations
- Inventory and secure all internet-exposed applications focusing on peripheral systems and vendor integrations.
- Restrict access to cloud admin interfaces, SCM/Kudu endpoints, hypervisors, backups, preferably limiting to trusted networks or private connectivity.
- Disable unnecessary publishing authentication and restrict deployment credential access.
- Employ deployment models that limit direct modification of application files (e.g., run-from-package).
- Implement Zero Trust access solutions for enterprise applications.
- Enforce least privilege principles on multi-tenant application permissions and monitor for anomalous app-only and service-principal activities in Microsoft 365 tenants.
- Review audit logs (Microsoft Entra, Microsoft Purview, SIEM) for unauthorized credential or permission changes and revoke or rotate suspicious items.
- Strengthen API protections by applying rate limits, abuse controls, and anomaly detection on business-critical endpoints.
- Monitor partner and employee portals for unusual access patterns and enforce strict server-side authorization.
- Avoid exposing sensitive error details to unauthenticated users.
- Continuously scan software repositories and pipelines for embedded secrets, rotating compromised credentials immediately.
- Preserve forensic evidence (sign-in logs, audit records, Graph telemetry) before containment and thoroughly investigate ConnectWise-related anomalies dating back to October 2026.
- Keep affected ConnectWise application connections disabled until formal restoration guidance; avoid deleting apps prematurely.
Reference link: https://www.ic3.gov/CSA/2026/261113.pdf
6. Juniper Junos OS Evolved Linux Kernel IPv4 TCP Use-After-Free Vulnerability CVE-2026-98432 (CVSS 9.8)
Overview
- A critical use-after-free vulnerability in the Linux kernel’s IPv4 TCP connection-handling routines affects all versions of Juniper Networks Junos OS Evolved.
- An unauthenticated remote attacker can send specially crafted TCP SYN packets with IPv4 options to access freed kernel memory.
- Exploitation may lead to kernel memory disclosure, denial of service (DoS), or arbitrary code execution.
Impact
- Disclosure of kernel memory.
- Denial of service.
- Potential remote code execution.
Affected / Fixed Versions
- Affects all Junos OS Evolved versions.
- No fixed software releases currently available.
- Workaround provided via a Python 3 script installing an iptables rule to drop TCP SYN packets with IPv4 options on non-iri interfaces.
Recommendations
- Deploy the recommended iptables-based workaround on all affected devices as detailed in Juniper Security Advisory JSA119568.
- Monitor network traffic for suspicious TCP SYN packets containing IPv4 options.
- Confirm the workaround’s persistence after system reboots and Routing Engine switchovers.
- Upgrade to fixed releases once they are made available.
7. Oracle Fusion Middleware and WebLogic Server Multiple Critical Vulnerabilities Including CVE-2026-114938 (Java4Shell) with Public Proof of Concept
Overview
- Oracle released its November 2026 Critical Security Patch Update addressing 655 vulnerabilities across multiple products.
- Critical flaws impact Oracle Fusion Middleware, WebLogic Server, Oracle Access Manager, PeopleSoft, Oracle E-Business Suite, and others.
- CVE-2026-114938 (Java4Shell) is a high-severity memory corruption vulnerability in the OpenJDK Base64 decoder that enables unauthenticated remote code execution.
- Public proof of concept available for Java4Shell increases exploitation risk.
- Other critical vulnerabilities include remote, unauthenticated access leading to confidentiality, integrity, and availability compromises in Oracle Access Manager (CVE-2026-114835, CVE-2026-91500, CVE-2026-91510), Oracle WebLogic Server (CVE-2026-91569), and PeopleSoft (CVE-2026-111497, CVE-2026-114934) among others.
Impact
- Potential full system compromise through unauthenticated remote code execution.
- Confidentiality, integrity, and availability of affected systems at risk.
- Broad impact on Oracle Database Server, Java SE, GraalVM, E-Business Suite, MySQL, Communications products, Enterprise Manager, and enterprise applications including PeopleSoft, Siebel, and Primavera.
Affected / Fixed Versions
- Detailed affected products and fixed release versions available in official Oracle advisory.
Recommendations
- Immediate application of Oracle’s November 2026 Critical Security Patch Update.
- Prioritize patching of Java4Shell (CVE-2026-114938) due to presence of public proof of concept.
- Monitor Oracle security advisories for updated information on affected versions and mitigations.
Reference links:
8. Mitel MiCollab Audio, Web and Video Conferencing Command Injection Vulnerabilities – MTLVULN-1864 (CVSS 10.0)
Overview
- Mitel released security updates addressing five vulnerabilities in MiCollab’s Audio, Web and Video Conferencing (AWV) component.
- Vulnerabilities include command injection, XML injection, arbitrary file upload, unauthorized access, and authentication bypass.
- The most critical, MTLVULN-1864, is a blind command injection allowing unauthenticated remote arbitrary command execution.
- MTLVULN-1862 permits XML injection leading to arbitrary command execution.
- Exploitation risks include compromise of system integrity, confidentiality, and availability.
- Concurrent exploitation of multiple vulnerabilities could amplify impact.
Impact
- Arbitrary command execution through unauthenticated remote attacks.
- Potential full system compromise affecting integrity, confidentiality, and availability.
- Unauthorized access to sensitive information limited to specific functionality.
- Unauthorized actions via authentication bypass.
Affected / Fixed Versions
- Affected: Mitel MiCollab Version 10.3 (10.3.0.18) and earlier, specifically AWV component.
- Fixed: Security patch available for MiCollab 10.3 (10.3.0.18) via Knowledge Base article KB000129195.
- Later releases include integrated security fixes.
Recommendations
- Apply the security patch to MiCollab 10.3 or upgrade to a later fixed release.
- Temporarily restrict external access to the AWV component to reduce risk until patches are applied.
- Follow Mitel Knowledge Base article KB000129195 for patch installation guidance.
Reference link: https://www.mitel.com/support/security-advisories/mitel-product-security-advisory-misa-2026-0012
9. GitLab CE/EE Multiple Authorization and Cross-Site Scripting Vulnerabilities – CVE-2026-105739, actively exploited
Overview
- GitLab released security updates addressing multiple vulnerabilities in Community Edition (CE) and Enterprise Edition (EE).
- Four high-severity flaws include cross-site scripting (CVE-2026-105739, CVE-2026-108153) and incorrect authorization issues in CI/CD pipeline jobs and workspaces (CVE-2026-18241, CVE-2026-97187).
- Additional medium and low severity vulnerabilities affect components including GitLab Agent Server, Maven Virtual Registry, GitLab Pages, Confluence integration, Merge Request Discussions, Package Registry, GitLab Duo Agent, and others.
- Vulnerabilities enable malicious JavaScript execution, unauthorized access to sensitive data, privilege escalation, CI/CD pipeline manipulation, credential exposure, internal network access, and denial of service.
Impact
- Exploitation allows attackers to bypass authorization controls, execute cross-site scripting attacks, escalate privileges, and cause service disruption.
Affected / Fixed Versions
- GitLab CE and EE versions prior to 19.5.6, 19.4.8, and 19.3.9 are vulnerable.
- Fixed by updates 19.5.6, 19.4.8, and 19.3.9.
Recommendations
- Immediately update GitLab CE and EE instances to version 19.5.6, 19.4.8, or 19.3.9 as applicable.
- Review CI/CD pipeline and workspace access controls.
- Monitor for indicators of compromise related to JavaScript injection or unauthorized access.
Reference link: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/
10. N-able N-central Multiple Vulnerabilities Including Local Privilege Escalation and Remote Code Execution CVE-2026-129271
Overview
- Multiple vulnerabilities affecting N-able N-central Remote Monitoring and Management (RMM) and Unified Endpoint Management (UEM) platforms.
- Issues include local privilege escalation, authentication bypass, syslog injection allowing root command execution, multiple missing authentication and authorization controls, XML External Entity (XXE) injection, Server-Side Request Forgery (SSRF), path traversal leading to remote code execution, and audit log tampering.
- CVE-2026-129271 describes a local privilege escalation in Patch Management.
- CVE-2026-129286 involves path traversal in SIS GenericFiles resulting in remote code execution.
- Several vulnerabilities enable unauthorized access, privilege escalation, command execution with root privileges, policy disclosure, user enumeration, and manipulation of audit logs.
Impact
- Attackers could bypass authentication and authorization controls.
- They may escalate privileges and execute arbitrary commands as root.
- Compromise of N-central servers and managed endpoints could occur, including unauthorized server-side requests and system manipulation.
Affected / Fixed Versions
- Affected: N-able N-central versions prior to 2026.4 Hotfix 3.
- Fixed: N-able N-central 2026.4.1.39 (Hotfix 3) or later.
- Agents and Probes updated to version 2026.4.1 HF3 or later.
Recommendations
- Upgrade N-central servers, Agents, and Probes to versions 2026.4.1.39 (Hotfix 3) or later.
- Restrict administrative access to trusted users and authorized networks.
- Review and strengthen authentication and access-control configurations.
- Monitor systems for suspicious activity and potential compromise.
- Follow official N-able security updates and guidance.
Reference links:
- https://status.n-able.com/2026/11/16/n-central-2026-4-hf3-release-notes/
- https://uptime.n-able.com/event/202669/
11. Atlassian Confluence Data Center Remote Code Execution vulnerability CVE-2026-90436 actively exploited
Overview
- Critical unauthenticated Remote Code Execution (RCE) in Atlassian Confluence Data Center caused by unsafe reflection flaw in the bundled Apache Axis 1.x SOAP library.
- Vulnerability allows remote attackers to execute arbitrary code with Confluence OS account privileges without authentication or user interaction.
- Actively exploited in the wild, confirmed by Rapid7 on November 13, 2026.
Impact
- Remote attackers can gain unauthorized access, modify data, and disrupt Confluence services.
- Exploitation can lead to sensitive information disclosure and service downtime.
Affected / Fixed Versions
- Affected: Confluence Data Center versions 1.x through 9.x when the Remote API (XML-RPC & SOAP) feature is enabled.
- Fixed: Confluence Data Center 9.2.28 and later unaffected releases; Confluence Data Center 10.x and beyond not affected.
Recommendations
- Immediately upgrade to Confluence Data Center 9.2.28 or a later unaffected version.
- If patching is not immediately feasible, disable the Remote API (XML-RPC & SOAP) setting to mitigate risk.
- Identify all Confluence Data Center deployments and verify the status of the Remote API feature.
- Prioritize patching or mitigation for internet-facing Confluence installations.
- Investigate logs for signs of exploitation or suspicious activity.
- Review other internal applications using Apache Axis 1.x; migrate to Apache Axis 2 or apply security patches as needed.
- Continuously monitor Atlassian and Apache security advisories for further guidance.
Reference link: https://confluence.atlassian.com/security/cve-2026-90436-remote-code-execution-in-confluence-data-center-1874560038.html
12. NginxPulse Unauthenticated SQL Injection Vulnerability CVE-2026-129171 (CVSS 9.3)
Overview
- A critical unauthenticated SQL injection vulnerability exists in NginxPulse, an NGINX monitoring and analytics platform.
- The flaw allows remote attackers to execute arbitrary SQL queries via the /api/stats/:type API endpoint without authentication.
- Exploitation can lead to unauthorized database access and potential file read/write on the underlying server using PostgreSQL superuser functions.
Impact
- Remote code execution and data compromise due to unauthorized SQL query execution.
- Potential full server compromise through abuse of database superuser capabilities.
Affected / Fixed Versions
- Affected: NginxPulse versions 1.5.0 through 1.6.25
- Fixed: NginxPulse version 1.6.26 and later
Recommendations
- Upgrade all NginxPulse installations to version 1.6.26 or later immediately.
- Inventory all deployments, including Docker and Docker Compose, to determine affected versions.
- Restrict access to NginxPulse management interfaces and API endpoints to trusted networks and authorized personnel.
Reference link: https://nvd.nist.gov/vuln/detail/cve-2026-129171
13. Linux Kernel TCP Networking Race Condition and Use-After-Free Vulnerability CVE-2026-99288 (NoisyTCP)
Overview
- A critical race condition vulnerability identified in the Linux kernel’s TCP networking implementation.
- The flaw involves TCP request socket reuse and concurrent packet processing, leading to use-after-free and kernel memory corruption.
- Vulnerability introduced in October 2015, affecting Linux kernel versions 4.4 and later.
- Exploitable remotely without authentication by sending crafted TCP traffic.
- Affects many Linux distributions and impacts applications relying on TCP, including Nginx, Apache, OpenSSH, and TCP proxies.
- Patch applied upstream on November 3, 2026 (commit 4e2b3ef19e0e).
Impact
- Remote kernel panic causing denial-of-service (DoS).
- Potential kernel memory corruption.
- Can disrupt containerized applications running on the host.
Affected / Fixed Versions
- Potentially affected kernels: Linux 4.4 and later, subject to vendor backports.
- Fixed stable kernel releases: 6.12.117, 6.18.63, 7.3.4.
- Fix available via upstream commit 4e2b3ef19e0e04adca38442f07dd6bc93c712bf1.
- Linux distributions may provide fixes through updated kernel packages.
Recommendations
- Immediately apply vendor-provided kernel updates that include the security fix.
- Prioritize patching internet-facing Linux servers running TCP services like Nginx, Apache, OpenSSH, and proxies.
- If patching is delayed, implement temporary mitigations:
1. Disable SYN cookies (sudo sysctl -w net.ipv4.tcp_syncookies=0) on each network namespace; note this reduces SYN flood protection.
2. Serialize to a single RX queue by reducing RX queues, and disabling RPS and RFS on external interfaces to prevent concurrent RX context races.
Reference links:
14. N-able N-central Multiple Critical Vulnerabilities Including XXE (CVE-2026-125883) and SSRF (CVE-2026-125881) with CVSS 9.3
Overview
- Multiple critical and high-severity vulnerabilities identified in N-able N-central, including XML External Entity (XXE), Server-Side Request Forgery (SSRF), OGNL injection, remote code execution (RCE), local privilege escalation, and stored cross-site scripting (XSS).
- These flaws enable arbitrary code execution and potential full system compromise.
- Both on-premises and hosted deployments are affected.
Impact
- Unauthorized access to external resources via XXE.
- Unauthorized server-side requests via SSRF.
- Remote code execution through OGNL injection and file repository upload path traversal.
- Local privilege escalation through writable syslog-ng configuration and insecure IPC channels.
- Persistent XSS through MMS3 patch metadata in administrator context.
Affected / Fixed Versions
- Affected: N-able N-central versions prior to 2026.4 HF2 (build 2026.4.1.26).
- Fixed: N-central 2026.4 HF2 (build 2026.4.1.26) and later.
Recommendations
- Upgrade to N-central 2026.4 HF2 or later immediately.
- Update all N-central Agents and Probes in hosted and on-premises environments.
- Disable the Legacy API to reduce attack surface.
- Review logs, administrative actions, and file uploads for signs of compromise.
- Monitor for and apply additional vendor security hotfixes as released.
Reference link: https://status.n-able.com/2026/11/10/n-central-2026-4-hf2-release-notes/
15. HPE Networking Private 5G Core Multiple Vulnerabilities Including Prototype Pollution CVE-2026-33228 (CVSS 9.8)
Overview
- Multiple vulnerabilities identified in HPE Networking Private 5G Core enabling denial of service, unauthorized access, information disclosure, and system integrity compromise.
- CVE-2026-33228: Critical prototype pollution in NodeJS Flatted allowing modification of global object prototypes.
- CVE-2026-49759: High severity remote stack-based buffer overflow in Erlang OTP causing BEAM VM crash.
- CVE-2026-95780: High severity authentication and session-management weaknesses permitting unauthorized access by previously authorized users.
- CVE-2026-95781 through CVE-2026-95784: High severity vulnerabilities enabling unauthorized access, information disclosure, or service disruption.
- CVE-2026-95785: High severity authenticated user exploitation to make unauthorized changes to system-managed content impacting confidentiality, integrity, and availability.
- CVE-2026-95786: Medium severity improper access control allowing unauthorized interaction with protected services and information.
Impact
- Denial of service via system crashes.
- Unauthorized access and retention of access.
- Disclosure of sensitive information.
- Integrity and availability affected through unauthorized content modifications.
Affected / Fixed Versions
- Affected: HPE Networking Private 5G Core version 1.26.1.4 and earlier.
- Fixed: Versions 1.26.2.0 or later.
Recommendations
- Update HPE Networking Private 5G Core installations to version 1.26.2.0 or later to remediate these vulnerabilities.
Reference link: https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05179en_us&docLocale=en_US
16. Zenitel IP Intercom Firmware and Connect Server OS Command Injection and Privilege Escalation Vulnerabilities, including CVE-2026-95377 (CVSS 9.4)
Overview
- Zenitel released updates addressing 11 vulnerabilities across its IP intercom firmware and Zenitel Connect server.
- Key flaws include unauthenticated OS command injection, privilege escalation, path traversal, and improper authorization issues.
- CVE-2026-95377 is an unauthenticated OS command injection via DHCP Option 66 in the EdgeAudioClient TFTP provisioning module.
- Additional issues in Zenitel Connect could allow chaining of vulnerabilities to gain root access on the server.
- No active exploitation has been reported.
Impact
- Potential for remote attackers on the same network segment to execute arbitrary commands with root privileges on affected intercom devices.
- Authenticated attackers, even with low privileges, may execute commands within application containers or escalate privileges to root on the host system.
- Administrative users could write arbitrary files as root via path traversal vulnerabilities.
- Improper JWT validation could enable assumption of PostgreSQL superuser roles, risking exposure of sensitive data including encryption keys and password hashes.
Affected / Fixed Versions
- IP Intercom Firmware: Models VSFF6, VSFF8, VSFF8MP, VSFF8MN, and VSFT with firmware earlier than 9.6.3.0 (for 9.x series) and earlier than 10.1.3.0 (for 10.x series).
- Zenitel Connect Server: All versions earlier than 1.11.0.
- Fixed versions are 9.6.3.0 or later for 9.x firmware, 10.1.3.0 or later for 10.x firmware, and Zenitel Connect 1.11.0 or later.
Recommendations
- Immediately upgrade affected intercom devices to firmware version 9.6.3.0 / 10.1.3.0 or later.
- Update Zenitel Connect server to version 1.11.0 or later to mitigate all addressed vulnerabilities.
Reference link: https://www.zenitel.com/sites/default/files/2026-11/A100K12404-Zenitel-Security-Advisory.pdf
17. PostgreSQL Type Confusion and Multiple High-Severity Vulnerabilities Including CVE-2026-6460 (CVSS 8.8)
Overview
- The PostgreSQL Global Development Group released security updates addressing 52 vulnerabilities across supported versions, alongside over 140 bug fixes.
- The most critical issue, CVE-2026-6460, is a long-standing type confusion vulnerability that allows an authenticated user with permissions to create or modify database objects to execute arbitrary code on the server with the operating system privileges of the PostgreSQL account.
- This flaw involves mishandling of composite data types and can lead to remote code execution.
- Exploitation has been demonstrated against PostgreSQL 18.6, with the vulnerability existing for approximately 22 years.
- Multiple other high-severity vulnerabilities include unauthenticated denial of service, use-after-free, SQL injection, privilege escalation, and arbitrary SQL execution risks.
Impact
- Successful exploitation of CVE-2026-6460 can result in full system compromise under the PostgreSQL service account.
- Other vulnerabilities may lead to denial of service, privilege escalation, arbitrary SQL execution, and code execution via client utilities.
Affected / Fixed Versions
- Affected versions include PostgreSQL 18.x (prior to 18.7), 17.x (prior to 17.12), 16.x (prior to 16.16), 15.x (prior to 15.20), and 14.x (prior to 14.25).
- Fixed in PostgreSQL releases: 18.7, 17.12, 16.16, 15.20, 14.25 (final release, end-of-life).
Recommendations
- Immediately upgrade PostgreSQL installations to fixed minor releases listed above.
- Rebuild or update all installed C-language extensions after database server upgrade, as these remain vulnerable if not rebuilt or updated.
- Update PostgreSQL client utilities including pg_dump, pg_restore, psql, reindexdb, and vacuumdb across all relevant systems.
- Audit and restrict database privileges to minimize permissions for creating or modifying database objects.
- Verify compatibility and security of third-party and custom C-language extensions.
- Monitor database logs for suspicious schema changes, unexpected object creation, and abnormal activity.
- Follow vendor instructions to reindex affected indexes after update.
- For incremental backups, take a new full backup post-update.
- Plan migration from PostgreSQL 14 to supported major releases due to end-of-life status.
- Confirm remediation status with managed database providers where applicable.
- Conduct vulnerability assessments to ensure all components are patched and secure.
Reference link: https://www.postgresql.org/docs/18/release-18-7.html
18. Check Point Gaia OS Local Privilege Escalation Vulnerability CVE-2026-123039 (CVSS 7.8) with Active Exploitation
Overview
- A local privilege escalation vulnerability exists in Check Point Gaia OS DynamicCLI process (dynamic_server), caused by an insecure world-writable local IPC socket (/tmp/dynamic_socket).
- The root-privileged dynamic_server does not authenticate connecting local processes and executes received commands with root privileges.
- An authenticated local user with code execution capabilities on an affected appliance can escalate privileges to root.
- Confirmed active exploitation affecting approximately two dozen customers.
Impact
- Arbitrary command execution as root by local attackers.
- Potential full system compromise of Check Point security appliances and management platforms.
Affected / Fixed Versions
- Affected versions: R82.20, R82.10, R82, R81.20, R81.10 (end of support), R81 (end of support)
- Fixed versions (Jumbo Hotfix Accumulators):
- R82.20: Take 14 and later
- R82.10: Take 52 and later
- R82: Take 132 and later
- R81.20: Take 174 and later
Recommendations
- Upgrade affected Check Point Force Firewalls (Security Gateway), Management and Log Servers, and Maestro Orchestrator to the applicable fixed Jumbo Hotfix Accumulator versions immediately.
- Investigate the /var/log/dynamicCli.log file for suspicious activity, including:
- Commands executed without the standard Clish wrapper.
- Use of the system() sink.
- Indicators such as commands containing "id;", "whoami", "/etc/shadow", "ncat", "nc -", "/dev/tcp", "curl ", "wget", "base64", "useradd", "authorized_keys".
Reference link: https://support.checkpoint.com/results/sk/sk1000362
19. USN-9182-1: nginx vulnerabilities
Overview
- Multiple vulnerabilities were discovered in nginx related to incorrect handling of certain configurations and protocol messages.
- Issues involve incorrect handling of try_files and alias directives, parsing of ClientHello messages, and certain TLS connections.
Impact
- CVE-2026-125283: Potential remote denial of service (crash) due to misconfiguration handling.
- CVE-2026-123640: Potential remote information leak through improper ClientHello message parsing.
- CVE-2026-118899: Potential remote denial of service due to TLS connection handling flaws.
Affected / Fixed Versions
- Fixes applied for Ubuntu 18.04 LTS, 20.04 LTS, 22.04 LTS, and 24.04 LTS where applicable.
Recommendations
- Update nginx to fixed versions provided in the respective Ubuntu LTS releases to mitigate denial of service and information leakage risks.
Reference link: https://ubuntu.com/security/notices/USN-9182-1
20. USN-9181-1: OpenJDK 8 vulnerabilities
Overview
- Multiple components of OpenJDK 8, including JGSS, JSSE, Hotspot, Core Java Libraries, and Compiler, were found to have improper authentication or authorization issues.
- These vulnerabilities could allow remote attackers to read or modify sensitive data or cause denial of service.
Impact
- Remote attackers may exploit these issues to access or alter sensitive information or disrupt service availability.
Affected / Fixed Versions
- OpenJDK 8 packages updated with security and bug fixes.
Recommendations
- Users should update OpenJDK 8 packages to the fixed versions to mitigate these vulnerabilities.
- Review detailed advisories and changelogs for related bug fixes and changes.
Reference link: https://ubuntu.com/security/notices/USN-9181-1
21. Hackers Exploit VMware vCenter 0-Day Since September to Hijack Admin Accounts and Steal VM Data
Overview
- A China-linked espionage group known as ARMORY CASTLE exploited a VMware vCenter Server zero-day vulnerability since early September 2026.
- The zero-day, CVE-2026-123890, allows attackers to bypass authentication and gain administrator-level access without the account password.
- Attackers used this flaw after initially breaching the network via another zero-day in BeyondTrust Remote Support (CVE-2026-102764).
- The exploitation enabled attackers to copy vCenter directory data, create admin accounts, forge SAML tokens, steal encryption material, database credentials, and access files from Windows VM virtual disks.
Impact
- The attack compromised central VMware management infrastructure, exposing multiple hosts and workloads.
- Sensitive data including Active Directory, registry, and DNS files were stolen from VM virtual disks.
- Endpoint detection on VMs may not detect access from the host level, complicating defense.
- Stolen signing keys allowed attackers to impersonate administrators and bypass multifactor authentication.
Affected / Fixed Versions
- VMware vCenter versions 9.1.1.0200, 9.0.2.0200, and 8.0 Update 3m have fixes available.
- VMware Cloud Foundation 5.2.5 updates available.
- No public fix for vCenter 7.0; affected customers need to contact support.
Recommendations
- Apply vendor patches promptly to affected vCenter and VMware Cloud Foundation versions.
- Restrict management network access to reduce exposure.
- Review logs for unusual administrator account activity, SSH access, new root SSH keys, and virtual disk access.
- Revoke sessions, replace compromised signing keys and credentials if compromise is suspected.
- Expand incident response beyond VMware systems to impacted Windows domains considering stolen Active Directory data.
Reference link: https://cybersecuritynews.com/hackers-exploit-vmware-vcenter-0-day/
22. Sean Cairncross out as national cyber director
Overview
- Sean Cairncross is leaving his role as national cyber director, which coordinates federal cybersecurity policy and strategy.
- Despite his political and national security experience, Cairncross did not have a technical cyber background.
- His office was actively involved in shaping AI security policy and protecting critical infrastructure.
- Department of Defense CIO Kirsten Davies will serve as acting director amid staff changes and debate on AI risk management.
- Cairncross helped influence a June executive order encouraging leading AI firms to submit models for voluntary government testing.
- The office also launched cybersecurity resource programs for water utilities in Texas and rural hospitals in South Carolina, reflecting the challenges of sectors with limited resources.
- Recent leadership changes follow staff departures and efforts to fill key federal cyber leadership roles.
Impact
- Transition in national cyber leadership occurs amid heightened focus on AI security, critical infrastructure protection, and ransomware threats targeting healthcare.
- The shift signals evolving federal priorities and approaches to integrating AI in cybersecurity defense without heavy regulation.
Recommendations
- Continue collaboration between government and industry on AI security measures.
- Maintain focus on security resilience in underserved infrastructure sectors.
- Fill key federal cybersecurity positions to ensure continuity in operations and policy execution.
Reference link: https://cyberscoop.com/sean-cairncross-out-national-cyber-director/
23. New Windows 11 Narrator Lock Screen 0-Day Allows Attackers to Bypass BitLocker Protections
Overview
- A new zero-day vulnerability called FastUnlock affects Windows 11 Narrator, enabling an attacker with physical access to bypass parts of the lock screen and run code without signing in.
- The flaw allows access to a running PC even when BitLocker is enabled but does not break BitLocker encryption or decrypt a powered-off drive.
- FastUnlock was tested on Windows 11 version 26H2 with November 2026 security updates; Windows 10 was not tested.
- The exploit utilizes the account recovery screen where Narrator accesses controls outside the lock screen before sign-in.
- The issue is distinct from prior BitLocker bypass vulnerabilities and currently has no associated Microsoft advisory, CVE, or patch.
Impact
- Attackers can execute code under the WsiAccount, a non-administrator account active at the lock screen.
- Does not enable takeover of signed-in user sessions, escalation to administrator rights, or full drive access.
- Targets the stage after the drive is unlocked when Windows is running, bypassing lock screen protections.
- Devices in sleep mode remain vulnerable since BitLocker startup PINs are not required on waking.
Recommendations
- Prioritize full shutdown or properly configured hibernation over sleep mode to protect unattended devices.
- Use a startup PIN alongside TPM to enhance BitLocker protection on devices at risk of physical access.
- Limit physical access to devices and monitor for official Microsoft advisories or patches addressing FastUnlock.
- Treat locked but powered-on laptops with caution, as they remain susceptible to this bypass.
Reference link: https://cybersecuritynews.com/windows-11-narrator-lock-screen-0-day/
24. VMware patches vCenter zero-day exploited in attacks since September
Overview
- Broadcom released security updates addressing a critical authentication bypass vulnerability in VMware vCenter Server.
- The vulnerability has been actively exploited by Chinese-linked hackers since September 2026.
Impact
- The flaw allows attackers to bypass authentication, potentially enabling unauthorized access to vCenter Server environments.
Recommendations
- Apply the latest security updates from Broadcom to remediate the authentication bypass vulnerability in VMware vCenter Server.
Reference link: https://www.bleepingcomputer.com/news/security/vmware-patches-vcenter-zero-day-exploited-in-attacks-since-september/
25. ASUS warns of critical hard-coded key flaw in Control Center Express
Overview
- ASUS released Control Center Express v1.7.29 to address three critical vulnerabilities in the management console.
- These flaws allow remote attackers to potentially gain administrative control over the console and the devices it manages.
Impact
- Remote attackers could take control of the management console and affected devices, posing serious security risks.
Recommendations
- Users should update to Control Center Express v1.7.29 or later to mitigate these vulnerabilities.
Reference link: https://www.bleepingcomputer.com/news/security/asus-warns-of-critical-hard-coded-key-flaw-in-control-center-express/
26. New phpAfterShell Attack Bypasses PHP2Shell Fix to Enable Remote Code Execution
Overview
- A new vulnerability named phpAfterShell enables unauthenticated remote code execution on vulnerable PHP servers, bypassing October PHP2Shell patches.
- Disclosed by Depthfirst researchers, the flaw involves PHP’s default file-based session handler and upload progress feature.
- Exploitation occurs when interrupted session file writes allow PHP to accept corrupted session files, leading to object deserialization and memory corruption.
- The attack path differs from previous PHP2Shell issues, not fixed by October updates.
- Exploitation runs code with the PHP worker’s permissions, potentially exposing credentials, application files, or customer data.
- Applications using Redis or database session storage instead of PHP file handler are not affected.
Impact
- Remote code execution on PHP servers with affected configurations.
- Potential exposure or modification of sensitive data accessible by PHP worker.
Affected / Fixed Versions
- Fixed in PHP versions 8.2.36, 8.3.37, 8.4.28, and 8.5.13.
- October PHP2Shell fixes do not mitigate phpAfterShell.
- PHP 8.0 and 8.1 are out of support and should be upgraded.
Recommendations
- Upgrade PHP to fixed versions.
- Temporarily disable upload progress (set session.upload_progress.enabled = 0) and restart PHP workers if upgrading is delayed.
- Verify PHP version serving web requests, not just command-line PHP.
- For container deployments, rebuild and redeploy with patched PHP.
- Check Linux distribution advisories for updated PHP packages.
Reference link: https://cybersecuritynews.com/phpaftershell-rce/
27. PHP security updates fix 18 flaws, including critical RCE bugs
Overview
- The PHP development team released security updates addressing 18 vulnerabilities.
- Several of these flaws are critical, enabling unauthenticated attackers to remotely execute code on vulnerable servers.
Impact
- Remote code execution allowing attackers to execute arbitrary code without authentication.
Recommendations
- Apply the latest PHP security updates promptly to mitigate these critical vulnerabilities and protect servers from remote exploits.
Reference link: https://www.bleepingcomputer.com/news/security/php-security-updates-fix-18-flaws-including-critical-rce-bugs/
28. Identity Context is Essential for Exposure Management: Tenable One Adds Ways to Bring in Identity Security Data
Overview
- Tenable One now integrates identity findings from third-party providers to enhance exposure management by including identity-related risks such as stale accounts, misconfigurations, and excessive privileges.
- Identity security is often siloed in organizations, leading to overlooked risks that attackers can exploit by chaining identity flaws with other vulnerabilities.
- The platform supports ingestion of identity data via a dedicated connector for Semperis Lightning and a customizable open connector for other sources.
- Semperis Lightning monitors Active Directory and Microsoft Entra ID for identity risks, feeding severity-rated findings into Tenable One for prioritization alongside other security issues.
Impact
- Enables organizations to see identity risk as part of the overall exposure landscape to better prioritize remediation and reduce attack surfaces.
- Reduces the chance of ignoring identity exposures by consolidating all security findings in one platform.
- Supports continuous synchronization between identity security findings and exposure management state.
Recommendations
- Incorporate identity security data into exposure management programs to address combined risks effectively.
- Use Tenable One connectors to integrate trusted identity tools like Semperis Lightning or custom sources.
- Prioritize remediation of high-severity identity-related exposures alongside other vulnerabilities using Tenable One dashboards and reporting.
Reference link: https://www.tenable.com/blog/identity-context-is-essential-for-exposure-management-tenable-one-adds-ways-to-bring-in
29. USN-9175-1: Linux kernel (Oracle) vulnerabilities
Overview
- Multiple security issues were discovered in the Linux kernel affecting a wide range of subsystems, including device drivers, architectures, file systems, networking, security modules, and various kernel frameworks.
- Vulnerabilities potentially allow attackers to compromise the system.
- The update corrects flaws in many components such as ARM64, PowerPC, RISC-V, x86 architectures, MediaTek and Mellanox network drivers, USB drivers, file system implementations like Ext4 and BTRFS, SELinux and AppArmor security modules, and many others.
- The fixes cover a broad set of CVEs spanning from 2024 to 2026.
Impact
- Exploitation of these vulnerabilities could lead to system compromise.
Recommendations
- Apply the provided Linux kernel update from Ubuntu Security Notices promptly to mitigate the issues.
Reference link: https://ubuntu.com/security/notices/USN-9175-1
30. PHP Fixes 7 Critical Flaws, Including Bugs That Could Allow Remote Code Execution
Overview
- The PHP Foundation issued security updates addressing seven critical vulnerabilities.
- These flaws could enable remote code execution on impacted PHP versions.
- The update covers all supported PHP versions under certain conditions.
Impact
- Successful exploitation could allow attackers to execute arbitrary code remotely, potentially compromising affected systems.
Recommendations
- Users and administrators should promptly apply the released security updates to mitigate these critical vulnerabilities.
Reference link: https://thehackernews.com/2026/11/php-fixes-7-critical-flaws-including.html
31. Drupal Patches Critical Installer Flaw That Could Give Unauthenticated Attackers Control of Sites
Overview
- A critical vulnerability in Drupal core allows unauthenticated attackers to use the built-in installer to attempt a site reinstall.
- This flaw can lead to site takeover or remote code execution.
- The vulnerability affects uncommon configurations.
- Fixed releases for all supported Drupal branches have been released.
Impact
- Potential site takeover
- Remote code execution risk
Recommendations
- Apply the fixed Drupal releases as soon as possible to mitigate the vulnerability.
Reference link: https://thehackernews.com/2026/11/drupal-patches-critical-installer-flaw.html
32. ClamAV Vulnerabilities Affecting Cisco Products: November 2026
Overview
- Multiple vulnerabilities in ClamAV allow remote attackers to bypass configured file and scan time limits.
- These vulnerabilities can cause denial of service (DoS), interrupting scanning operations.
- Cisco Secure Endpoint Connector software on Windows, Linux, and Mac platforms is affected; Secure Endpoint Private Cloud is not impacted.
- The Security Impact Rating (SIR) is High on Windows due to privileged context execution, and Medium on Linux and Mac due to lower privileges.
Impact
- Denial of Service conditions affecting scanning operations.
- Elevated risk on Windows platforms due to privileged process execution context.
Affected / Fixed Versions
- Cisco has released software updates addressing these vulnerabilities in affected platforms.
Recommendations
- Apply Cisco’s updates to Secure Endpoint Connector software on all affected platforms.
- No workarounds are available.
33. Government tech debt is a national security risk
Overview
- The FBI has detected and disrupted multiple Chinese state-sponsored cyberattacks targeting U.S. critical infrastructure in recent years, including PlugX, Flax Typhoon, and Volt Typhoon campaigns.
- These attacks often exploit vulnerabilities in federal government networks, which are hampered by outdated, complex, and fragmented IT systems.
- Federal agencies frequently operate multiple generations of technology simultaneously, combining legacy databases, cloud environments, and managed services without clear integration or security mapping.
- Approximately 80% of the federal IT budget is spent on maintaining and securing existing systems rather than modernizing them.
- Adversaries are leveraging agentic AI tools to automate reconnaissance and accelerate exploitation before defenses can respond.
Impact
- The fragmented and outdated federal IT infrastructure increases the risk of successful penetration and diminishes network resilience during crises.
- Slower modernization and complex procurement processes hinder defense capabilities and quick recovery.
- Potential strategic vulnerabilities emerge as adversaries exploit government tech debt.
Recommendations
- Federal cyber investment and technology modernization should be prioritized with urgency comparable to traditional defense acquisition.
- Procurement processes must be streamlined to adopt trusted security technologies rapidly.
- Vendor contracts should enforce clear accountability to quickly identify responsible parties post-breach.
- Reducing platform duplication can shrink the attack surface without compromising capability.
- Applying faster, cost-effective acquisition standards will enhance cybersecurity posture and operational resilience.
Reference link: https://cyberscoop.com/government-tech-debt-national-security-risk-op-ed/
34. How CISA is prioritizing companies for talks about security improvements
Overview
- CISA has identified about 100 critical infrastructure companies for discussions on system hardening based on their importance to national economy, public health, safety, and security.
- The selection was based on input from the Homeland Defense Working Group and intelligence on what cyber adversaries value most, including pre-positioning and R&D targets.
- Engagements include right sector risk management agencies and span multiple interdependent entities, such as port operators alongside energy and telecommunications providers.
- Focus areas include resilience, minimum viability, and collective investment strategies as outlined in CISA’s "CISA 2030" strategy.
- Conversations have incorporated CI-Fortify assessments emphasizing planning for isolation and recovery.
Impact
- Enhanced prioritization and coordinated efforts expected to improve resilience of critical infrastructure to cyber threats.
Recommendations
- Encourage collaborative security planning across interconnected sectors.
- Leverage insights from assessments to develop isolation and recovery strategies.
- Continue fostering dialogue to refine investment and resilience priorities.
Reference link: https://cyberscoop.com/cisa-100-critical-infrastructure-companies-fed-talks/
35. Huntress Delivers 24/7 Response for Microsoft Defender Incidents Across Endpoints and Microsoft 365
Overview
- Huntress Agentic Security Platform integrates data from multiple Microsoft Defender services including Defender for Identity, Office 365, Cloud Apps, and Entra ID Protection.
- This integration enhanced detection capabilities, revealing a token-replay campaign impacting 97 accounts across 79 organizations.
Impact
- The exposure of a multi-organization token-replay attack campaign demonstrates improved visibility and threat detection by Huntress leveraging Defender incident data.
Recommendations
- Organizations should consider integrated threat response platforms that consolidate alerts from various endpoint and cloud identity security solutions to improve detection and response.
Reference link: https://www.huntress.com/blog/huntress-response-for-microsoft-defender-incidents-across-endpoints-and-microsoft-365
36. Cisco Informational for Emergency Distrust of eMudhra Root and Intermediate Certificate Authorities
Overview
- In October 2026, a critical security compromise of eMudhra-managed Certificate Authorities was disclosed.
- A security researcher found that private keys for eight eMudhra intermediate certificates were vulnerable due to a flawed Key Generation Ceremony from April 2025.
- This flaw allows attackers to brute-force these private keys within seconds.
- Cisco reviewed its products and found no affected products outside those listed in the advisory.
Impact
- Potential compromise of certificates issued by the vulnerable eMudhra intermediate CAs due to exposed private keys.
- Could undermine trust in affected certificates and enable man-in-the-middle attacks or impersonation.
Recommendations
- Refer to the advisory for the latest updates and mitigation steps.
- Monitor for product-specific guidance and updates from Cisco and eMudhra.
- Replace affected certificates and distrusted eMudhra CAs as per outlined procedures.
37. CVE-2026-84869 in ScreenConnect Exploited to Run Malicious Files on MSP Technician Accounts
Overview
- Huntress confirmed active exploitation of CVE-2026-84869 targeting Managed Service Provider (MSP) technicians through ScreenConnect.
- The attack chain and Indicators of Compromise (IOCs) have been detailed to assist defenders.
Impact
- Attackers can run malicious files on MSP technician accounts, potentially compromising MSP environments and their clients.
Recommendations
- Review provided IOCs and apply recommended mitigations to protect MSP teams from this exploitation.
Reference link: https://www.huntress.com/blog/cve-2026-84869-screenconnect-technician-exploitation
38. From view-only access to container root: five vulnerabilities in ONLYOFFICE Docs (FIXED)
Overview
- Rapid7 reported five vulnerabilities in ONLYOFFICE Docs that allow an attacker with view-only document access to chain exploits resulting in arbitrary OS command execution as root within the official DocumentServer container.
- Vulnerabilities include native file read and Session JWT forgery, conversion parameter injection leading to code execution, path traversal with arbitrary file write, root-helper command injection, and view-only export of non-rendered document data.
- An attacker can steal server files and document data not normally visible to viewers, even when downloading is disabled.
- The official container image version 9.4.0 was tested, with exploitation demonstrated; fixes were confirmed in Document Server 10.0.
- Proof-of-concept code is available on GitHub, and the findings were responsibly disclosed.
Impact
- Attackers can escalate from view-only access to root command execution inside the container.
- Stealing the Session JWT signing key enables forging credentials with unauthorized document permissions.
- Unauthorized access to sensitive server files can compromise system security.
- Exfiltration of incomplete or hidden document content is possible despite disabled download permissions.
Affected / Fixed Versions
- Tested version: onlyoffice/documentserver:9.4.0
- Fixed in Document Server 10.0
Recommendations
- Upgrade to ONLYOFFICE Document Server 10.0 or later.
- Review JWT key management and token validation processes.
- Restrict access to /docbuilder and ensure proper permission checks.
- Monitor container and server logs for suspicious access patterns.
Reference link: https://www.rapid7.com/blog/post/ve-from-view-only-access-to-container-root-five-vulnerabilities-in-onlyoffice-docs-fixed
AI SOC
1. What Is Preemptive MDR? A Guide For Security Leaders
Overview
- Preemptive MDR integrates exposure context, threat intelligence, AI-assisted investigation, and human expertise to enable more proactive and prioritized cybersecurity operations.
- It connects asset and vulnerability information with threat investigations to better assess urgency and guide remediation efforts.
- AI accelerates the investigation process by retrieving, correlating, and organizing logs and activity data, enabling parallel and agentic-style analysis.
- Human analysts remain central for validation, decision-making, and overseeing AI contributions.
Impact
- Improves prioritization of weaknesses and threat hunting based on real-time asset criticality and attacker behavior.
- Enhances clarity on ownership and remediation tracking of vulnerabilities uncovered during investigations.
- Facilitates containment, detailed analysis, and mitigation of incidents through AI-assisted but expert-validated workflows.
Recommendations
- When selecting a preemptive MDR provider, require transparency on how exposure context influences investigations and how AI is employed with oversight.
- Confirm clearly defined responsibilities about incident response and remediation ownership to balance security with business impact.
- Regularly review evidence of exposures resolved before exploitation, threats contained, and vulnerabilities addressed.
Reference link: https://www.rapid7.com/blog/post/dr-what-is-preemptive-mdr-security-leaders-guide
2. Why AI-ROC Is the Future of Exposure Management
Overview
- Security teams face a huge surge in vulnerability disclosures, increasingly accelerated by frontier AI models surfacing vulnerabilities and attackers exploiting them within hours.
- Traditional remediation processes are too slow, with manual handoffs and ticketing causing delays that enable attacker success.
- Qualys introduces the AI-native Risk Operations Center (AI-ROC) operating model designed to detect, validate, prioritize, and remediate vulnerabilities autonomously and at machine speed.
- AI-ROC relies on three AI agents: Agent Insta for near real-time detection without rescanning, Agent Val for production-safe exploit validation to hyper-prioritize truly exploitable risks, and Agent Sara for automated, low-risk remediation with rollback and patch reliability scoring.
Impact
- Vastly reduced time from vulnerability disclosure to remediation, compressing weeks-long SLAs to hours or days.
- Dramatically fewer findings to review by triaging millions of vulnerabilities down to those confirmed exploitable in the environment.
- Increased confidence in remediation through patch reliability scores, compensating controls visibility, and rollback capabilities.
- Provides a unified platform eliminating delays from multiple tool handoffs, critical for countering attacker speeds accelerated by AI.
Recommendations
- Adopt AI-ROC-style operational models integrating AI agents across detection, validation, and remediation to address current exposure management inefficiencies.
- Use real-time detection with AI agents to continuously monitor advisories and asset inventory without waiting for scheduled scans.
- Employ exploit validation to confirm actual risk and prioritize effectively.
- Automate remediation with patch reliability scoring, rollback, and policy-controlled deployment waves to balance speed and safety.
Reference link: https://blog.qualys.com/product-tech/2026/11/18/ai-roc-future-of-exposure-management
3. Fix Tenable One findings where developers work: Tenable and OpenAI Daybreak Defense Factory
Overview
- Tenable One findings can now be imported into OpenAI Daybreak Defense Factory via a local Codex Security CLI, preserving key details like description, solution, and file context.
- The integration aims to bridge the gap between security teams identifying vulnerabilities and developers fixing them by enabling developers to access precise security findings directly where they code.
- Findings include severity, state, Tenable’s description and remediation guidance, file paths, and line numbers where available.
- Daybreak Defense Factory assists developers in prioritizing, investigating, and proposing fixes for code issues based on imported Tenable findings.
- OpenAI’s connector for Tenable One is open source and leverages the Inventory Export API or CSV exports for importing data.
Impact
- Streamlines vulnerability remediation by reducing context loss and duplicated triage efforts between security and development teams.
- Enhances developer productivity by integrating security findings directly into their workflow.
- Facilitates faster and more accurate remediation of code security issues.
Recommendations
- Tenable One customers should leverage the OpenAI Daybreak Defense Factory connector to import findings directly into their development environment.
- Follow OpenAI’s setup guide to export and import findings using the Codex Security CLI.
- Regularly refresh findings imports to maintain updated vulnerability status in the development workflow.
Reference link: https://www.tenable.com/blog/openai-connector-tenable-one-codex-security
4. Security for the Agentic Era, Powered by Microsoft Perception
Overview
- AI technologies are rapidly accelerating vulnerability discovery and exploitation, compressing exploit development from months to minutes.
- Attackers increasingly use autonomous AI agents capable of running entire attack campaigns, raising the stakes for defenders.
- Microsoft’s new cyber stack integrates signals, context, and collaborative AI agents (red, blue, and green teams) orchestrated by Microsoft Perception for automated, agentic security operations.
- Microsoft Perception enables simulation of attacks, automated alert triage and investigation, and automated remediation in a closed-loop system, allowing security teams to operate at machine speed while maintaining control.
- The stack includes foundational capabilities such as the Integrated Security Operations Center in Microsoft Defender, with SIEM, UEBA, and threat intelligence capabilities supporting the transition to an agentic SOC.
- New AI-driven initiatives in Perception help organizations close security gaps and manage AI-induced risk through playbooks, vulnerability shielding, and prioritized exposure reduction, spanning multiple cloud platforms.
Impact
- Significantly reduces time required for vulnerability exploitation, increasing the urgency for rapid detection and response.
- Facilitates automated, collaborative SOC functions powered by AI agents, augmenting human analysts’ effectiveness.
- Addresses risk from AI-powered attackers and AI agents with broad access that can be compromised or manipulated.
Recommendations
- Adopt agentic security operations with coordinated AI agents and automated playbooks to respond at machine speed.
- Close critical security gaps proactively with AI Readiness Initiatives and vulnerability shielding.
- Leverage integrated capabilities across Microsoft Defender, Sentinel, and the broader ecosystem to enhance situational awareness and operational efficiency.
- Implement governance and guardrails to maintain human oversight over high-impact automated actions.
Reference link: https://www.microsoft.com/en-us/security/blog/2026/11/17/security-for-the-agentic-era-powered-by-microsoft-perception/
5. Tenable One Adversary View brings Claude Mythos’ adversarial reasoning to your environment
Overview
- Tenable One Adversary View, accessible via Tenable Hexa AI, uses Claude Mythos’ AI model to perform adversarial reasoning on existing vulnerability scan data.
- It constructs an on-demand graph of asset connections, identifies vulnerability chains, choke points, and prioritizes fixes to disrupt the highest number of attack paths.
- The solution goes beyond rule-based attack path analysis by reasoning dynamically, mimicking attacker behavior in real time.
- It offers remediation guidance including patches, configuration changes, and integration with Jira and ITSM tools for workflow automation.
- Users can narrow analysis scope by tags, IP ranges, or business units and interact with the AI for follow-up prioritization and risk assessment.
Impact
- Enables security teams to prioritize vulnerability remediation based on attack path disruption rather than severity alone.
- Provides a focused approach to reducing risk by identifying critical chokepoints and highest-leverage fixes.
- Demonstrated finding complex multi-hop attack paths including exploitation scenarios like EternalBlue.
Recommendations
- Organizations using Tenable One and Tenable Hexa AI should utilize Adversary View for on-demand, AI-powered attack path analysis.
- Scope analysis to critical assets or business units to understand and remediate highest-risk attack pathways.
- Leverage integration capabilities to automate ticketing and remediation tracking, improving security operations efficiency.
Reference link: https://www.tenable.com/blog/tenable-one-adversary-view-claude-mythos-break-attack-paths
AI Threat Landscape
1. Navigating Vulnerability Hysteria in the AI Era
Overview
- The Reporters’ Notebook video series episode discusses the aftermath of recent high-severity vulnerability disclosures.
- It explores how fears around AI-assisted exploits contribute to widespread panic and operational disruptions.
- The episode highlights increasing warning fatigue among security professionals due to the heightened volume and severity of alerts.
Impact
- Security teams experience operational challenges caused by panic-driven responses.
- Warning fatigue may reduce the effectiveness of vulnerability management and response efforts.
Recommendations
- Develop calibrated responses to AI-related vulnerability disclosures to avoid overreaction.
- Improve prioritization and filtering of alerts to combat warning fatigue.
Reference link: https://www.darkreading.com/vulnerabilities-threats/navigating-vulnerability-hysteria-ai-era
2. 30 Years of Gatekeeper Asymmetry Doom: The Paradox that Makes Powerful LLMs More Vulnerable
Overview
- Discusses the principle of gatekeeper asymmetry doom in information security, where less powerful vetting systems are consistently outmatched by the systems they evaluate.
- Describes historical and contemporary examples, from simple hash-based antivirus methods to complex static binary analysis and limitations of pattern matching tools like YARA.
- Explains how even advanced AI models (frontier LLMs) face inherent limits in fully analyzing or vetting malicious code due to fundamental computational theory.
- Highlights the ongoing arms race where attackers exploit these asymmetries, using polymorphism and obfuscation techniques to bypass detection.
- Recommends minimizing the power gap between gatekeepers and targets, potentially leveraging advanced AI capabilities but acknowledging persistent challenges.
Impact
- Highlights the persistent and fundamental difficulty in defending against adversarial inputs that are more computationally powerful or obfuscated than vetting mechanisms.
- Illustrates vulnerabilities in static detection methods and AI-powered analysis that could be exploited by sophisticated attackers.
Recommendations
- Recognize and address "doomed" attack surfaces by increasing gatekeeper power or using it more effectively.
- Continue enhancing AI and other vetting systems while understanding their theoretical and practical limitations.
Reference link: https://research.checkpoint.com/2026/30-years-of-gatekeeper-asymmetry-doom-the-paradox-that-makes-powerful-llms-more-vulnerable/