# Threat Watch by Helix — Vulnerabilities

> Live security incidents: actively exploited vulnerabilities, breaches and supply-chain attacks — patch status, fixed versions and what to do, curated by Helix Cyber.

All endpoints are public JSON/XML/text with CORS enabled; no auth. Poll changes.json at most hourly with If-None-Match (every response carries an ETag).

## Categories

Every incident has exactly one `category`.
- Vulnerabilities (`patch`): 1924 incidents, 52 live. Flaws in software you may run — which versions are affected, the fixed release, and what to do first. Page https://helix.ml/threat-watch?c=patch · RSS https://helix.ml/threat-watch/c/patch/feed.xml · JSON Feed https://helix.ml/threat-watch/c/patch/feed.json · changes https://helix.ml/threat-watch/c/patch/changes.json · llms.txt https://helix.ml/threat-watch/c/patch/llms.txt
- Breaches (`breach`): 1200 incidents, 128 live. Attacks on companies and services. Nothing to patch on your side; rotate credentials and watch for follow-on phishing if you are a customer. Page https://helix.ml/threat-watch?c=breach · RSS https://helix.ml/threat-watch/c/breach/feed.xml · JSON Feed https://helix.ml/threat-watch/c/breach/feed.json · changes https://helix.ml/threat-watch/c/breach/changes.json · llms.txt https://helix.ml/threat-watch/c/breach/llms.txt
- Supply chain (`supply-chain`): 514 incidents, 334 live. Compromised packages, releases, build pipelines and certificates. Check what you depend on and what you trust. Page https://helix.ml/threat-watch?c=supply-chain · RSS https://helix.ml/threat-watch/c/supply-chain/feed.xml · JSON Feed https://helix.ml/threat-watch/c/supply-chain/feed.json · changes https://helix.ml/threat-watch/c/supply-chain/changes.json · llms.txt https://helix.ml/threat-watch/c/supply-chain/llms.txt

## Data

- All incidents: https://helix.ml/threat-watch/incidents.json
- One incident: https://helix.ml/threat-watch/i/<slug>.json (timeline, sources, `agentBrief` markdown)
- Update stream: https://helix.ml/threat-watch/changes.json
- Fields: severity (critical|high|medium|low|unknown), patchStatus (patched|partial|unpatched|no-fix-needed|unknown), status (live|closed), exploited, stacks, tags, cveIds, affectedVersions, fixedVersions, actions.
- Incidents marked `auto: true` were generated from an authoritative catalog (CISA KEV, Have I Been Pwned) and not yet reviewed by an editor.

## Use with your AI

Poll changes.json hourly with ETag; for each new change, fetch the incident JSON, compare `stacks`, `product`, `affectedVersions` and `cveIds` against the systems and dependencies you manage, and alert only when one matches. Follow `actions`.

## Live incidents (52)

### [critical] Check Point gateways: PHP2Shell chain to root, webshells and ESXi wiper (CVE-2026-109618, CVE-2026-123039)
https://helix.ml/threat-watch/i/php2shell-check-point-gateways-attackers-chain-php-rce-local-privesc-to-root-deploy-webshells-and-wiper-cve-2026-109618 · Vulnerabilities · patched · since 2026-11-12 · CVE-2026-109618, CVE-2026-109619, CVE-2026-114713, CVE-2026-123039
From 30 October 2026 an attacker hit Check Point Security Gateways whose Mobile Access portals were still unpatched, using PHP2Shell as the entry point (Check Point Research says the activity is consistent with CVE-2026-109618 and CVE-2026-109619) and then escalating from the portal service account to root through the DynamicCLI IPC interface (CVE-2026-123039, a Check Point local flaw). The operator dropped base64 PHP webshells into the portal's template directory, installed the TSGA backdoor and its TSProxy networking component (modified PhiliKit variants that ESET has associated with China-nexus UNC5221, although Check Point says several attributes do not fit that group), pivoted from the gateway to a VMware ESXi host over SSH, and ran a file-destroying wiper (destroy_v6) that left a Hebrew-language note bearing the Dream Security brand. The first wave, on 30 October, hit Israeli organisations and included destructive activity; a second scanning wave on 2 November reached organisations in several countries with no destructive activity. The gateway campaign began roughly a week after the 21 October PHP fixes, so it is not part of the pre-patch exploitation window reported for PHP2Shell generally. Check Point Research, which published on 12 November, says the true nature of the operation cannot be assessed with high confidence: the actor may have run the whole campaign, acted solely as an initial access broker, or staged a false flag, and the destructive stage may be a smoke screen. The PHP flaws are in CISA KEV (added 26 October). PHP's fixed branches are 8.2.35, 8.3.36, 8.4.27 and 8.5.12; PHP 8.1 and older receive no upstream releases. Check Point's CVE-2026-123039 fix is in Jumbo Hotfix Accumulators, and a documented workaround exists.
Fixed: PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35 (PHP Group, 2026-10-21); Check Point SK1000362 (CVE-2026-123039): R82.20 Take 14+, R82.10 Take 52+, R82 Take 132+, R81.20 Take 174+
Do: Patch PHP to 8.2.35, 8.3.36, 8.4.27 or 8.5.12 (or a vendor backport). PHP 8.1 and older get no upstream releases: upgrade them or take them offline.; Patch Check Point gateways to a Jumbo Hotfix Take that includes the CVE-2026-123039 fix (SK1000362: R82.20 Take 14+, R82.10 Take 52+, R82 Take 132+, R81.20 Take 174+; R81.10 and R81 are end-of-support with no take listed). If you cannot patch, SK1000362 documents a workaround (stop dynamic_server and stop it restarting); verify the exact command in the SK first, because it breaks the Dynamic CLI commands in sk144112.; Hunt the Mobile Access portal: zz*.tpl files in the portal templates directory, /tmp/.up.tpl, challenge_render.tpl in the portal directory, PHP session files with the upload_progress_pwn marker under /opt/CPcvpn-*/tmp/, TSGA artifacts (/tmp/CPconfigdaemon, slot_CPconfigdaemon in the boot persistence directory, TCP 11072, /tmp/.p_sock) and /lib/libcpfwcommon.so.; Review ESXi hosts reachable from gateways: SSH logins by the vpxuser account, /tmp/des wiper staging, destroy_v6 execution and DREAM_ANNEXATION.txt files. Treat any hit as a destructive incident.; Remove internet exposure of gateway management and Mobile Access portal interfaces. Monitor for scanning from 00:00 to 09:00 UTC, the window in which Check Point saw the activity concentrated.

### [critical] Apache Shiro: DefaultLdapRealm accepts any password with auth caching enabled (CVE-2026-129349)
https://helix.ml/threat-watch/i/apache-shiro-defaultldaprealm-accepts-any-password-with-auth-caching-enabled-cve-2026-129349 · Vulnerabilities · patched · since 2026-11-14 · CVE-2026-129347, CVE-2026-129348, CVE-2026-129349
Apache disclosed three Shiro flaws on 2026-11-14. The critical one, CVE-2026-129349 (CVSS 4.0 9.1 as published by Apache on oss-sec), affects DefaultLdapRealm and JndiLdapRealm only when authenticationCachingEnabled is set to true, which is not the default. After an account has logged in successfully once, the cached authentication path skips the LDAP bind, and the AllowAllCredentialsMatcher that the realm installed by default accepts any password, so anyone who knows that username can sign in as it. Apache fixed it in 3.0.1 by no longer installing that matcher by default; 3.0.1 was tagged on GitHub on 2026-08-23, about twelve weeks before the advisory, and its release notes do not name the CVE. The two companion low-severity issues (CVE-2026-129347 for empty stored credentials matching empty passwords, CVE-2026-129348 for PropertiesRealm reloads that keep removed users and narrowed permissions) are fixed in 3.0.2, tagged 2026-11-08. No exploitation or public proof of concept was found, and NVD had not yet analysed the CVEs at research time. Action: upgrade to 3.0.2; if on the LDAP realm, keep authentication caching off or configure a credentials matcher that checks the cached data.
Fixed: 3.0.1 (CVE-2026-129349); 3.0.2 (CVE-2026-129347, CVE-2026-129348)
Do: Upgrade Apache Shiro to 3.0.2 or later (3.0.1+ covers the LDAP realm flaw); If you use DefaultLdapRealm/JndiLdapRealm with authenticationCachingEnabled=true, disable caching or configure SimpleCredentialsMatcher immediately; Avoid storing empty credentials and reject empty passwords at the application layer; If using PropertiesRealm, verify reloads correctly remove deleted users and narrowed permissions

### [critical] Copeland Dixell XWEB EVO: 14 disclosed flaws give root on refrigeration controllers
https://helix.ml/threat-watch/i/dixell-xweb-evo-refrigeration-controller-flaws-14-vulns-give-root-access-two-actively-exploited · Vulnerabilities · partial · since 2026-11-13
VulnCheck published details of 14 vulnerabilities in Copeland's Dixell XWEB EVO supervision system, which it says give root or administrative access in lab testing with rebuilt firmware. CyberScoop, reporting on 2026-11-13, gives CVSS scores of 8 to 9.8 without per-flaw scores and lists no CVE IDs. CyberScoop also says at least two of the flaws are known to be exploited in the wild, but it names no source for that claim. VulnCheck researcher Valentin Lobstein looked into the XWEB login, and VulnCheck says it and Lobstein notified Copeland and Dixell and helped fix the problems before disclosure. Copeland confirmed that certain XWEB monitoring solutions are affected, says patches are available, and urges customers to take devices off the public internet and update. The sources publish no fixed version number, and legacy unpatched versions remain exposed. Separately, an active campaign against refrigeration controllers (CERT-FR, 2026-10-12; CISA and partner fact sheet, 2026-11-05) lists Copeland/Dixell XWEB units among the targeted families, but neither source names these 14 flaws or EVO as the entry vector. XBOW researcher Max Günther ran internet-facing honeypots that imitate these controllers and logged exploit probes and login attempts within a day of deployment.
Do: Immediately apply the latest Copeland/Dixell XWEB EVO firmware and software patches; Ensure XWEB controllers and supervisory systems are not exposed to the public internet; restrict to isolated OT networks; Review access logs for signs of exploitation or unauthorized temperature-setting changes; Enforce strong, unique credentials and disable legacy unpatched versions; Monitor industrial controllers for anomalous probes and login attempts

### [high] Dropbear: per-destination forwarding limits bypassed via unix sockets, docker.sock reachable
https://helix.ml/threat-watch/i/dropbear-permitopen-permitlisten-bypass-via-unix-socket-forwarding-docker-sock-reachable · Vulnerabilities · unpatched · since 2026-11-13
A researcher's oss-sec post dated 2026-11-13 says Dropbear's unix-socket forwarding (direct-streamlocal and streamlocal-forward) checks only the coarse no-port-forwarding flag and never the permitopen or permitlisten lists that TCP forwarding enforces, so an authorized_keys entry restricted to one TCP destination can still open unix sockets. The author tested only HEAD commit 99baf182 (2026-11-11), built from source on a local rig. The test key was limited to permitopen 127.0.0.1:1; after the account was added to the docker group, the same key reached /var/run/docker.sock and got a Docker API response, while a non-permitted TCP destination was refused. Reach to Docker therefore depends on host configuration (the account must be able to use the socket), not on the key alone. The author describes commit 796a89ef (2024-04-03) as an incomplete fix. The commit page shows it changes src/svr-tcpfwd.c and the manpage, not src/svr-streamfwd.c as the write-up says. No CVE, vendor advisory, upstream response or fixed version was found, and the Dropbear 2026.93 release notes do not mention this behavior. The author's suggested mitigation is to refuse streamlocal channels for keys that carry per-destination restrictions. The test harness and logs are not published in the post.
Do: Audit authorized_keys for keys carrying permitopen/permitlisten restrictions on Dropbear servers and treat them as unrestricted for unix-socket forwarding until patched; Remove unix-socket forwarding capability for restricted accounts (e.g. disable DROPBEAR_SVR_LOCALSTREAMFWD/REMOTESTREAMFWD at build time or restrict via server options); Restrict OS-level access to sensitive unix sockets (docker.sock, database sockets) for accounts holding restricted SSH keys — e.g. remove from docker group; Monitor for direct-streamlocal@openssh.com and streamlocal-forward@openssh.com channel requests in Dropbear logs; Track upstream Dropbear for a fix adding path-based permit restrictions in svr-streamfwd.c

### [critical] Apache HTTP Server mod_http2 RCE and mod_vhost_alias/mod_md flaws disclosed (CVE-2026-119618 et al.)
https://helix.ml/threat-watch/i/apache-http-server-mod-http2-rce-and-mod-vhost-alias-mod-md-flaws-disclosed-cve-2026-119618-et-al · Vulnerabilities · patched · since 2026-11-11 · CVE-2026-106023, CVE-2026-109163, CVE-2026-119618, CVE-2026-63292
On 2026-11-11 the Apache HTTP Server project released httpd 2.4.71, which fixes three CVEs disclosed the same day on oss-security. The most serious is CVE-2026-119618, rated critical by Apache and CVSS 9.8 by Red Hat. It is a thread-safety flaw in mod_http2 assign_headers(). For a body-less HTTP/2 request that has Content-Type but no Content-Length, a worker thread writes a synthesised "Content-Length: 0" into the stream's shared header table instead of the request's private copy. When that table is full, the write takes memory from the connection's lock-free allocator while the connection thread is using it, which corrupts the child process heap. Red Hat says public research has shown a reliable exploit against a default-configured server with mod_http2 enabled. The flaw affects httpd 2.4.55 through 2.4.70 and standalone mod_h2 2.0.8 through 2.0.42, and is reachable without authentication. Only servers that negotiate HTTP/2 through the Protocols directive (h2 or h2c) are affected; the httpd default is http/1.1. Red Hat rates RHEL 9 and 10 Important, because their mod_http2 builds give each stream its own allocator, and says RHEL 8 and earlier are not affected. A public reproduction lab (googlesky/CVE-2026-119618) appeared on 2026-11-12. It demonstrates heap corruption under ASan and TSan, not a working RCE exploit. The fix is a one-line change in httpd 2.4.71. Standalone mod_h2 has no fixed release, because the repository was archived in June 2026 at v2.0.42. Debian has the fix only in sid (2.4.71-1); bookworm, trixie and forky are still marked vulnerable. The same release fixes CVE-2026-106023 (important, mod_md NULL pointer dereference crash, 2.4.30 through 2.4.70) and CVE-2026-109163 (low, mod_vhost_alias one-byte stack overwrite, 2.4.69 and 2.4.70, a follow-up to CVE-2026-63292). No in-the-wild exploitation has been reported.
Fixed: Apache HTTP Server 2.4.71 (released 2026-11-11; fixes CVE-2026-119618, CVE-2026-106023 and CVE-2026-109163); Debian sid apache2 2.4.71-1
Do: Upgrade Apache HTTP Server to 2.4.71 (released 2026-11-11), which fixes CVE-2026-119618, CVE-2026-106023 and CVE-2026-109163. Before relying on a distro package, confirm it carries the fix: on 2026-11-12 Debian stable (bookworm, trixie) was still unpatched.; If you cannot patch now and do not need HTTP/2, remove h2 and h2c from every Protocols directive, including those inside VirtualHost blocks, and reload. The PoC author verified this workaround in their lab. Servers that serve only http/1.1 (the httpd default) are not affected.; Find HTTP/2-enabled httpd first: run `apachectl -M | grep http2`, grep the configuration for `Protocols.*h2`, and check internet-facing hosts with `curl -sI --http2 https://host` (it reports HTTP/2 when h2 is negotiated).; Standalone mod_h2 users have no fixed module release (repository archived, last tag v2.0.42). Move to httpd 2.4.71's bundled mod_http2. Disregard third-party claims of a mod_h2 2.0.43.; RHEL 8 and earlier are not affected. RHEL 9 and 10 are rated Important; apply the httpd/mod_http2 errata as Red Hat ships them.; Patch internet-facing servers that negotiate HTTP/2 first. A public lab now shows exactly which requests trigger the corruption.

### [high] PostgreSQL 14-18 update: 52 CVEs fixed, many allow code execution by a database user
https://helix.ml/threat-watch/i/postgresql-bulk-security-update-fixes-52-cves-incl-many-rce-flaws · Vulnerabilities · patched · since 2026-11-12 · CVE-2026-116303, CVE-2026-116304, CVE-2026-116306, CVE-2026-116307, CVE-2026-116308, CVE-2026-116309, CVE-2026-116310, CVE-2026-116311, CVE-2026-116312, CVE-2026-116313, CVE-2026-116314, CVE-2026-116315, CVE-2026-116316, CVE-2026-116317, CVE-2026-116318, CVE-2026-116319, CVE-2026-116320, CVE-2026-116321, CVE-2026-116322, CVE-2026-116323, CVE-2026-116325, CVE-2026-116326, CVE-2026-116327, CVE-2026-116328, CVE-2026-116329, CVE-2026-116330, CVE-2026-116331, CVE-2026-116332, CVE-2026-116333, CVE-2026-116335, CVE-2026-116336, CVE-2026-120139, CVE-2026-120141, CVE-2026-120142, CVE-2026-120143, CVE-2026-120144, CVE-2026-120145, CVE-2026-120146, CVE-2026-120147, CVE-2026-120148, CVE-2026-120149, CVE-2026-120150, CVE-2026-120151, CVE-2026-120152, CVE-2026-120153, CVE-2026-120154, CVE-2026-14661, CVE-2026-16237, CVE-2026-16240, CVE-2026-18447, CVE-2026-6460, CVE-2026-6467
On 12 November 2026 the PostgreSQL Global Development Group released 18.7, 17.12, 16.16, 15.20 and 14.25, plus 19 RC 2, fixing 52 security vulnerabilities and over 140 bugs. About 30 of the CVEs are memory-safety or type-confusion flaws scored CVSS 8.8 that can run code as the operating-system user running the database; most need a database account that can create objects or run SQL, and no CVE scores 9.0 or above. Other fixes cover SQL injection in pg_dump, reindexdb and extension scripts, privilege bypasses in row security, DROP OWNED and REASSIGN OWNED, and a dblink/subscription file-append issue. The only unauthenticated item is a denial-of-service restart (CVE-2026-116322, CVSS 5.3). PostgreSQL 14 is end-of-life with this release. No exploitation is reported. Some fixes need post-update steps (reindexing, new backups for incremental backups), so read the release notes before upgrading.
Fixed: 18.7; 17.12; 16.16; 15.20; 14.25; 19 RC 2
Do: Upgrade all PostgreSQL deployments to 18.7, 17.12, 16.16, 15.20 or 14.25 (or 19 RC 2 for testing); prioritise databases where untrusted users can create objects or run SQL; Plan migration off PostgreSQL 14, which is now end-of-life; Review the release notes and apply required post-update steps (reindexing, new full backup before incremental backups); Restrict CREATE privileges and untrusted SQL execution, and avoid restoring untrusted dump or archive files, until patched; Rebuild or restore workflows using patched pg_dump, pg_restore and pg_basebackup clients

### [critical] Citrix NetScaler November 2026 patches: Console auth bypass and ADC/Gateway memory flaws (CVE-2026-120869 et al.)
https://helix.ml/threat-watch/i/citrix-netscaler-november-2026-patch-batch-12-flaws-incl-auth-bypass-and-dos-cve-2026-120868-et-al · Vulnerabilities · patched · since 2026-11-12 · CVE-2026-107407, CVE-2026-107408, CVE-2026-107409, CVE-2026-107410, CVE-2026-107412, CVE-2026-107415, CVE-2026-118268, CVE-2026-118269, CVE-2026-120864, CVE-2026-120868, CVE-2026-120869
Citrix shipped fixes on 2026-11-12 for a batch of NetScaler and Secure Access Client flaws. Press coverage counts 12 flaws; the full per-CVE list is only partly confirmed because the Citrix bulletin was not readable as text. The one flaw in NVD so far is CVE-2026-120869, an authentication bypass in NetScaler Console: NVD says an unauthenticated attacker can bypass authentication controls and reach restricted resources (CVSS v4.0 9.3 in NVD, 9.4 in press reports). The NetScaler ADC and Gateway memory-corruption flaws are rated 9.3 to 9.5 in press lists and are described as causing denial of service or unpredictable behavior. No source reviewed describes any of them as remote code execution; press summaries say CVE-2026-107412 and CVE-2026-120868 need no login, and neither is in NVD yet. Two local privilege-escalation flaws in Secure Access Client, CVE-2026-118268 (Windows, to SYSTEM) and CVE-2026-118269 (Linux, to root), are rated 8.5 and need a low-privileged local account. Citrix reports no known exploitation and no public proof of concept has been confirmed. None of the listed IDs is in the CISA KEV catalogue snapshot of 2026-11-10, which predates the batch, so that check is point-in-time only. The Hacker News reports that Citrix attributes the fixes to AI-assisted code review; that detail could not be re-checked against the bulletin. Patch NetScaler ADC and Gateway to 14.1-73.57 or 13.1-64.39 (FIPS builds 14.1-73.58 FIPS, FIPS/NDcPP builds 13.1-37.293), NetScaler Console to 14.1-74.34, and Secure Access Client to 26.11.1.6 (Windows; one advisory mirror shows 26.11.16, so confirm against the bulletin) or 26.10.4 (Linux).
Fixed: NetScaler ADC/Gateway 14.1-73.57+, 13.1-64.39+; NetScaler ADC FIPS 14.1-73.58 FIPS+; NetScaler ADC FIPS/NDcPP 13.1-37.293 FIPS & NDcPP+; NetScaler Console 14.1-74.34+; Secure Access Client Windows 26.11.1.6+; Secure Access Client Linux 26.10.4+
Do: Upgrade NetScaler ADC and NetScaler Gateway to 14.1-73.57 or later, or 13.1-64.39 or later. FIPS builds need 14.1-73.58 FIPS or later; FIPS/NDcPP builds need 13.1-37.293 or later.; Upgrade NetScaler Console to 14.1-74.34 or later, and restrict network access to it until the upgrade is done, because CVE-2026-120869 is an unauthenticated authentication bypass.; Upgrade Secure Access Client for Windows to 26.11.1.6 or later and for Linux to 26.10.4 or later.; Review DNS/DoH, NetScaler Push, Email OTP and ICA proxy configurations on ADC and Gateway, and limit their exposure until patched.; After patching, check internet-facing appliances for signs of compromise from before the upgrade. Citrix reports no known exploitation, so treat this as a precaution, not a finding.

### [critical] N-able N-central: unauthenticated root RCE and Windows SYSTEM exploits work on Hotfix 2 (CVE-2026-90436)
https://helix.ml/threat-watch/i/4everable2shell-agent2shell-n-able-n-central-new-root-rce-and-windows-system-exploits-work-against-patched-servers-cve-2 · Vulnerabilities · partial · since 2026-11-12 · CVE-2026-90436
N-able is investigating a second set of N-central flaws, published by researcher Sean Bales days after it shipped 2026.4 Hotfix 2 (build 2026.4.1.26) for the earlier Able2Shell set. He says two new proofs of concept, 4EverAble2Shell and Agent2Shell, still work against that build. 4EverAble2Shell gives unauthenticated remote code execution as root on the N-central server, but only where the Legacy API is turned on and reachable from the internet, which N-able says is not the default. Agent2Shell chains more than ten zero-days to run commands as NT AUTHORITY\SYSTEM on managed Windows agents if the attacker knows the target appliance ID. Previdian reports probing from 157.20.241[.]16 within hours of the PoC release. The observed chain used the Apache Axis 1.x flaw CVE-2026-90436 for initial access, then a root step, then a curl download of a shell script. No successful exploitation is confirmed. Hosted environments are not affected by the server issue. The reporting reviewed names no vendor hotfix for the new flaws. N-able urges customers to disable the Legacy API.
Fixed: 2026.4.1.26 (Hotfix 2) fixes seven of the 33 Able2Shell flaws (see the Able2Shell record); no fix announced for 4EverAble2Shell or Agent2Shell in the reporting reviewed; CVE-2026-90436: upstream commit 41f3b4e8 to apache/axis-axis1-java; Axis 1.x is end-of-life and the project will not release a 1.x fix (per NVD)
Do: Disable the Legacy API on every internet-exposed N-central on-premise server now (Administration > Mail and Network Settings > Network Security > LEGACY APIS). N-able says it is off by default and not recommended.; Keep N-central at 2026.4.1.26 or later and apply further N-able updates as they ship. Hotfix 2 does not stop the reported PoCs, per the researcher.; CVE-2026-90436 (Apache Axis 1.x): the project will not release a 1.x fix. Apply the upstream commit 41f3b4e8 or migrate to Axis 2, and confirm whether the N-central SOAP stack depends on Axis 1.x.; Block and monitor traffic to and from 157.20.241[.]16 and watch for probe activity against N-central; Restrict N-central and Legacy API exposure to the public internet via firewall or VPN; Review managed Windows agents for signs of SYSTEM-level command execution

### [medium] SANSAR: Linux cryptomining orchestrator with kernel rootkit, Tor C2 and Ethereum-based backdoor
https://helix.ml/threat-watch/i/sansar-linux-cryptomining-orchestrator-with-kernel-rootkit-tor-c2-and-ethereum-based-backdoor · Vulnerabilities · no-fix-needed · since 2026-11-12
Elastic Security Labs (tracked as REF3364) describes one Linux cryptomining intrusion spanning three GPU hosts. The entry point was a Ray job agent reachable from the internet that accepted job submissions without authentication. Between October 22 and 25, 2026 the actor used it to run commands, send GPU inventory to an external server and open a reverse shell, then added an SSH key to the Ray session account for persistence. The report does not say how the actor obtained root. With root, the actor installed SANSAR, a Rust orchestrator that receives commands over a Tor onion service and supervises XMRig (CPU) and SRBMiner-MULTI (GPU) miners; its commands include interactive shells and raw TCP SYN flood tasks. A kernel module (acpi_thermal_mgr) hides selected processes, files and sockets, and a replaced NVML library reports 0% GPU utilization with randomised temperature and power readings, so nvidia-smi looks idle while the GPUs mine. A separate backdoor, netns, looks up its controller address in an Ethereum smart contract through public RPC services and then connects directly over TCP; this is the Ethereum element of the title. No CVE or vendor patch is involved. The fix is to remove unauthenticated internet exposure of Ray job submission and to hunt the affected hosts for the artifacts Elastic lists.
Do: Take Ray's job-submission interface off the internet and require authentication; check whether any job agent on a GPU host accepted submissions without it; Check GPU hosts for /opt/vadi_/, the acpi_thermal_mgr kernel module (DKMS build; source under /usr/src/acpi_thermal_mgr-1.0/) and a netns systemd service; Verify libnvidia-ml.so.1 against the vendor package and look for /usr/lib/.libnvidia-ml.so.1.backup; compare nvidia-smi readings with GPU power draw and process load; Review authorized_keys for accounts that own Ray sessions, and Ray job logs for nvidia-smi output sent to external hosts; Block Tor egress and outbound HTTPS to public Ethereum RPC endpoints from GPU servers, and match the SHA-256 hashes in Elastic's indicator table

### [high] Windows CLFS: unpatched SignDrop zero-day grants SYSTEM and reportedly bypasses tamper protection
https://helix.ml/threat-watch/i/signdrop-windows-clfs-authentication-mitigation-zero-day-grants-system-privileges-and-edr-tamper-protection-bypass · Vulnerabilities · unpatched · since 2026-11-10
On 2026-11-10 a researcher publishing as Nightmare Eclipse (MSNightmare) posted a public proof-of-concept called SignDrop, with a write-up, for a local privilege escalation in the Windows Common Log File System (CLFS) driver; BleepingComputer covered it on 2026-11-12. As the researcher describes it, the bug abuses the CLFS logfile-authentication mitigation that Microsoft began shipping in updates from 2025-10-28: it makes a privileged process such as Windows Defender open a log, which causes the .cnpf authentication file to be created with SYSTEM rights while inheriting the original file's permissions, and he says this also gets past antimalware tamper protection. The PoC needs code execution as a standard user first, so it is a second-stage tool rather than a remote entry point. The researcher reports it works on Windows 11 26H2 and Windows Server 2025 builds, and his claim that about 80% of Windows installations are exposed is an unmeasured estimate. Third-party reports are mixed. Mallory relays that Howler Cell (Cyderes) reproduced a SYSTEM shell on 2026-11-12 and that 78researchlab found it works but is noisy, since every UAC prompt opened both a standard-user and a SYSTEM shell; we could not retrieve either firm's own post. The tamper-protection bypass is a claim that no source we read has verified; Shield53 repeats it without testing. As of the latest sources (2026-11-13) there is no CVE, no CVSS score, no Microsoft statement or patch, and no CISA KEV entry, and no in-the-wild exploitation has been reported. Microsoft's documentation says the mitigation's Mode registry value 0 is enforcement and 1 is learning, and that disabling it (value 2) is not recommended.
Do: Check HKLM\SYSTEM\CurrentControlSet\Services\CLFS\Authentication\Mode. Microsoft Learn documents 0 = enforcement, 1 = learning and 2 = disabled by an administrator; the researcher and ThreatDefence treat 0 and 1 as the exposed states (not independently verified); Do not run the public PoC on production or corporate endpoints; treat it as hostile code and block or alert on its execution; Apply Microsoft's patch as soon as it is released; monitor for the fix; Keep the CLFS authentication mitigation enabled: Microsoft Learn says disabling it is not recommended, and the researcher says disabling it would re-expose systems to CLFS memory-corruption attacks; Monitor privileged processes (e.g., Defender) for unexpected file creation in log directories and watch for tamper-protection bypass attempts; Restrict which processes can open CLFS log files where feasible

### [critical] Red Hat Quay: unauthenticated service-key takeover forges registry tokens (CVE-2026-123710)
https://helix.ml/threat-watch/i/red-hat-quay-key-server-flaw-lets-attackers-forge-registry-tokens-and-steal-private-container-images-cve-2026-123710 · Vulnerabilities · partial · since 2026-11-11 · CVE-2026-110697, CVE-2026-123710
Red Hat rates CVE-2026-123710 Critical (CVSS 3.1 9.8) in the service key server of Red Hat Quay. Key rotation accepts any JWT signed by an already-approved service key that carries the expected audience and issuer, and it never checks that the token is a rotation credential. An anonymous token from /v2/auth passes that check, so a caller who can reach the /keys endpoint can install a signing key of its own, with no expiry and inherited approval. Registry tokens signed with that key are then accepted for every repository, which allows reading and overwriting private images and tags, and the rogue key survives restarts. Red Hat's exposure condition is that /keys is reachable by untrusted clients, and anonymous access is one route to a token rather than the only one. Red Hat lists Quay 3 and Quay 5 as affected. SecurityWeek reports no exploitation in the wild and no public proof-of-concept. The fix is merged to the upstream quay/quay master branch (PR #8056, 2026-11-11), but no tagged release contains it as of 2026-11-12, and Red Hat names no fixed build for this CVE. The same merge fixes CVE-2026-110697, a separate authenticated flaw (CVSS 9.9) that lets a namespace-name wildcard expose other tenants' robot tokens; Red Hat names fixed builds 3.9.28 through 3.18.3 for that one only. Until a fixed build ships, restrict access to /keys, audit service_key_rotate and service_key_delete events, and remove any unrecognised approved key.
Do: Restrict network access to the /keys service-key endpoint at the proxy or load balancer so only trusted internal components can reach it; Review audit events service_key_rotate and service_key_delete, especially any with a null expiration_date, and remove every approved service key you do not recognise; Expect reinstalled keys: deleting a rogue key is not durable until a fixed build is deployed, because the anonymous request can install a new one. Watch for disrupted pushes and pulls; Treat images and secrets in affected registries as potentially exposed, and rotate credentials embedded in images; Apply the fixed Quay build as soon as one ships. The fix for CVE-2026-123710 is on master (quay/quay PR #8056) but is not in any tagged release as of 2026-11-12

### [critical] PTC Windchill/FlexPLM: critical deserialization RCE patched (CVE-2026-126325)
https://helix.ml/threat-watch/i/ptc-windchill-flexplm-critical-deserialization-rce-patched-cve-2026-126325 · Vulnerabilities · patched · since 2026-11-12 · CVE-2026-12569, CVE-2026-126325
PTC published a patch on 2026-11-11 for CVE-2026-126325, a critical remote code execution flaw in Windchill and FlexPLM caused by deserialization of untrusted data (CVSS v4 9.2, CVSS v3.1 9.0). PTC applied the fix itself to PTC-hosted instances; self-hosted customers have to apply it, following eSupport article CS483249. That article needs a PTC login and could not be read for this review, so the affected and fixed release lines are not confirmed here. Neither the PTC notice nor the press coverage reviewed says the flaw is exploited or that a public proof of concept exists, and it is not in CISA KEV. The same product line carries CVE-2026-12569, which is in KEV with known ransomware use and was exploited by Cl0p-linked actors to drop JSP web shells and take product data. PTC's trust center also lists a separate RCE, CVE-2026-77645, and an SSRF, CVE-2026-77646, from August 2026. The trust center does not say whether this patch relates to either.
Do: Apply the PTC patch for CVE-2026-126325 now if you self-host Windchill or FlexPLM (PTC eSupport CS483249; a Windchill administrator applies it). Confirm the fixed build for your release line in that article.; Monitor hosts for code execution, backdoor access and JSP web shells. PTC's trust center lists hunt patterns for CVE-2026-12569 webshells under /Windchill/login/.; Apply network restrictions to limit exposure if patching is not immediately possible; Review whether the environment was exposed to CVE-2026-12569 (KEV, ransomware use) and hunt for compromise indicators

### [critical] Zoom Workplace for Windows: unauthenticated privilege escalation (CVE-2026-108186, CVE-2026-108187)
https://helix.ml/threat-watch/i/asus-router-firmware-flaws-zoom-workplace-for-windows-privilege-escalation-cve-2026-108186 · Vulnerabilities · patched · since 2026-11-10 · CVE-2026-108186, CVE-2026-108187
Zoom published two bulletins on 2026-11-10 for Zoom Workplace for Windows. CVE-2026-108186 (CVSS 9.6 per Zoom and NVD) is an improper input validation flaw that lets an unauthenticated attacker over the network escalate privilege. CVE-2026-108187 (CVSS 8.1) is an origin validation error with the same effect. Both CVSS 3.1 vectors require user interaction, so the attack needs a victim action. CVE-2026-108186 affects versions from 7.1.0 up to 7.1.8; CVE-2026-108187 affects versions before 7.1.5. Version 7.1.8 and later carries fixes for both. Neither Zoom nor SecurityWeek reports exploitation, neither CVE is in the CISA KEV catalog (checked against the 2026.11.10 feed), and NVD still lists both as awaiting analysis.
Fixed: Zoom Workplace for Windows 7.1.8 or later (fixes both CVEs)
Do: Update Zoom Workplace for Windows to 7.1.8 or later, which carries the fixes for both CVEs; Inventory Windows endpoints running Zoom Workplace below 7.1.8, since the affected range starts at 7.1.0

### [high] Windows 10 KB5131096 ESU: November 2026 security fixes, plus PowerShell and NTLM signing changes
https://helix.ml/threat-watch/i/windows-10-kb5131096-esu-november-2026-patch-tuesday-fixes-incl-actively-exploited-outlook-zero-day · Vulnerabilities · patched · since 2026-11-10
Microsoft's KB5131096, released 2026-11-10, is the cumulative update for Windows 10 version 22H2 under Extended Security Updates and for Windows 10 Enterprise and IoT Enterprise LTSC 2021. It moves builds to 19045.7846 and 19044.7846. The KB's change list covers an Active Directory printer-install failure (error 87), Intune control of the trusted .rdp publisher thumbprint policy, RDS shadow-connection failures on Windows Server 2016 and 2012 R2, a Cuba time-zone rule change, and the remaining USB Audio Class 1.0 symptoms from September. Two changes can break working setups. PowerShell signature validation can now reject scripts that were accepted before because they are not valid UTF-8 with a byte order mark, so they must be re-saved and re-signed. NTLM message signing is now offered by default for non-anonymous connections, which can affect legacy clients. The package also carries Microsoft's November security fixes for these Windows 10 builds; by our reading of Microsoft's CVRF, 30 of the CVEs mapped to it are rated Critical and none is marked exploited. The actively exploited Outlook zero-day, CVE-2026-124194, belongs to Microsoft 365 Apps and Office LTSC 2021 and 2024 and is not in this package.
Fixed: 19045.7846; 19044.7846
Do: Install KB5131096 (builds 19045.7846 and 19044.7846) on Windows 10 22H2 ESU and Enterprise or IoT Enterprise LTSC 2021 devices. It requires servicing stack 19044.6088 or later, and the combined SSU KB5132689 ships with it; Patch Outlook separately: CVE-2026-124194 is fixed in the November Microsoft 365 Apps and Office LTSC 2021/2024 updates, not in KB5131096. Until then, warn users about unexpected message files and consider blocking outbound NTLM to untrusted destinations; Re-save PowerShell scripts as UTF-8 with a byte order mark and sign them again before relying on signature validation after this update; Audit for non-anonymous NTLM connections that are not signed, since signing is now offered by default, and test legacy clients before broad rollout; After installing, verify AD-published printer installs, Intune RDP publisher policy, RDS shadow connections where used, and USB Audio Class 1.0 devices; For Dynamic Update installs, include boot.stl on the installation media, or secure boot validation can fail with 0xc0430001

### [critical] N-able N-central: 33 flaws with public PoCs, unauthenticated XXE-to-RCE; 7 of 33 fixed in Hotfix 2
https://helix.ml/threat-watch/i/able2shell-n-able-n-central-30-zero-days-published-hosted-environments-taken-offline · Vulnerabilities · partial · since 2026-11-09 · CVE-2026-125878, CVE-2026-125879, CVE-2026-125880, CVE-2026-125881, CVE-2026-125882, CVE-2026-125883, CVE-2026-91000
A researcher publishing as Oracle-Security put proof-of-concept exploits for 33 alleged zero-day flaws in N-able's N-central RMM on GitHub on 8-9 November 2026, all tested on pre-release appliance 2026.4.0.31. Press reports name the researcher as Sean Bales; N-able does not name him. The worst chain needs no credentials: an unauthenticated XXE in service import can reset an account, run code as the nable user, and add an enabled Default Administrator. N-able took Hosted N-central offline on 9 November as a precaution and told on-premises customers to keep their servers offline until upgraded. On 10 November it released N-central 2026.4 Hotfix 2 (build 2026.4.1.26), which fixes seven CVEs: CVE-2026-125883, CVE-2026-125878, CVE-2026-125879, CVE-2026-125880, CVE-2026-125881, CVE-2026-125882 and CVE-2026-91000 (CVSSv4 8.3 to 9.3). N-able has not said which of the other 26 flaws the hotfix covers, and a follow-up hotfix has been promised with no date. N-able says hosted servers are upgraded and back in service, and that it has no evidence of customer exploitation, while its status page tracks scanning tied to the published code. Beazley and watchTowr report exploitation attempts against N-central honeypots, and Previdian reports attempts against a decoy; none of these is a confirmed customer compromise. Five older N-central CVEs in CISA KEV (including CVE-2026-86218) are separate; Tenable says it is not known whether Able2Shell relates to them. Apply Hotfix 2 to on-premises servers (agents and probes first), check authentication activity from 8 November onward, and restrict access to service-import endpoints until the follow-up fix ships.
Fixed: 2026.4.1.26 (N-central 2026.4 Hotfix 2, released 2026-11-10; fixes seven of the 33 flaws)
Do: Upgrade on-premises N-central to 2026.4 Hotfix 2 (build 2026.4.1.26), agents and probes first; N-able says keep an on-premises server offline until it is upgraded; Treat Hotfix 2 as partial: N-able has not mapped the other 26 flaws to a fix and the follow-up hotfix has no date; track N-able's status page and apply it when it ships; Until then, restrict N-central exposure and block unauthenticated access to service-import (SOAP) endpoints; Check login and authentication activity from 2026-11-08 onward, and look for new admin accounts, unexpected script execution and Take Control sessions on managed endpoints; Review firewall and edge logs for XXE and SOAP-endpoint probes; the source IPs and endpoints are published by Beazley Security Labs and Previdian; Review downstream customer environments that N-central manages for unauthorized scripts or access; earlier N-central exploitation was seen spraying scripts into managed environments

### [critical] MongoDB Server: unauthenticated use-after-free in replica set catch-up, crash or code exec (CVE-2026-118383)
https://helix.ml/threat-watch/i/cve-2026-118383-mongodb-server-unauthenticated-use-after-free-in-replica-set-primary-catch-up-can-crash-or-execute-code · Vulnerabilities · patched · since 2026-11-10 · CVE-2026-118383
MongoDB published CVE-2026-118383 on 2026-11-10, together with fixed releases on each branch from 4.4 to 9.0 that the vendor lists as affected. The bug is a use-after-free in the replication code that runs when a newly elected replica set primary finishes catching up on writes it missed. The vendor's CVE text says requests that need no authentication can reach it, and that the outcome is a server crash or, under certain conditions, arbitrary code execution. Datadog Security Labs reproduced the crash on 8.0.34 in a four-member lab: two unauthenticated ping requests carrying readConcern.afterOpTime left stale waiters on one member, and a failover that made that lagging member primary segfaulted it. The same two requests were rejected with Unauthorized on 8.0.37. The attacker cannot create the lag or the election, so the crash needs a member to fall behind and then win an election, which is why the CVSS attack complexity is High. Datadog did not demonstrate code execution. Standalone mongod is not affected. MongoDB said it was not aware of exploitation when it announced the fix, and the CISA KEV catalogue has no entry for this CVE. Fix: upgrade every replica set member, including shard and config server members and members offline during maintenance, to the fixed release for its branch, then confirm the running versions. Until then, limit network access to MongoDB to the systems that need it; that reduces who can send the requests but does not fix the bug. Atlas clusters are upgraded automatically during maintenance, according to MongoDB.
Fixed: 9.0.7; 8.3.16; 8.0.37; 7.0.48; 6.0.30; 5.0.35; 4.4.32
Do: Upgrade every replica set member (including shards, config servers, containers, and members offline during maintenance) to the fixed release for your branch and verify running versions; Until upgraded, restrict network access to MongoDB to only the systems that need it; Monitor MongoDB logs for COMMAND 'Slow query' events (ID 51803) with command.ping, readConcern.afterOpTime, and MaxTimeMSExpired/MaxTimeMSExpired errName indicating planted waiters; If deferring maintenance (e.g. on Atlas), apply the upgrade promptly

### [medium] 'Smart Eye' Overseas Chinese Affairs platform: leaked files describe UFWD AI profiling of diaspora talent
https://helix.ml/threat-watch/i/overseas-chinese-affairs-big-data-platform-smart-eye-ccp-ai-system-scrapes-diaspora-data-to-scout-spies-in-taiwan-chip-i · Vulnerabilities · no-fix-needed · since 2026-11-11
NetAskari, a research group, says internal documents leaked to it describe the Overseas Chinese Affairs Big Data Platform, which it calls 'Smart Eye', run from Jinan University's Big Data Center and attributed to the United Front Work Department. Its published analysis says the platform uses big-data analysis of social media, news and other open sources, including AI-supported web scraping, to build profiles of overseas Chinese and to pick 'fruitful' targets among foreign academics and think-tank staff. Dark Reading reports that the platform scraped Instagram, Facebook, X, Weibo and WeChat through rotating foreign proxies and produced profiles of ethnic-Chinese chip-sector talent, including Skymizer executives, Taiwanese university students and a Microsoft AI research center director, with approaches through hometown, alumni and professional networks. Those specifics are not in the NetAskari excerpt and were not checked against Dark Reading. The leaked documents are not published, and the NetAskari excerpt does not say how they were obtained or verified. This is influence and recruitment activity rather than a technical breach, so no patch applies.
Do: Review insider-risk and foreign-influence exposure for staff with ties to Chinese diaspora networks, especially in semiconductor and AI roles; Harden social media privacy practices for executives and researchers in strategic industries; Brief leadership and security teams on UFWD recruitment and influence tactics (hometown/alumni/professional association approaches); Monitor for anomalous data-scraping infrastructure and proxy networks targeting your organization's online presence; Coordinate with government counterintelligence channels if approached by suspected influence actors

### [high] pappl-retrofit: path traversal in PPD add/delete lets attackers write or delete files (CVE-2026-123747)
https://helix.ml/threat-watch/i/cve-2026-123747-pappl-retrofit-directory-traversal-in-add-delete-ppdfiles-actions-lets-attackers-write-delete-arbitrary · Vulnerabilities · partial · since 2026-11-11 · CVE-2026-123747
pappl-retrofit, OpenPrinting's library for turning classic CUPS PPD drivers into Printer Applications, does not sanitise filenames in its add-ppdfiles and delete-ppdfiles actions. Each name is joined to the PPD storage directory as-is, so ../ sequences let a client write or delete files outside it. The GitHub advisory (GHSA-wxj6-x3wg-4vmc, published 2026-11-11, CVE-2026-123747) includes a working curl proof of concept, and says an uploaded PPD with a cupsFilter setting can also lead to command execution. Affected: versions up to and including 1.0b2. Authentication is contested: NVD and the advisory text describe the service as unauthenticated and running as root by default, but the advisory's CVSS vector requires low privileges. Red Hat's rating (CVSS 7.3, Important) assumes high privileges and user interaction, and says default RHEL 10, CentOS Stream 10 and Fedora installs are not exposed because the storage directory /var/lib/legacy-printer-app/ppd is not created by default. The advisory scores the flaw 9.6 (critical). NVD and Red Hat, the only independent scorers, rate it 7.3 (high). No in-the-wild exploitation is reported, and the flaw is not in CISA's KEV catalogue (the copy checked predates disclosure). The fix is commit c65a28f on master. No release containing it is listed in the sources checked, so upgrade once one ships.
Do: Check whether pappl-retrofit (<= 1.0b2) is installed, including as the legacy-printer-app service, and whether /var/lib/legacy-printer-app/ppd exists; Restrict network access to pappl-retrofit's web and IPP interfaces until a fixed release is installed; If building from source, apply fix commit c65a28f on master; Upgrade to the first release that includes c65a28f (none is listed in the sources checked); Check logs for add-ppdfiles or delete-ppdfiles requests with ../ in the filename

### [critical] Xen Orchestra: crafted cookie logs in as a token owner with admin rights (VSA-2026-062)
https://helix.ml/threat-watch/i/xen-orchestra-auth-bypass-vsa-2026-062-vates-attackers-bypass-auth-via-crafted-cookie-take-over-xcp-ng-hosts-as-root-cve · Vulnerabilities · unknown · since 2026-11-10
Vates' security advisory VSA-2026-062 (rated Critical, no CVE assigned) describes an authentication bypass in Xen Orchestra and the Xen Orchestra Appliance. The REST cookie parser turns a crafted authenticationToken cookie (an empty JSON object) into an empty object, and the token lookup treats that as an unfiltered query and returns the first unexpired login token, so the request is authenticated as that token's owner with admin rights. Anyone who can reach the management API can then list reusable login token IDs and act as an administrator. The vendor states the flaw is being actively exploited by an unnamed actor, and warns that this can lead to code execution on managed pools and root takeover of XCP-ng hosts. The exploitation leaves no log entries, so detection depends on HTTP inspection and the published indicators. The vendor names Xen Orchestra 6.9.1 (stable) and 6.10.0 (latest) as fixed. The upstream fix (PR #10748) was merged on 2026-11-10, after the 6.10.0 release date, so the fixed release has not yet been confirmed from a public changelog. Discovered by TDC NET Security (Filip Magic, Christoffer Olsen).
Fixed: Xen Orchestra 6.9.1 (stable), 6.10.0 (latest); xo-server 5.211.2, 5.213.1
Do: Upgrade Xen Orchestra and XOA to a build that contains the VSA-2026-062 fix (advisory: 6.9.1 stable, 6.10.0 latest; xo-server 5.211.2 / 5.213.1), then confirm the running xo-server version. Do not treat 6.10.0 as fixed until a release containing PR #10748 is confirmed; If patching is delayed, keep Xen Orchestra on a dedicated management network, not the internet, and block 91.211.251.112 (port 8001) and the listed onion endpoint; Add WAF or reverse-proxy rules for authenticationToken=j:{} and authenticationToken=j:%7B%7D; the advisory warns that regex rules can be bypassed with other encodings; Hunt for the IOCs: authenticationToken=j:{} in HTTP logs; a VM named pivot2; hvm_serial: file VM configs; /etc/cron.d/zz-ustar and zz-ustar2, /.ustar5, /.ustar6 and /etc/ld.so.preload on XCP-ng hosts. Absence of IOCs does not prove a host is clean; If compromise is suspected, rotate all passwords and secrets used by the platform, including proxy, backup, S3, root and user accounts

### [critical] Barracuda appliances: auth bypass and command injection chain to root (CVE-2026-116606, CVE-2026-111560)
https://helix.ml/threat-watch/i/barracuda-esg-and-appliance-flaws-allow-root-access-via-admin-interface-cve-2026-116606-cve-2026-111560 · Vulnerabilities · patched · since 2026-11-02 · CVE-2026-111560, CVE-2026-116606
Barracuda's advisory of 2 November 2026 covers two flaws that, used together, let an attacker bypass authorization and reach root on affected appliances. CVE-2026-116606 is an authentication bypass in Email Security Gateway (ESG) firmware before 9.4.0.030 that lets an unauthenticated network attacker restore a crafted backup through the configuration-import function and change the global configuration. CVE-2026-111560 is an OS command injection through the timezone field that runs as root and needs administrator access. Six products are in scope: ESG, Load Balancer ADC, Message Archiver, WAF Control Center, Web Application Firewall and Web Security Gateway. Barracuda has released patches for all of them. Barracuda's own advisory says exploitation requires access to an affected product's administrative interface and advises restricting that interface to trusted networks; Mandiant's advisory for CVE-2026-116606 instead describes exposure to unauthenticated remote attackers and scores it CVSS 4.0 9.3. On 9 November Barracuda updated its advisory to say it has identified exploitation activity affecting a small number of organizations; it names no actor, per-CVE detail or indicators. CISA added both CVEs to its KEV catalog on 10 November, with a federal remediation due date of 13 November under BOD 26-04. CVE-2023-2868 and CVE-2023-7102 are 2023 ESG flaws that BleepingComputer mentions as background (UNC4841); they are not part of this advisory. SecurityWeek, citing Previdian, reports 17 attempts against CVE-2026-116606 from 15 IP addresses in three countries between 9 and 11 November; that figure comes from one secondary report and has not been checked against Previdian's own publication.
Fixed: ESG 9.4.017+ (BNSF-40425); ESG <9.4.017 via patch BNSF-40430; Load Balancer ADC and WAF (BNADC-16586); Message Archiver (BNMA-32468); WAF Control Center (BNWF-60060); Web Security Gateway (BNYF-24789)
Do: Apply the vendor patches now: ESG BNSF-40425 (9.4.017+) or BNSF-40430 (<9.4.017); BNADC-16586 for Load Balancer ADC and WAF; BNMA-32468 for BMA; BNWF-60060 for WCC; BNYF-24789 for WSG; Federal agencies: meet the CISA KEV due date of 2026-11-13 for both CVEs under BOD 26-04, including CISA forensic triage; Restrict administrative interfaces to trusted internal networks with network access controls, since Barracuda's advisory makes admin-interface reach a precondition and Mandiant calls CVE-2026-116606 unauthenticated; Confirm each device runs the latest firmware with all security patches applied (Barracuda Campus has the manual steps; Barracuda Support handles version checks); Check appliances for unauthorized configuration changes, unexpected restored backups and unexpected admin activity; Treat internet-reachable ESG admin interfaces as potentially compromised: Barracuda reports exploitation, so review for the unauthorized configuration changes and restored backups above and engage Barracuda Support if anything looks off

### [critical] Plone: anonymous visitor can run code on the server via CMFEditions modifier and sandbox escapes
https://helix.ml/threat-watch/i/plone-rce-chain-via-cmfeditions-modifier-and-allow-module-sandbox-escapes-anonymous-attackers-can-run-code-on-server · Vulnerabilities · patched · since 2026-11-10
The Plone/Zope Security Team published five GitHub security advisories and fixed releases on 2026-11-10 for a chained remote code execution flaw. It affects Plone 6.0, 6.1 and 6.2 and older releases back to 4.3. An anonymous visitor can start the chain: missing security declarations on CMFEditions portal_modifier classes let them change a versioning TALES condition, which runs when an editor saves versioned content, so the code executes with that editor's privileges. Overly broad allow_module declarations in CMFPlone, MimetypesRegistry and plone.batching expose imported modules to restricted code, and plone.restapi (rated Medium) lets restricted code bypass permissions through json. The chain was reported by Mokrane ABDELMALEK via Ghent University's VDP. The advisory says the details are now fully public and that a working exploit may not take long to build. It reports no in-the-wild exploitation. Fixed releases: CMFPlone 6.2.3, 6.1.6, 6.0.16; CMFEditions 5.0.2, 4.0.7; MimetypesRegistry 4.0.2, 3.0.2; plone.batching 3.0.3, 2.0.8; plone.restapi 10.2.1, 9.15.8. For Plone 4.3 through 6.2 the alternative is Products.PloneHotfix20261110. Until patched, block URLs containing portal_modifier at the web server and keep the block after upgrading. Restart all Zope instances after updating. Check for changed modifier conditions with @@check-modifier-conditions as Manager, or the hotfix's startup log line 'POSSIBLE ATTACK: MODIFIED VERSIONING CONDITIONS FOUND'. A changed condition persists in the database after the fix, and the advisory says to treat any condition you do not recognise as a compromise.
Fixed: Products.CMFPlone 6.2.3/6.1.6/6.0.16; Products.CMFEditions 5.0.2/4.0.7; Products.MimetypesRegistry 4.0.2/3.0.2; plone.batching 3.0.3/2.0.8; plone.restapi 10.2.1/9.15.8; Products.PloneHotfix20261110 (Plone 4.3–6.2)
Do: Update to the fixed package versions for your Plone series, or install Products.PloneHotfix20261110 and restart all Zope instances; Block URLs containing portal_modifier at the web server as a workaround and keep it after updating; Check for attacks: use @@check-modifier-conditions as Manager, or review hotfix startup logs for 'POSSIBLE ATTACK: MODIFIED VERSIONING CONDITIONS FOUND'; treat unrecognized conditions as compromise; Review custom Python Scripts/templates for imports now blocked, declaring needed names via ModuleSecurityInfo rather than allow_module; Upgrade out-of-support Plone 5.2 and older to Plone 6

### [high] Microsoft Outlook: NTLM hash-leak zero-day exploited in Nov 2026 Patch Tuesday (CVE-2026-124194)
https://helix.ml/threat-watch/i/microsoft-november-2026-patch-tuesday-fixes-record-1-235-flaws-actively-exploited-outlook-ntlm-hash-leak-zero-day-cve-20 · Vulnerabilities · patched · since 2026-11-10 · CVE-2026-112982, CVE-2026-114155, CVE-2026-114171, CVE-2026-116717, CVE-2026-116718, CVE-2026-116719, CVE-2026-116720, CVE-2026-116721, CVE-2026-116722, CVE-2026-116922, CVE-2026-116926, CVE-2026-116927, CVE-2026-116929, CVE-2026-116930, CVE-2026-116931, CVE-2026-116932, CVE-2026-116933, CVE-2026-116934, CVE-2026-116935, CVE-2026-116936, CVE-2026-116937, CVE-2026-116938, CVE-2026-116939, CVE-2026-116940, CVE-2026-116941, CVE-2026-116942, CVE-2026-116943, CVE-2026-116944, CVE-2026-116945, CVE-2026-116946, CVE-2026-118117, CVE-2026-118118, CVE-2026-118119, CVE-2026-118120, CVE-2026-118148, CVE-2026-118288, CVE-2026-118292, CVE-2026-118293, CVE-2026-118294, CVE-2026-118295, CVE-2026-118296, CVE-2026-118297, CVE-2026-118298, CVE-2026-118299, CVE-2026-118300, CVE-2026-118301, CVE-2026-118302, CVE-2026-118700, CVE-2026-118701, CVE-2026-118702, CVE-2026-118703, CVE-2026-118704, CVE-2026-118705, CVE-2026-118706, CVE-2026-118707, CVE-2026-118708, CVE-2026-118709, CVE-2026-118710, CVE-2026-118711, CVE-2026-118712, CVE-2026-118713, CVE-2026-118714, CVE-2026-118715, CVE-2026-118716, CVE-2026-118717, CVE-2026-118718, CVE-2026-118719, CVE-2026-118720, CVE-2026-118740, CVE-2026-118741, CVE-2026-118742, CVE-2026-118746, CVE-2026-118747, CVE-2026-119382, CVE-2026-119824, CVE-2026-119886, CVE-2026-119981, CVE-2026-119990, CVE-2026-120796, CVE-2026-121681, CVE-2026-122162, CVE-2026-122163, CVE-2026-122164, CVE-2026-122165, CVE-2026-122166, CVE-2026-122167, CVE-2026-122168, CVE-2026-122169, CVE-2026-122170, CVE-2026-122171, CVE-2026-122172, CVE-2026-122173, CVE-2026-122174, CVE-2026-122175, CVE-2026-122297, CVE-2026-122474, CVE-2026-122475, CVE-2026-122987, CVE-2026-124194, CVE-2026-85929
Microsoft's November 2026 Patch Tuesday fixes 1,094 vulnerabilities dated to the release day, per Microsoft's own CVRF document and SecurityWeek; BleepingComputer's 1,235 figure (which it says excludes 108 earlier fixes) does not reproduce from the CVRF. The only CVE marked Exploitation Detected is CVE-2026-124194, a spoofing flaw in Outlook: a crafted message file makes Outlook connect to an attacker-controlled network location without the usual external-content warning, which can expose the user's NTLM authentication hash so an attacker can impersonate them. The attack needs network reach and a user to open the file. CISA added CVE-2026-124194 to the Known Exploited Vulnerabilities catalog on 2026-11-10 with a federal due date of 2026-11-24. Microsoft rates it Moderate (CVSS 3.1 6.5, user interaction required). Deploy the November updates, prioritising Outlook, warn users about unexpected message files, and consider blocking outbound NTLM authentication to untrusted destinations.
Do: Deploy the November 2026 Patch Tuesday updates immediately, prioritizing the Outlook CVE-2026-124194 fix on all clients; Apply Windows 11 KB5132061 and KB5131087 cumulative updates; Warn users not to open unexpected message/attachment files and report phishing; Consider blocking outbound SMB/NTLM authentication to untrusted destinations and enforcing NTLM blocking policies; Review the MSRC update guide for other affected components (Azure File Sync, Telephony Service, Remote Desktop Client) and patch accordingly

### [high] Google Chrome: XML use-after-free zero-day exploited in the wild (CVE-2026-125350)
https://helix.ml/threat-watch/i/chrome-xml-use-after-free-zero-day-exploited-in-the-wild-cve-2026-125350 · Vulnerabilities · patched · since 2026-11-09 · CVE-2026-125342, CVE-2026-125343, CVE-2026-125344, CVE-2026-125345, CVE-2026-125346, CVE-2026-125347, CVE-2026-125348, CVE-2026-125349, CVE-2026-125350, CVE-2026-126840, CVE-2026-126841, CVE-2026-126843, CVE-2026-126844, CVE-2026-126845, CVE-2026-126847, CVE-2026-126848, CVE-2026-126849
Google released Chrome Stable 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux on 2026-11-09, with nine security fixes. Google says it is aware that an exploit for CVE-2026-125350, a high-severity use-after-free in the XML component, exists in the wild; it is the only fix in the release that Google marks as exploited, and Google has not described the attacks. The bug was reported to Google by an anonymous researcher on 2026-11-06. The other eight fixes are six High and two Medium issues in WebGL, FileSystem, Compositing, GPU, V8 and XML. CVE-2026-125346, a second XML use-after-free reported on 2026-10-12, is one of them, and Google does not say it is exploited. Press coverage calls this the eighth exploited Chrome zero-day of 2026; the seven earlier ones have their own records. Extended Stable 156.0.8078.96 for Windows and Mac shipped the same day with the same fix, and Chrome for Android 157.0.8103.50 carries the desktop fixes. CISA had not added the CVE to KEV as of catalog 2026.11.09.
Fixed: 157.0.8103.50/.51 (Windows, Mac); 157.0.8103.50 (Linux, Android); 156.0.8078.96 (Extended Stable, Windows, Mac)
Do: Update Chrome to 157.0.8103.50/.51 (Windows, Mac) or 157.0.8103.50 (Linux) and restart the browser; Extended Stable users update to 156.0.8078.96; Android users update via Google Play to 157.0.8103.50; Force browser updates across managed fleets via enterprise update policies and verify versions; Review CISA KEV additions for CVE-2026-125350 and monitor for related exploitation indicators; Ensure Chromium-based browsers (Edge, Brave, etc.) are updated once they merge the underlying fixes

### [high] Apache TomEE: 38 CVEs fixed in 10.3.0/11.0.0-M2 incl. EJB auth bypass on JDK 21+ (CVE-2026-86336)
https://helix.ml/threat-watch/i/apache-tomee-38-cves-fixed-in-10-3-0-11-0-0-m2-incl-ejb-auth-bypass-on-jdk-21-cve-2026-86336 · Vulnerabilities · patched · since 2026-11-10 · CVE-2026-111239, CVE-2026-111240, CVE-2026-111241, CVE-2026-111242, CVE-2026-111243, CVE-2026-111244, CVE-2026-111245, CVE-2026-111246, CVE-2026-111247, CVE-2026-111248, CVE-2026-111249, CVE-2026-111250, CVE-2026-111251, CVE-2026-111256, CVE-2026-111257, CVE-2026-111258, CVE-2026-111259, CVE-2026-111260, CVE-2026-111261, CVE-2026-111262, CVE-2026-111263, CVE-2026-111264, CVE-2026-86336, CVE-2026-86531, CVE-2026-86532, CVE-2026-86811, CVE-2026-87755, CVE-2026-87756, CVE-2026-87758, CVE-2026-97849, CVE-2026-97867, CVE-2026-97870, CVE-2026-97872, CVE-2026-97874, CVE-2026-97880, CVE-2026-97881, CVE-2026-97888, CVE-2026-97890
On 10 November 2026 Apache TomEE published 38 security advisories, consolidated on oss-security on 12 November. TomEE 10.3.0 and 11.0.0-M2 fix 26 of them: five rated Important by the project (EJB method authorization skipped on JDK 21+ (CVE-2026-86336); MicroProfile JWT role checks not enforced for JAX-RS resources (CVE-2026-111244); well-known administrative credentials created at startup in the default configuration with no users defined (CVE-2026-111257); empty-password LDAP bind accepted where the directory allows unauthenticated binds (CVE-2026-111261); and an EJB JAX-WS endpoint auth bypass via alternative HTTP methods (CVE-2026-111264)). The other 21 fixed items are rated Moderate or Low. Twelve more affect optional modules (embedded OpenEJB HTTP server, Hessian remoting, SSH admin shell) that are removed in both releases and have no fixed version. Several fixes change default behaviour, so read the migration guides. No exploitation is reported.
Fixed: 10.3.0; 11.0.0-M2
Do: Upgrade to Apache TomEE 10.3.0 or 11.0.0-M2 and read the 10.3.0 and 11.0.0-M2 migration guides, since several fixes change default behaviour; If upgrading is not possible, stop using or block network access to the embedded OpenEJB HTTP server, Hessian remoting and the SSH administration shell from untrusted clients; these modules have no fix; On JDK 21+, review EJB method authorization in deployments (CVE-2026-86336) and confirm checks are enforced after upgrade; Check for default administrative users on startup, LDAP identity stores that accept unauthenticated binds, and EJB web service endpoints with authentication configured (CVE-2026-111257, CVE-2026-111261, CVE-2026-111264)

### [critical] Ivanti EPM SQLi RCE (CVE-2026-121653) and CSA auth bypass (CVE-2026-121683) in a 19-flaw Patch Tuesday
https://helix.ml/threat-watch/i/citrix-ivanti-patch-tuesday-19-flaws-incl-critical-csa-auth-bypass-cve-2026-121683-and-epm-sqli-rce-cve-2026-121653 · Vulnerabilities · patched · since 2026-11-10 · CVE-2026-102705, CVE-2026-105425, CVE-2026-121653, CVE-2026-121683
On Tuesday 2026-11-10 Ivanti and Citrix published patches for 19 vulnerabilities. Ivanti fixed 13 flaws across five products. The two criticals are CVE-2026-121653 (CVSS 9.8 per NVD), an unauthenticated SQL injection in the Endpoint Manager Core that leads to remote code execution, fixed in EPM 2024 SU8; and CVE-2026-121683 (CVSS 9.4 per NVD), a missing-authentication flaw in Cloud Services Application 5.0.8 that lets an unauthenticated remote attacker add and delete trusted EPM Core certificate entries, fixed in CSA 5.0.8.1. SecurityWeek reports that Dual NIC deployments cannot be exploited externally. Ivanti also fixed CVE-2026-105425 in Sentry (high, CVSS 7.2 per NVD), an OS command injection that NVD says needs administrator privileges; the same CVE is fixed in EPMM, which also received five medium issues. Citrix fixed six XenServer flaws, including a high-severity CVE-2026-102705 that SecurityWeek says allows Pool Secret inference and host compromise; that CVE does not appear in NVD or in Citrix's bulletin CTX697170, so it is unverified. XenServer also received updates for AMD CPU issues. Neither vendor reports exploitation. None of these CVE IDs is in CISA KEV at catalog 2026.11.10. Patch CSA to 5.0.8.1 and EPM to 2024 SU8 first, then Sentry and EPMM to the versions listed below.
Fixed: CSA 5.0.8.1; EPM 2024 SU8; Sentry 11.0.0, 10.8.3 and 10.7.4 (CVE-2026-105425); EPMM 12.11.0.0, 12.10.0.1 and 12.9.0.3 (CVE-2026-105425)
Do: Patch Ivanti CSA to 5.0.8.1 immediately; verify Dual NIC exposure as a temporary mitigation; Update Ivanti EPM to 2024 SU8 and restrict database access pending patch; Update Sentry to 11.0.0, 10.8.3 or 10.7.4, and EPMM to 12.11.0.0, 12.10.0.1 or 12.9.0.3 (CVE-2026-105425; NVD says admin privileges are needed); Apply Citrix XenServer security updates, including AMD CPU mitigations; Review certificate trust entries in EPM Core for tampering and audit for signs of exploitation

### [critical] Fortinet Patch Tuesday: 89 advisories, ~17 critical, incl. FortiClient Fortinet2Shell code execution via CORS
https://helix.ml/threat-watch/i/fortinet2shell-fortinet-patch-tuesday-fortinet-89-advisories-fix-100-flaws-incl-critical-rce-and-auth-bypass-across-fort · Vulnerabilities · patched · since 2026-11-10
On Tuesday 2026-11-10 Fortinet published 89 PSIRT advisories fixing nearly 100 flaws, about 17 of them critical and roughly 80 high. FortiMail has the largest share of the criticals, followed by FortiAuthenticator, FortiOS, FortiManager and FortiAnalyzer, with critical fixes also in FortiSASE and FortiClient. The criticals include code execution, authentication bypass, account takeover, SSRF, IBE webmail session compromise and super-admin command execution. The headline FortiClient bug, which researcher Kevin Joensen of Baldur Security named Fortinet2Shell, is a CORS misconfiguration that lets an attacker's web page reach a local service and run code on a victim who visits it, but only when FortiPAM is enabled. No CVE or Fortinet advisory for that specific bug was retrieved; the detail rests on SecurityWeek's report of the researcher's statement. Fortinet's own statements in the batch say no exploitation: the FortiGuard pages for FG-IR-26-267 and FG-IR-26-207 both read Known Exploited: No, SecurityWeek says Fortinet makes no mention of exploitation, and no CVE from this batch is in CISA KEV at catalog 2026.11.10. Fixes are in the PSIRT advisories. Patch the FortiMail, FortiAuthenticator and FortiOS criticals first, patch FortiClient and check whether FortiPAM is enabled, and restrict management interfaces to trusted networks.
Do: Immediately review Fortinet's PSIRT advisories and patch FortiMail, FortiAuthenticator, FortiOS, FortiManager and FortiAnalyzer critical issues first; Patch FortiClient and review whether FortiPAM is enabled; treat the Fortinet2Shell flaw as high priority; Restrict access to Fortinet management interfaces and local services from untrusted web content; Monitor Fortinet systems for signs of exploitation before and after patching; Prioritise upgrades quickly given AI is shortening disclosure-to-exploitation windows

### [critical] Fortinet patch batch: FortiOS OSPF auth bypass, FortiAuthenticator hard-coded password & auth flaws
https://helix.ml/threat-watch/i/fortinet-patch-batch-fortios-ospf-auth-bypass-fortiauthenticator-hard-coded-password-auth-flaws · Vulnerabilities · patched · since 2026-11-10 · CVE-2026-126214, CVE-2026-126215, CVE-2026-126216, CVE-2026-126217, CVE-2026-126244, CVE-2026-126251, CVE-2026-126253, CVE-2026-126257
Fortinet's PSIRT published five advisories on 2026-11-10 for fixes that the earlier Fortinet record (2026-10-26) tracks as shipped in its 2026-10-22 hardening releases. The highest-rated is FG-IR-26-267 (CVE-2026-126253, CVSS 9.3, adjacent-network attacker): an authentication bypass in the FortiOS and FortiSASE OSPF daemon that lets an unauthenticated attacker broadcast crafted LSAs. FG-IR-26-271 (CVE-2026-126257, CVSS 9.0, CWE-259) is a hard-coded password in FortiAuthenticator. FG-IR-26-265 (CVE-2026-126251, CVSS 9.1, CWE-863) is an incorrect-authorization flaw in FortiAuthenticator that the advisory says may allow authentication bypass. FG-IR-26-258 (CVE-2026-126244, CVSS 7.5, CWE-770) is an unbounded-resource denial-of-service in FortiAuthenticator; its title says fastapi, but the body and product table name only FortiAuthenticator. FG-IR-26-234 (CVE-2026-126214 to CVE-2026-126217, CVSS 8.7) covers FortiAnalyzer, FortiManager and FortiSASE-Sovereign. Each advisory names fixed builds per branch. Fortinet reports no exploitation, none of the eight CVEs is in CISA KEV, and no virtual patch is offered. Three advisories credit Claude Mythos with the discovery.
Fixed: FortiOS 8.0.2, 7.6.8, 7.4.13, 7.2.14 or above (FG-IR-26-267); FortiSASE 26.3.2 for 26.3.1 and 26.3.1_a; older FortiSASE branches: migrate to a fixed release (no version named); FortiAuthenticator 8.0.4 or above, 6.6.11 or above (FG-IR-26-271, FG-IR-26-265, FG-IR-26-258); FortiAnalyzer and FortiManager 8.0.2, 7.6.8, 7.4.12, 7.2.13 or above (FG-IR-26-234); FortiSASE-Sovereign: migrate to a fixed release (no version named)
Do: Upgrade FortiOS to 8.0.2, 7.6.8, 7.4.13 or 7.2.14 or later (FG-IR-26-267), prioritising internet-reachable and OSPF-enabled FortiGate devices; Upgrade FortiSASE 26.3.1 and 26.3.1_a to 26.3.2; migrate older FortiSASE branches to a fixed release; Upgrade FortiAuthenticator to 8.0.4 or 6.6.11 or later (FG-IR-26-271, FG-IR-26-265, FG-IR-26-258); Upgrade FortiAnalyzer and FortiManager to 8.0.2, 7.6.8, 7.4.12 or 7.2.13 or later (FG-IR-26-234); migrate FortiSASE-Sovereign to a fixed release; Restrict OSPF and FortiAuthenticator management interfaces to trusted networks until patched; Review FortiAuthenticator logs for signs of authentication anomalies

### [critical] FortiMail critical flaws: unauth command injection, SQL injection, IBE session hijack; FortiOS sshd auth bypass
https://helix.ml/threat-watch/i/fortimail-critical-flaws-unauth-command-injection-sql-injection-ibe-session-hijack-fortios-sshd-auth-bypass · Vulnerabilities · unknown · since 2026-11-10 · CVE-2026-126148, CVE-2026-126155
On 2026-11-10 Fortinet published four PSIRT advisories. FortiMail is affected by three unauthenticated critical flaws: command injection via crafted HA join-request packets (CVE-2026-126148, CVSS 9.8, allows arbitrary code execution), SQL injection via crafted requests (CVSS 9.4), and incorrect authorization in IBE webmail (CVE-2026-126155, CVSS 9.1, lets an attacker obtain an authenticated session as any IBE recipient and read or send their encrypted mail). FortiMail 7.2.0 through 8.0.1 are affected. Separately, a path traversal in the ssh daemon of FortiOS, FortiSASE, FortiProxy and FortiPAM (CVSS 7.4) allows authentication bypass via crafted credentials. Two flaws were found internally with AI model assistance. No in-the-wild exploitation is reported; fixes are available — upgrade promptly.
Do: Upgrade FortiMail to a fixed release immediately, prioritising internet-facing IBE webmail and HA clusters; Upgrade FortiOS, FortiProxy, FortiPAM and FortiSASE sshd-affected builds to patched versions; Restrict management and HA interfaces to trusted networks until patched; Review FortiMail IBE mailboxes and logs for signs of unauthorised session access or sent mail; Monitor Fortinet PSIRT for updated fixed-version details, as advisories list affected versions but not fixed builds in these feeds

### [critical] GitLab CE/EE: Git merge heap overflow may allow command execution in Gitaly (CVE-2026-105437)
https://helix.ml/threat-watch/i/gitlab-critical-patch-release-19-5-4-19-4-6-19-3-8-heap-overflow-in-bundled-git-enables-rce-in-gitaly-cve-2026-105437 · Vulnerabilities · patched · since 2026-11-10 · CVE-2026-105437
GitLab's 2026-11-10 critical patch releases (19.5.4, 19.4.6, 19.3.8) update the Git binary bundled with GitLab CE/EE to fix CVE-2026-105437, a heap overflow in Git's xdiff three-way merge code. The merged-output size is summed in a 32-bit int, and the conflict-marker-size attribute, which can be set from a committed .gitattributes file, accepts any positive integer and multiplies the marker writes. A small file with a huge marker size and many conflicts can wrap that total, so Git writes past a buffer that is too small. Upstream Git describes the result as a crash with possible heap corruption. GitLab says the out-of-bounds writes could execute arbitrary commands inside the Gitaly environment; upstream says a forge is exposed when it reads attributes from repository trees (attr.tree or --attr-source) and any user who can push and open a merge request can trigger the overflow. On clients, any merge, rebase, cherry-pick or merge-tree in an untrusted repository that carries the attribute can trigger it. Self-managed CE/EE from 16.2 before 19.3.8, 19.4 before 19.4.6 and 19.5 before 19.5.4 are affected; GitLab.com and GitLab Dedicated are already patched. Official packages and images ship the patched Git; self-compiled installs must rebuild Gitaly's Git and the Git at git.bin_path, or use Git 2.56.1 or a distribution patch. Upstream fixed it in Git 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1 and 2.56.1, and the vulnerable code is present in every release checked from v1.7.0 through v2.56.0. No exploitation and no public proof of concept were found, and CISA KEV has no entry. Reported via HackerOne by taise.
Fixed: 19.5.4; 19.4.6; 19.3.8; Upstream Git 2.50.2; Upstream Git 2.51.3; Upstream Git 2.52.1; Upstream Git 2.53.1; Upstream Git 2.54.1; Upstream Git 2.55.1; Upstream Git 2.56.1
Do: Upgrade self-managed GitLab CE/EE to 19.5.4, 19.4.6 or 19.3.8 immediately; For self-compiled installations, rebuild Git binaries in Gitaly and the Git referenced by git.bin_path, or upgrade Git to 2.56.1 or a distribution-patched version; Verify no other bundled/embedded Git copies remain unpatched; Review Gitaly logs for signs of anomalous command execution; Until patched, servers and forges can add conflict-marker-size=7 to each repository's info/attributes (it overrides any in-tree .gitattributes), or turn off server-side mergeability checks for untrusted repositories (upstream workaround); Before merging, rebasing or cherry-picking in an untrusted repository, check its .gitattributes for a very large conflict-marker-size, or add the same override to .git/info/attributes

### [critical] Adobe November 2026 Patch Tuesday: 110 vulnerabilities fixed across 9 products, incl. CVSS 10 Connect flaws
https://helix.ml/threat-watch/i/adobe-november-2026-patch-tuesday-110-vulnerabilities-fixed-across-9-products-incl-cvss-10-connect-flaws · Vulnerabilities · patched · since 2026-11-10 · CVE-2026-121349, CVE-2026-121350, CVE-2026-121351, CVE-2026-121352, CVE-2026-121353, CVE-2026-121354, CVE-2026-121355, CVE-2026-121356, CVE-2026-121887, CVE-2026-121889, CVE-2026-121890, CVE-2026-121892, CVE-2026-121894, CVE-2026-121896, CVE-2026-121898, CVE-2026-121900, CVE-2026-121902, CVE-2026-121904, CVE-2026-121906, CVE-2026-121908, CVE-2026-121910, CVE-2026-121912, CVE-2026-121913, CVE-2026-122102
Adobe's November 2026 Patch Tuesday fixes roughly 110 vulnerabilities across nine products, per SecurityWeek. The Adobe Connect bulletin APSB26-191 (published 2026-11-10, priority 2) covers 24 CVEs in Adobe Connect 12.12 and earlier on Windows. It rates five of them CVSS 10.0 (privilege escalation via SSRF, path traversal, incorrect authorization and CRLF injection). Twelve more are Critical between 9.1 and 9.9, covering arbitrary code execution, SQL injection, XXE, path traversal and stored XSS. The remaining seven are High or Medium, including an arbitrary file system read. SecurityWeek reports six CVSS 10 Connect flaws; the bulletin we could read shows five. Adobe states it is not aware of any exploits in the wild for any issue in this update. The other products in the release (AEM, Premiere Pro, Photoshop, After Effects, Audition, Dimension, Media Encoder and the Content Credentials SDK) are covered by bulletins not verified here. Update Adobe Connect first, then the desktop and SDK products as change control allows.
Fixed: Adobe Connect 12.12.a; Adobe Connect 12.11.i; Adobe Connect 12.10.f; Adobe Connect 12.9.a; Adobe Connect 12.8.a (Windows; the bulletin does not map fixed versions to individual CVEs)
Do: Prioritise updating Adobe Connect and AEM (priority 2, critical CVSS 10 flaws) as soon as change control allows; Update Premiere, Photoshop, After Effects, Audition, Dimension, and Media Encoder to the November 2026 releases; Update the Content Credentials Rust SDK / C2PA Tool if used in builds; Review internet-exposed Connect and AEM instances for signs of SSRF, path traversal, or injection attempts; Track Adobe advisories for any later exploitation reports and adjust patch priority accordingly

### [critical] SAP NetWeaver / Web Dispatcher: four CVSS 10.0 pre-auth flaws patched, incl. SAML bypass (CVE-2026-120017)
https://helix.ml/threat-watch/i/sap-netweaver-web-dispatcher-four-cvss-10-0-pre-auth-flaws-fixed-on-patch-day-incl-rce-and-saml-auth-bypass-cve-2026-769 · Vulnerabilities · patched · since 2026-11-10 · CVE-2026-120017, CVE-2026-76964, CVE-2026-89103, CVE-2026-89126
On SAP's November 2026 Security Patch Day (10 Nov), SAP published four security notes, each rated CVSS 10.0 by SAP as CNA, and each flaw is reachable without authentication or user interaction. CVE-2026-76964 (ICM, Note 3778530) and CVE-2026-89126 (Web Dispatcher, Note 3778556) are memory-corruption bugs triggered by insufficiently validated network input, which SAP says can allow arbitrary code execution. CVE-2026-89103 (SAP Gateway, Note 3798345) is a default access control list that classifies an external attacker as an internal application server. CVE-2026-120017 (SAML2 service provider in AS ABAP, Note 3849308) does not sufficiently verify incoming authentication assertions under certain configurations, which lets an attacker impersonate arbitrary users, including privileged accounts. SAP's page lists the affected releases per note, including the HANA-related Web Dispatcher components HDB 2.00, XS_ADVANCED_RUNTIME 1.00 and SAP_EXTENDED_APP_SERVICES 1. Neither SAP's page nor NVD reports exploitation or a public proof of concept, and none of the four CVEs is in the CISA KEV feed checked on 2026-11-09. Patch each note for the components you run, and review SAML2 logons and Gateway access control, which are the paths these flaws describe.
Fixed: SAP Notes 3778530 (ICM), 3778556 (Web Dispatcher), 3798345 (Gateway), 3849308 (SAML2 service provider); fixed release levels per note not verified
Do: Patch SAP Note 3849308 (CVE-2026-120017) on AS ABAP systems that use SAML2 browser logon, and review trusted identity providers and SAML2 logon audit logs for privileged users logging on from unexpected sources; Patch SAP Note 3778530 (ICM, CVE-2026-76964) and SAP Note 3778556 (Web Dispatcher, CVE-2026-89126) together, and find every Web Dispatcher instance, including the HANA-related components listed on SAP's page; Patch SAP Note 3798345 (Gateway, CVE-2026-89103) and review Gateway access control lists, since the flaw is in default ACL handling; Check each system's release level against the affected lists on SAP's page, and confirm the fixed release level in each note, which this record did not verify

### [critical] IBM Aspera Faspex 5: authorization bypass gives full admin rights, exploited in the wild (CVE-2026-123218)
https://helix.ml/threat-watch/i/ibm-aspera-faspex-cve-2026-123218 · Vulnerabilities · patched · since 2026-11-07 · CVE-2026-116779, CVE-2026-123218
IBM Aspera Faspex 5.0.0 through 5.0.19 has an incorrect-authorization flaw (CWE-863): a user can craft a specific message that bypasses authorization and gains full administrator rights. IBM's bulletin calls the attacker an authenticated or authorized user, but its CVSS 3.1 vector (score 9.8) sets privileges required to none, so the precondition is unresolved. CISA added CVE-2026-123218 to the Known Exploited Vulnerabilities catalog on 2026-11-09, with a federal due date of 2026-11-12. That listing is the only exploitation evidence found so far; no source we could open names an actor or campaign. IBM fixed the flaw in 5.0.19 PL1 (Linux; faspex-core container image 5.0.19, fix pack 1) and lists no workaround, so upgrading is the only remedy IBM gives.
Fixed: 5.0.19 PL1 (Linux; faspex-core container image 5.0.19, fix pack 1)
Do: Upgrade IBM Aspera Faspex 5.0.x to 5.0.19 PL1. For container deployments, confirm the faspex-core image is 5.0.19 (1ce4b13, Fix Pack 1). IBM lists no workaround.; Review Faspex user accounts for administrator rights that were not granted on purpose. IBM's bulletin gives no detection guidance, so this check is our recommendation, not IBM's.; Federal agencies: remediate by 2026-11-12 (CISA KEV due date) and follow CISA's BOD 26-04 guidance, which says to discontinue use of the product where mitigations are unavailable.

### [critical] CISA KEV additions: GPUStack, FreeSWITCH, OpenSSH, IBM Aspera Faspex flaws exploited in the wild
https://helix.ml/threat-watch/i/cisa-kev-additions-gpustack-freeswitch-openssh-ibm-aspera-faspex-flaws-exploited-in-the-wild · Vulnerabilities · patched · since 2026-11-09 · CVE-2026-102895, CVE-2026-116779, CVE-2026-123158, CVE-2026-123218
CISA added four flaws to its Known Exploited Vulnerabilities catalog with a dateAdded of 2026-11-09 and a federal due date of 2026-11-12. CVE-2026-102895 (GPUStack, CVSS 9.8): before 2.2.0, a request that appeared to come from loopback was treated as the built-in administrator when force_auth_localhost was at its default of false, so a remote client could reach admin functions unauthenticated, including creating persistent admin API keys, reading worker and cloud-provider secrets, and running code through the inference-backend YAML endpoint; CISA and the GitHub advisory say exploitation was seen against a 2.1.1 deployment. CVE-2026-116779 (FreeSWITCH, CVSS 9.8): before 1.11.3, an inbound SIP MESSAGE could select an internal chat protocol and run FreeSWITCH API and OS commands; it needs an authenticated profile account, and the project's advisory says this path has been exploited in the wild. CVE-2026-123158 (OpenSSH, CVSS 8.1): before 10.6p2 on Linux built with musl libc and without PAM, sshd accepts a long password (about 256 to 1024 characters) for some account configurations; Alpine describes the condition as an account with a '*' password field plus another account with a $5$ or $6$ hash. CISA lists it as exploited, but I found no product-specific exploitation report. CVE-2026-123218 (IBM Aspera Faspex 5.0.0 to 5.0.19, CVSS 9.8): an authorized user can craft a message that bypasses authorization and gains full administrator rights; IBM fixed it in 5.0.19 PL1. CISA's KEV criteria require reliable evidence of active exploitation, so its listing counts as exploitation for this flaw too, although IBM's bulletin and the press coverage give no exploitation detail. Fixes exist for all four.
Fixed: GPUStack 2.2.0; FreeSWITCH 1.11.3; OpenSSH 10.6p2; IBM Aspera Faspex 5.0.19 PL1
Do: Patch GPUStack to 2.2.0 or later; check for unauthorized admin API keys, changed users or models, edited configuration, and any reads of worker or cloud-provider secrets; Upgrade FreeSWITCH to 1.11.3 or later; if a SIP profile does not need chat, set enable-chat=false (the advisory says chat is on by default in the stock internal and external profiles); rotate credentials that the FreeSWITCH configuration could expose; Upgrade OpenSSH to 10.6p2 or later on Linux systems that use musl without PAM (Alpine is the documented example); until then set PasswordAuthentication no and restart sshd, because upgrading the package does not restart a running daemon; Upgrade IBM Aspera Faspex to 5.0.19 PL1 and confirm the faspex-core image reports 5.0.19 with fix pack 1, as IBM's bulletin specifies; Treat 2026-11-12 as the KEV due date for federal agencies; the KEV entries cite BOD 26-04, which carries forward the KEV criteria from BOD 22-01

### [high] OpenSSH on musl (Alpine): password-auth bypass for `*`-password accounts via 257–1024-byte password (CVE-2026-123158)
https://helix.ml/threat-watch/i/openssh-on-musl-alpine-password-auth-bypass-for-password-accounts-cve-2026-123158 · Vulnerabilities · patched · since 2026-11-05 · CVE-2026-123158
When sshd is built without PAM (Alpine's default `openssh-server`, or `openssh-server-pam` with `UsePAM no`), it checks a password by running `crypt()` on the attempt and comparing the result with the stored field. An account whose field is too short to hold a salt, such as `*` (no password), gets the salt of another account with a `$5$`/`$6$` hash. sshd has done this since a 2016 timing-attack mitigation (`pick_salt()`). musl's SHA-crypt rejects keys over 256 bytes and returns the literal string `*` as its error value. So a password of roughly 257–1024 bytes "hashes" to `*`, matches the stored field, and logs the attacker in on the first try. Affected hosts need: `PasswordAuthentication yes`, any account with a `*` password field, and at least one local account with a real `$5$`/`$6$` hash. Accounts with `*` include `root` (shipped as `root:*` since about Alpine 3.16, but blocked by the default `PermitRootLogin prohibit-password`), key-only users, directory users from nslcd, winbind or sssd, and the `alpine` user with passwordless `doas` in tiny-cloud images 3.18.11–3.24.3. Every Alpine release from 3.16 to 3.24 and edge is affected. OpenSSH's maintainers say the root cause is outside sshd and shipped a workaround in 10.6p2 (2026-11-05); Alpine backported a patch to every branch back to 3.16 and cut point releases 3.21.10, 3.22.8, 3.23.8 and 3.24.4. The reporter is Özgün Kültekin of Wakefield, who calls the bug "sshole". Public lab/PoC repositories appeared within hours. There are no reports of in-the-wild exploitation so far. Hosts not affected: locked `!` accounts, `UsePAM yes`, and glibc-based distros.
Fixed: OpenSSH portable 10.6p2; Alpine openssh: edge 10.6_p2-r0 · 3.24 10.3_p1-r2 · 3.23 10.2_p1-r1 · 3.22 10.0_p1-r11 · 3.21 9.9_p2-r1 · 3.20 9.7_p1-r6 · 3.19 9.6_p1-r3 · 3.18 9.3_p2-r4 · 3.17 9.1_p1-r7 · 3.16 9.0_p1-r6; Alpine point releases 3.21.10, 3.22.8, 3.23.8, 3.24.4 (and images built from them)
Do: Upgrade and restart sshd: `apk upgrade -U -a && rc-service sshd restart`. Upgrading the package does NOT restart the running daemon.; Confirm the fixed openssh package for your branch: edge 10.6_p2-r0, 3.24 10.3_p1-r2, 3.23 10.2_p1-r1, 3.22 10.0_p1-r11, 3.21 9.9_p2-r1, 3.20 9.7_p1-r6, 3.19 9.6_p1-r3, 3.18 9.3_p2-r4, 3.17 9.1_p1-r7, 3.16 9.0_p1-r6. Non-Alpine musl/no-PAM builds: upgrade to OpenSSH 10.6p2.; If you cannot patch now, set `PasswordAuthentication no`, run `sshd -t`, restart sshd, and check that `sshd -T | grep -i passwordauthentication` prints `no`.; Hunt for prior use: search `/var/log/messages` (or your syslog) for `Accepted password for` on accounts that have no password (root, alpine, key-only and directory users). Review doas/sudo use, new users, authorized_keys and recently changed files. Treat a host as compromised if you cannot rule a login out.; Rebuild Alpine-based VM and cloud images (tiny-cloud qcow2/VHD/AMI 3.18.11–3.24.3 ship an `alpine` user with `*` and passwordless doas) and any container images that run sshd with password authentication.; Inventory other musl/no-PAM sshd builds (OpenWrt/Buildroot/Yocto images that ship OpenSSH rather than Dropbear, postmarketOS) and lock no-password accounts with `!` instead of `*` where possible.

### [high] SonicWall SonicOS SSLVPN Use of Single-factor Authentication Vulnerability (CVE-2026-19868)
https://helix.ml/threat-watch/i/sonicwall-sonicos-sslvpn-cve-2026-19868 · Vulnerabilities · patched · since 2026-11-06 · CVE-2026-19868
SonicWall's PSIRT advisory SNWLID-2026-0014 (published 2026-11-06) bundles seven CVEs; this record covers CVE-2026-19868. A user holding valid credentials for an alternate authentication method can bypass SAML authentication controls on SonicOS SSLVPN, and may also bypass SAML-enforced MFA. The advisory says the issue only affects SSLVPN when SAML is enabled for SSLVPN logins. The PSIRT says it investigated a report of potential exploitation, and CISA added the CVE to the KEV catalog on 2026-11-06 with a federal remediation date of 2026-11-20. Affected builds are SonicOS Gen7 7.3.3-7015 and older and Gen8 8.2.2-8015 and older; fixed builds are Gen7 7.3.4-7013 and higher and Gen8 8.2.3-8015 and higher. The PSIRT lists no workaround, so upgrading is the vendor fix.
Fixed: SonicOS Gen7 7.3.4-7013 and higher; SonicOS Gen8 8.2.3-8015 and higher
Do: Upgrade to SonicOS Gen7 7.3.4-7013 or higher, or Gen8 8.2.3-8015 or higher (PSIRT SNWLID-2026-0014); the PSIRT lists no workaround; Check whether SSLVPN logins use SAML; the PSIRT says this CVE only applies when SAML is enabled for SSLVPN logins; Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA's "Forensics Triage Requirements" (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.; US federal agencies must remediate by Nov 20, 2026 (BOD 22-01); treat that as the outer limit.

### [critical] UnrealIRCd label tag injection: any user can run commands with server/IRCOp authority (CVE-2026-114713)
https://helix.ml/threat-watch/i/unrealircd-label-tag-injection-any-user-can-run-commands-with-server-ircop-authority-cve-2026-114713 · Vulnerabilities · patched · since 2026-11-07 · CVE-2026-114713
On 7 November 2026 UnrealIRCd shipped 6.2.7.1 and a hot-patch bundle (bundle-20261107) that fix nine security issues. The maintainer says they were found in an internal audit done with the help of AI. The critical one, CVE-2026-114713, is an escaping failure in the labeled-response module's handling of the IRCv3 "label" message tag. Any user can inject newlines into server-to-server traffic, and the receiving servers execute the injected IRC commands with server authority, such as KILL or GLINE. NVD records the affected range as UnrealIRCd 6.0.0 before 6.2.7.1 and says the flaw needs a network with two or more linked servers. The other eight issues cover IP-address leaks that let a user decloak another user, crashes, a hang, a connection-counting error that can refuse every new connection until restart, a TLS renegotiation flood, and a Services ban limit. NVD lists no CVE for those eight. The vendor advisory reports no exploitation. This research found no CISA KEV entry, no public proof of concept, and no EPSS score yet. Apply the SPAMFILTER workaround first, which only protects if every server runs 6.0.4 or newer. Then hot-patch with bundle-20261107 or upgrade to 6.2.7.1 and restart. UnrealIRCd 5 (EOL) is also affected; the vendor's mitigation there is a blacklist-module line and a restart.
Fixed: 6.2.7.1; hot-patch bundle-20261107
Do: Before anything else, run as an IRCOp on the network: SPAMFILTER add -regex T block - Invalid_label ^label=(?![^\r\n;\x20]*\z) . This protects all linked servers only if every server runs 6.0.4 or newer. It does not fix the other eight issues.; Hot-patch each *NIX server (UnrealIRCd 6.0.0 to 6.2.7, no restart): ./unrealircd hot-patch bundle-20261107 . The output should end with "Patch installed and server rehashed correctly. All should be good now!"; Verify: ./unrealircd module-status | grep labeled-response should show 5.0-hot-patch-bundle-20261107, or 6.2.7.1 if the server was upgraded. On IRC, MODULE -all as an IRCOp, then search for labeled-response. If the hot-patch fails, use the FAQ section "Hot-patching failed" or upgrade.; Alternatively upgrade to 6.2.7.1 (./unrealircd upgrade on *NIX, or download the release on Windows) and restart the server. Windows servers must upgrade.; UnrealIRCd 5 (EOL, affected): add blacklist-module "labeled-response"; to the config on every server and restart (not rehash). The vendor advises moving to UnrealIRCd 6.; UnrealIRCd 3.2.x and 4 (EOL): the vendor has not checked them and says it is likely that several fixed bugs go back to 3.2.x. Treat them as unassessed and move to UnrealIRCd 6.

### [high] Claude Code 'don't ask again' approvals leak secrets into public GitHub repos (settings.local.json)
https://helix.ml/threat-watch/i/claude-code-secrets-leak-ai-coding-agent-commits-credentials-to-public-github-repos-claude-settings-local-json · Vulnerabilities · unpatched · since 2026-11-05
Apiiro, a commercial application-security vendor, searched public GitHub for copies of .claude/settings.local.json and found 104,185 copies in 103,617 repositories. 1,122 of them (about 1.1%) held at least one real secret: 1,379 distinct secrets, among them database passwords, Supabase service-role keys, SSH logins and cloud and SaaS tokens, belonging to 63 organisations. When a user chooses "Yes, and don't ask again" on a permission prompt, Claude Code saves the approved command as typed into that file as an allow rule, so a password typed inline into a command lands on disk in plain text. Claude Code adds the file to the developer's global git excludes, not to the project .gitignore, so the protection does not follow a clone or a second machine; in 539 of the 1,105 repositories Apiiro traced, a commit co-authored by Claude changed the file. Anthropic's documentation describes this storage. A bug report filed on Anthropic's tracker in August 2025 (anthropics/claude-code#5544) was closed as not planned in January 2026. No fix has shipped and no response from Anthropic was reported. Apiiro did not test whether the secrets were still valid or whether anyone used them. Apiiro's wider total of 2,539 secrets across 1,994 repositories adds older git versions, the shared settings.json and saved agent transcripts; it is not the headline count.
Do: Rotate every credential that appears in a committed .claude/settings.local.json or in a command approved with "don't ask again", prioritising cloud keys, database passwords and production tokens; Find committed .claude/settings.local.json files in public and private repositories and in their git history; untrack them and purge the history; Add .claude/settings.local.json to each project's .gitignore (the global excludes entry does not protect clones) and enforce pre-commit secret scanning; Do not approve a permission prompt whose command contains an inline credential; pass secrets through environment variables or a secret store instead; Search GitHub for your organisation's copies of the file and check provider logs for use of any key found to be live

### [critical] Rails 8.0.5.2 / 8.1.4.1 security releases fix 21 flaws incl. Active Storage file write and conditional RCE
https://helix.ml/threat-watch/i/rails-8-0-5-2-8-1-4-1-security-releases-fix-21-flaws-incl-active-storage-rce · Vulnerabilities · patched · since 2026-11-04
Rails 8.0.5.2 and 8.1.4.1 were released on 2026-11-04 (gems published 02:34 and 02:47 UTC) as security updates for 21 GitHub advisories, none of which has a CVE. The Critical advisory, GHSA-f3w6-w445-fwh9, lets an unauthenticated attacker who can submit an upload write arbitrary files through ImageMagick processing and, where attachments use the Disk service, read files the application can read; the advisory says the exposed secrets may then lead to remote code execution or lateral movement. The only advisory titled as remote code execution is High GHSA-v924-7rp8-4mxh: an attacker-chosen filename extension decides which FFmpeg or ImageMagick decoder runs, and the advisory states RCE only for an FFmpeg built with AviSynth and the AviSynthPlus runtime, which upstream and common Linux and Homebrew builds do not enable; it also says other extension-selected decoders may be reachable. The remaining items are a High Strong Parameters bypass, a High 8.1-only IP spoofing flaw in RemoteIp, a High DoS in safe_constantize, Medium XSS in several Action View helpers and the MessagePack serializer, Medium and Low DoS, session, cache-poisoning and file-size-limit issues, and a Low Mailgun signature replay. Fixed in 8.0.5.2 and 8.1.4.1; affected ranges are below 8.0.5.2 and from 8.1 to below 8.1.4.1. Security support for the 8.0 series ends 2026-11-07.
Fixed: 8.0.5.2; 8.1.4.1
Do: Upgrade all Rails apps to 8.1.4.1 or 8.0.5.2 now, prioritising apps that accept uploads and analyse or preview attachments, since GHSA-f3w6 needs no privileges and no variant or preview call.; If the app uses the Disk service, or runs an AviSynth-enabled FFmpeg with uploads (GHSA-v924), treat secret_key_base, the master key, config/credentials.yml.enc contents, storage and database credentials and third-party tokens as exposed and rotate them after upgrading; do not keep the old value as a fallback.; If an upgrade cannot happen immediately: apply the advisory patch commits (GHSA-f3w6: 8.1 468aa9a, 8.0 ea8c401; GHSA-v924: 8.1 72136ff, 8.0 8106938), deny the MSL, Ghostscript and gs-delegate coders in the host ImageMagick policy, and remove VideoPreviewer, VideoAnalyzer and AudioAnalyzer from the Active Storage config.; Audit apps on Rails below 8.0 and plan the move to the 8.0 series before its security support ends on 2026-11-07.; Review session settings against GHSA-gmj8 (SameSite on session-store cookies) and GHSA-2586 (CacheStore restoring destroyed sessions), and Active Storage proxy and GCS direct-upload settings against GHSA-x6mj, GHSA-3w93 and GHSA-hfr4.; Verify gem SHA-256 hashes against the list in the oss-sec announcement when updating.

### [critical] Apache Allura OAuth1 rebinding vulnerability (CVE-2026-118196)
https://helix.ml/threat-watch/i/apache-allura-oauth1-rebinding-vulnerability-cve-2026-118196 · Vulnerabilities · patched · since 2026-11-06 · CVE-2026-118196
Apache Allura, the open-source software forge, has an OAuth 1 rebinding flaw tracked as CVE-2026-118196, which the Apache project rates critical. Every release through 1.22.0 is affected, and Apache says 1.22.1, released 2026-11-06, fixes it. The release notes, the oss-security post and the project's changelog give no mechanism, CVSS score, attacker preconditions or exploit detail, and none of the sources we checked reports exploitation or lists the CVE in CISA KEV. The CVE record itself was not yet visible in the CVE Services API or NVD when checked. The issue was reported by hataehoon. Upgrading is the only fix named; 1.22.1 also changes audit-log encryption and needs migration steps.
Fixed: 1.22.1
Do: Upgrade Apache Allura to 1.22.1; every release through 1.22.0 is affected; Follow the 1.22.1 upgrade steps from the release post: upgrade through prior releases first, update requirements, run paster ensure_index, run migration 039 (field-level encryption), and run migration 040 cleanup once the new version is up; Review OAuth 1 consumer and token registrations and access logs for unexpected activity; no source describes the abuse pattern

### [critical] Apache Axis 1.x: unauthenticated class instantiation via SOAP fault exceptionName, RCE (CVE-2026-90436)
https://helix.ml/threat-watch/i/apache-axis-1-x-unauthenticated-remote-class-instantiation-via-soap-fault-exceptionname-enables-rce-cve-2026-90436 · Vulnerabilities · patched · since 2026-11-06 · CVE-2026-90436
A critical flaw in Apache Axis 1.x (EOL, all versions through 1.4) allows unauthenticated remote class instantiation via deserialization of inbound SOAP faults. When a SOAP <Fault> carries a <detail><exceptionName> element, Axis loads the named class—running its static initializer—and, if a String <data> element is present, instantiates it via its String constructor before verifying it is an AxisFault. With a suitable class on the application classpath this leads to remote code execution. The fault is parsed before per-service handler chains run, so service authentication handlers do not protect against it. Found by José Apari-Pantigozo of OKIOK. No Axis 1.x release is planned; a patch exists on the axis-axis1-java repository, and migration to Axis 2/Java is recommended.
Fixed: commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd (no 1.x release planned)
Do: Migrate off Apache Axis 1.x to Apache Axis 2/Java or another supported SOAP engine; If migration is not immediate, apply the patch from commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd to your Axis build; Audit applications and classpaths for exploitable classes reachable via String constructors or dangerous static initializers; Restrict network exposure of Axis 1.x SOAP endpoints as an interim mitigation

### [medium] US state/local government email DNS: typo and expired records let attackers send mail as agencies (no CVE)
https://helix.ml/threat-watch/i/dangling-dns-records-us-government-email-domains-typos-expired-dns-records-let-attackers-send-receive-email-and-spoof-ag · Vulnerabilities · unpatched · since 2026-11-05
Alex Shakhov of SH Consulting scanned 25,964 US government-related domains and found 43 whose SPF, MX, NS or DMARC records point at expired, mistyped or repurposed domains. The affected names are state and local bodies, not federal agencies: Dark Reading's account names Livingston County, Michigan, Pikeville, Kentucky, and the City of Rupert, Idaho. In Livingston and Pikeville, typos of Amazon SES's domain (amzonses[.]com and amasonses[.]com) in SPF records authorise thousands of IP addresses to send mail as those governments; the researcher counts 32,066 addresses for one typo. In Rupert, a lapsed neighbouring city's domain was bought by a gambling operator and used to send and receive email. Pikeville's domain is now listed on URIBL. The reported rotation of Livingston's authorised addresses every three to eight days is a claim without cited evidence of mail actually sent. The fix is to correct or remove the stale records, monitor domain expiry, and lock and renew any domain that DNS records depend on. No vendor patch applies.
Do: Audit all DNS records (SPF, MX, CNAME, NS, DMARC) for typos, expired, or purchasable 'dangling' domains and correct them immediately; Monitor domain expiry and lock/renew domains referenced in DNS records; Minimize SPF include lists and verify every third-party service domain character-by-character; Check DMARC rua/ruf reporting domains are owned and review DMARC reports for anomalies; Check sending domains against blocklists (e.g., URIBL) and investigate historical mail logs for abuse; Set registrar transfer locks and alerts on all domains referenced in DNS configurations

### [critical] Linux KVM: guest-to-host escape via malformed IPv4 checksum metadata lets guest VMs compromise the host (CVE-2026-99999)
https://helix.ml/threat-watch/i/linux-kvm-guest-to-host-escape-via-malformed-ipv4-checksum-metadata-lets-guest-vms-compromise-the-host-cve-2026-99999 · Vulnerabilities · partial · since 2026-10-14 · CVE-2026-99999
PwnEscape (CVE-2026-99999) is a Linux host kernel flaw, despite the name: the bug is in the IPv4 stack, not KVM. A guest can hand the host virtio-net checksum metadata that points inside the IPv4 header; the host writes the completed checksum there, corrupting a header it has already validated and acted on. A guest that controls its own packets can therefore leak host kernel memory back to itself repeatedly, crash the host and every VM on it, and take over the host. On 5 November PWNAI published Part 2 with full proof-of-concept code: from inside a Firecracker v1.16.1 microVM on an unpatched Ubuntu 26.04 AWS host kernel (7.0.0-1011-aws), run without the jailer, it used the leak to find and hijack a vCPU thread and ran code as root on the host. The vulnerable code dates to 2.6.27 (2008). Paulos Yibelo of PWNAI found it in Vercel's sandbox challenge and reported it privately on 4 September; Michael Tsirkin's fix landed upstream on 14 October and is in stable 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.57 and 7.2.11. Amazon Linux, Debian, SUSE, AlmaLinux and Red Hat 9/10 ship fixed kernels, but Ubuntu 22.04, 24.04 and 26.04 (including the linux-aws kernels) were still unfixed on 7 November, and there is no 7.0.y/7.1.y stable backport. AWS says EC2, Lambda and Fargate are not affected; self-managed Firecracker and KVM hosts are. No in-the-wild exploitation has been reported and the CVE is not in CISA KEV.
Fixed: Upstream 6785011f8b16 ('ipv4: validate checksum_start before completing checksum'), mainline 7.3; Stable 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.57, 7.2.11; Amazon Linux 2023 kernel-6.1.188-233.385.amzn2023, kernel6.12-6.12.110-135.201.amzn2023, kernel6.18-6.18.51-120.162.amzn2023; Amazon Linux 2 kernel-4.14.355-287.750, 5.4.302-229.494, 5.10.269-270.1108, 5.15.220-156.256; Debian bookworm 6.1.190-1 (DSA-6568-1), bookworm linux-6.12 6.12.113-1~deb12u1, trixie 6.12.115-2, sid 7.2.15-1; SUSE SLES 15 SP7 6.4.0-150700.53.87.3 (SUSE-SU-2026:4935-1), SLES 16.0 6.12.0-160000.40.1, SLE 12 SP5-LTSS 4.12.14-122.336.1; Ubuntu 26.10 linux 7.3.0-10.10 / linux-aws 7.3.0-1004.4; AlmaLinux 8 kernel-4.18.0-553.177.1.el8_10, 9 kernel-5.14.0-687.59.1.el9_8, 10 kernel-6.12.0-211.67.1.el10_2
Do: Patch every host that runs guests or sandboxes you do not fully trust (self-managed KVM, QEMU, Firecracker, Cloud Hypervisor): a public PoC now turns a guest into host root; Confirm the running kernel carries upstream 6785011f8b16 or its stable backport: 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.57, 7.2.11 or 7.3+; check uname -r after the reboot; Distro builds: Amazon Linux 2023 kernel-6.1.188-233.385 / kernel6.12-6.12.110-135.201 / kernel6.18-6.18.51-120.162; Debian bookworm 6.1.190-1, trixie 6.12.115-2; SLES 15 SP7 6.4.0-150700.53.87.3; AlmaLinux 8/9/10 kernel-4.18.0-553.177.1.el8_10 / 5.14.0-687.59.1.el9_8 / 6.12.0-211.67.1.el10_2; Ubuntu 22.04/24.04/26.04 (generic and linux-aws, including 7.0.0-*-aws) has no fixed kernel yet: move untrusted-guest hosts to a fixed kernel (Ubuntu 26.10, or a stable kernel listed above) or a livepatch, or stop running untrusted guests there; Run Firecracker under the jailer with its default seccomp filters: Part 2 was demonstrated without the jailer, and the jailer narrows what a hijacked VMM thread can do (it does not fix the kernel bug); QEMU/libvirt hosts that cannot reboot: CloudLinux and Red Hat describe turning off virtio-net checksum offload (QEMU csum=off,guest_csum=off; libvirt host/guest csum='off'); untested against the bug, needs a guest restart and costs throughput. AWS states there is no workaround; On virtualization hosts, migrate or shut down guests before rebooting so the patch does not become an outage; Patch ordinary servers too: Red Hat says a local attacker can trigger it; until then, dropping CAP_NET_RAW from containers and setting user.max_user_namespaces=0 removes some local paths (Akamai, CloudLinux)

### [critical] Cisco, WatchGuard, SonicWall: UCS Central and AuthPoint patches; EOL GMS file read unfixed (CVE-2026-109593)
https://helix.ml/threat-watch/i/node2shell-http2shell-broccoli2shell-cisco-watchguard-sonicwall-patch-releases-and-unpatched-gms-flaws-cve-2026-111497-e · Vulnerabilities · partial · since 2026-11-03 · CVE-2026-109593, CVE-2026-109594, CVE-2026-111497, CVE-2026-121637, CVE-2026-121638, CVE-2026-121639, CVE-2026-121640, CVE-2026-76506, CVE-2026-98432
This is a vendor patch roundup covering several unrelated products. The Node2Shell item is a Google Brotli decoder bug (CVE-2026-111497) that Cisco and Splunk ship with their own products, and it has separate records. WatchGuard published five advisories on 3 and 4 November 2026. Four cover AuthPoint Authentication Gateway (CVE-2026-121637 to CVE-2026-121640, CVSS 8.9 to 9.2), and all four are fixed in AuthPoint 7.6.0. The fifth, WGSA-2026-0033, covers a Linux kernel IPv4 use-after-free (CVE-2026-98432, CVSS 9.8). For that one WatchGuard says Fireware OS and WatchGuard AP run a vulnerable kernel but do not enable MPTCP and are not affected by the remote code execution chain circulating online. Its product table still lists Fireware OS, AP and Dimension as potentially affected, and none has a resolved release yet. Cisco published a fix for CVE-2026-76506, a High-rated (CVSS 3.1 7.6) flaw in the UCS Central web interface that can lead to code execution or information disclosure for an attacker who already holds valid credentials. The fix ships in 2.1(2c), and Cisco says it knows of no exploitation. Cisco also updated its Node.js and Brotli advisory for CVE-2026-111497. CISA has listed that Brotli flaw in KEV since 2026-10-27. Cisco says proof-of-concept code exists and that it knows of no malicious use against its own products, and SecurityWeek reports 19 Cisco products affected. SonicWall GMS 9.5.2 and earlier reached its last day of support on 2026-09-30. Per SecurityWeek, SonicWall will not fix CVE-2026-109593 (unauthenticated file read, NVD CVSS 3.1 9.1) or CVE-2026-109594 (authenticated SQL injection, CVSS 6.8).
Fixed: AuthPoint Authentication Gateway 7.6.0; Cisco UCS Central Software 2.1(2c); Google Brotli 1.0.10, 1.1.1 or 1.2.1 (upstream; CVE-2026-111497)
Do: Apply Cisco's UCS Central fix for CVE-2026-76506 (2.1(2c) or later; migrate from 2.0 and earlier); Update WatchGuard AuthPoint Authentication Gateway to 7.6.0 or later for CVE-2026-121637 to CVE-2026-121640 (affected: 1.0 up to 7.6.0); Stop using or isolate SonicWall GMS 9.5.2 and earlier: it is past end of support and CVE-2026-109593 and CVE-2026-109594 will not be fixed; restrict management access and plan a migration; Track WatchGuard WGSA-2026-0033 (CVE-2026-98432): no resolved release is listed yet for Fireware OS, WatchGuard AP or Dimension; WatchGuard says it will update the advisory when Ubuntu ships a fix for Dimension; For CVE-2026-111497 (Node2Shell), follow the Node2Shell records: upgrade Brotli to 1.0.10, 1.1.1 or 1.2.1 (upstream fixes) and check bundled Node.js and Brotli in Cisco and Splunk products against their advisories

### [high] APT: on-path attacker can make Debian/Ubuntu run unverified package as root (CVE-2026-109518)
https://helix.ml/threat-watch/i/apt-mitm-package-swap-rce-debian-ubuntu-mitm-attacker-can-swap-verified-packages-and-run-code-as-root-cve-2026-109518 · Vulnerabilities · partial · since 2026-11-04 · CVE-2026-109518
CVE-2026-109518 is a flaw in APT, the package manager on Debian and Ubuntu. An on-path attacker who can manipulate HTTP traffic between an APT client and its archive, for example through a malicious mirror or proxy, can make a package download fail and be retried after a redirect. The retry path reuses hard links, which lets the attacker install a package that was not verified, and the install runs with root privileges. Exposure needs a non-zero Acquire::Retries setting. Its default is 3 from Debian 12 and Ubuntu 22.04 onward, so older releases are exposed only if that setting was changed. NVD scores it CVSS 4.0 7.7 (High) and Ubuntu rates it High. No in-the-wild exploitation appears in the sources read, and CISA KEV does not list it. The Debian tracker shows fixed APT builds for bookworm (2.6.2), trixie (3.0.4) and sid (3.3.6), while Debian forky (3.3.5) was still vulnerable in the tracker snapshot. The Ubuntu tracker lists every supported release as vulnerable with no fixed version at the time of reading, so Ubuntu status needs a re-check against its security notice before anyone treats it as patched.
Fixed: 2.6.2 (Debian 12 bookworm); 3.0.4 (Debian 13 trixie); 3.3.6 (Debian sid / unstable)
Do: Update apt on Debian to the fixed build for your release (bookworm 2.6.2, trixie 3.0.4, sid 3.3.6); on Ubuntu, install the fixed build named in the Ubuntu security notice for CVE-2026-109518 once it is confirmed; Check Acquire::Retries in APT configs. Setting it to 0 removes the exposure until patched; older releases are exposed only when it is non-zero; Audit HTTP (non-HTTPS) package mirrors and proxies on the path to package installs; the advisory describes manipulation of HTTP traffic; Rebuild or re-verify derived distributions built on Debian/Ubuntu once their base fixes land; Monitor package-install logs for anomalies on systems that were exposed

### [high] Sogou Input Method: DNS-hijacked plaintext config fetch deploys DarkVigil backdoor (CVE-2026-120422)
https://helix.ml/threat-watch/i/darkvigil-slippynunchucks-dns-hijack-sogou-input-method-http-config-fetch-hijacked-to-deploy-backdoor-cve-2026-120422 · Vulnerabilities · patched · since 2026-11-04 · CVE-2026-120422
ESET attributes this campaign to SlippyNunchucks, a China-aligned actor that deploys the DarkVigil (FDMTP) .NET backdoor and has been active since at least 2023-09-15; ESET found no overlap with Mustang Panda. From 2026-07-01, the actor redirected DNS for config.pinyin.sogou.com to attacker-run staging servers. The Sogou Input Method helper SGTool.exe fetches its brand configuration over plaintext HTTP, so a forged response told it to download a legitimate signed Adobe helper renamed biz_helper.exe and a malicious libcef.dll; DLL sideloading then ran the implant. ESET does not identify where the DNS answer was altered and lists router compromise or ISP interception as possibilities. Reported victims include organisations and individuals in Hong Kong, Thailand, Japan, Vietnam, Oman and Sri Lanka, among them online gambling operators. Tencent released Sogou IME 16.10 on 2026-10-30 (ESET gives 29 or 30 October in different places), moving these requests to HTTPS. CVE-2026-120422, assigned by ESET as CNA, describes the plaintext configuration fetch; NVD had no CVSS score at last check. CVE-2026-51990 is a separate, earlier biz_helper.exe bug fixed in 16.3.0.3498. ESET also ties an earlier QuickFox VPN supply-chain compromise to the same actor; secondary coverage dates Fortinet's report to August 2026.
Fixed: 16.10
Do: Update Sogou Input Method on Windows to version 16.10 or later immediately (the fix moves the config request to HTTPS); Hunt DNS and proxy logs for config.pinyin.sogou[.]com resolving to anything other than Sogou infrastructure, and for connections to 47.239.250.102, 47.237.122.175 and 47.86.15[.]162, and to sogou-cdn[.]com, blog.wangmengfun[.]top, update.mssproxy[.]net and img.fusfun[.]top; Audit endpoints for sideloading of libcef.dll and biz_helper.exe beside Adobe binaries, especially \Components\SogouComMgr.exe, \Components\libcef.dll and SGTool.exe activity; ESET's libcef.dll SHA-1 is 8A60A8E90E1F5F08F28FE5A6DD57BD686C20DC23; Enforce HTTPS/HSTS and DNS integrity monitoring for internal use of Chinese-language applications; Review QuickFox installs against the vendor's clean release; ESET ties an earlier QuickFox supply-chain compromise to the same actor

### [critical] Apache OFBiz: 46 CVEs incl. pre-auth RCE and auth bypass fixed in 24.09.08
https://helix.ml/threat-watch/i/apache-ofbiz-50-cves-incl-pre-auth-rce-and-auth-bypass-fixed-in-24-09-08 · Vulnerabilities · patched · since 2026-11-04 · CVE-2026-100168, CVE-2026-100228, CVE-2026-105325, CVE-2026-105330, CVE-2026-105461, CVE-2026-109129, CVE-2026-109837, CVE-2026-109856, CVE-2026-109928, CVE-2026-114229, CVE-2026-114233, CVE-2026-114235, CVE-2026-114271, CVE-2026-114272, CVE-2026-114277, CVE-2026-66903, CVE-2026-68524, CVE-2026-71901, CVE-2026-73577, CVE-2026-73578, CVE-2026-73580, CVE-2026-74841, CVE-2026-76150, CVE-2026-76152, CVE-2026-81734, CVE-2026-81744, CVE-2026-81808, CVE-2026-81815, CVE-2026-81816, CVE-2026-81828, CVE-2026-82894, CVE-2026-82902, CVE-2026-82904, CVE-2026-82907, CVE-2026-82910, CVE-2026-82912, CVE-2026-82916, CVE-2026-82960, CVE-2026-83538, CVE-2026-83542, CVE-2026-84183, CVE-2026-84728, CVE-2026-85627, CVE-2026-92887, CVE-2026-97355, CVE-2026-97356
On 2026-11-04 the Apache OFBiz maintainer announced 46 CVEs affecting every release before 24.09.08, all addressed in 24.09.08. The announcement labels CVE-2026-68524 a pre-authentication remote code execution flaw, reached through an attacker-supplied screen definition, and describes CVE-2026-83542 (injection through the login-page widget) as unauthenticated RCE. CVE-2026-73578 is an unauthenticated saved-view authorization bypass that the post says has RCE impact; its exact preconditions are not stated. Several other RCE-class issues need an account: CVE-2026-82960 (a widget expression bypass of the Groovy sandbox), CVE-2026-84183 (RCE from a VIEW-only Content Manager role) and CVE-2026-85627 (authenticated code execution). The rest include a hard-coded JWT key that grants unauthenticated admin access (CVE-2026-105330), a password-reset flaw that enables full account takeover (CVE-2026-109928), a hard-coded credential in AdminServer that enables unauthenticated denial of service (CVE-2026-97355), SQL injection, XXE, SSRF, and many missing-authorization and IDOR flaws across Order, Catalog, Content, Payment and HR. The post gives no CVSS and marks no CVE as exploited. None of the 46 IDs appears in the CISA KEV feed (catalog 2026.11.03), and NVD had no record for the IDs sampled.
Fixed: 24.09.08
Do: Upgrade Apache OFBiz to 24.09.08 immediately; Until upgraded, treat any low-privilege or view-only account as able to reach authenticated RCE (CVE-2026-82960, CVE-2026-84183, CVE-2026-85627); If multitenant mode is used, review exposure to unauthenticated tenant DoS (CVE-2026-74841); Audit for signs of exploitation of pre-auth RCE (CVE-2026-68524, CVE-2026-83542) and the JWT / hard-coded-key access paths (CVE-2026-105330); Restrict external access to OFBiz instances and enforce authentication on REST APIs (CVE-2026-92887 is an auth bypass where the auth attribute is omitted); Review account and authorization configurations for abuse of view-only roles

### [critical] Xen XSA-523: guest reads/writes other domains and Dom0 memory via grant copy (CVE-2026-102703/CVE-2026-102704)
https://helix.ml/threat-watch/i/xen-xsa-523-arbitrary-read-write-via-grant-copy-cache-bugs-cve-2026-102703-cve-2026-102704 · Vulnerabilities · partial · since 2026-11-03 · CVE-2026-102703, CVE-2026-102704
Xen Project published XSA-523 version 2 as a public release on 2026-11-03 at 12:00 UTC. A batch of grant-copy operations on adjacent ranges can reuse cached validation results that were not always re-checked, which produced two flaws: frame numbers and grant references can be confused (CVE-2026-102703), and the check that limits copy-by-frame-number to the caller's own memory is misplaced (CVE-2026-102704). A malicious guest can therefore read and write memory belonging to other domains, including Dom0. The advisory covers all Xen releases from 4.6 onwards and says 4.5 and earlier are not affected. It states there is no known mitigation, so the fix is the only remedy. Upstream published two patch sets: one for xen-unstable and 4.19.x, and one for 4.18.x and 4.17.x. Downstream status is mixed on the day: Qubes issued QSB-121 with Xen 4.19.6-3 for Qubes 4.3 dom0, XCP-ng 8.3 LTS shipped the fix in its 2026-11-03 update, SUSE shows released packages for some products and in-progress or affected states for others, and Debian lists the package as unfixed. The advisory credits Anthropic using Claude as the discoverer, validation by Stephan Lipp of Ada Logics, and an independent report from the CodeAnt AI Security Research Team. No exploitation report was found in the sources checked.
Fixed: Upstream: xsa523 patch set for xen-unstable and 4.19.x; xsa523-4.18 patch set for 4.18.x and 4.17.x (advisory v2); Qubes OS 4.3 dom0: Xen 4.19.6-3 (QSB-121; security-testing repo first); XCP-ng 8.3 LTS: 2026-11-03 update (Vates VSA-2026-055); SUSE xen fixed-package list on CVE page: 4.20.4_08-150700.3.52.1, 4.18.6_03-150600.3.56.1, 4.17.7_04-150500.3.85.1, 4.16.7_18-150400.4.98.1, 4.12.4_78-3.157.1 (not all products Released)
Do: Patch every Xen host on 4.6 or later as a priority. Where the upstream patch sets apply (xen-unstable, 4.19.x, 4.18.x, 4.17.x), apply them; the advisory says patches target stable branches and may not apply cleanly to release tarballs, so update to the stable-branch tip first if needed; Use your vendor's packages where they exist: XCP-ng 8.3 LTS 2026-11-03 update (Vates VSA-2026-055), Qubes OS 4.3 dom0 Xen 4.19.6-3 (QSB-121, arrives via security-testing first), SUSE xen packages per the SUSE CVE page (state varies by product), and Debian once fixed (unfixed at check time); Hosts on Xen 4.6 to 4.16 have no upstream patch in the advisory; treat them as needing an upgrade to a branch with a vendor fix, and confirm your vendor's coverage before relying on a backport; Until a host is patched, treat untrusted guest workloads as able to read and write other tenants and Dom0 memory; consider isolating or draining those hosts; Re-check the Ubuntu, Red Hat, AWS and Citrix trackers, which could not be read or had no entry at check time, and monitor for exploitation reports

### [critical] Android: November 2026 patches fix 216 flaws, incl. critical Framework RCE (CVE-2026-58868)
https://helix.ml/threat-watch/i/android-november-2026-security-updates-patch-200-vulnerabilities-including-critical-framework-rce-cve-2026-58868 · Vulnerabilities · patched · since 2026-11-02 · CVE-2026-58868
Google released Android's November 2026 security updates on 2026-11-03, patching more than 200 vulnerabilities including two dozen critical-severity issues. The 2026-11-01 patch level fixes 119 flaws across Android runtime, Framework (65) and System (53); the most severe, CVE-2026-58868, is a critical Framework RCE needing no privileges or user interaction. Critical RCE, EoP and DoS bugs were also fixed in System, with 17 flaws already addressed via Google Play system updates. The 2026-11-05 patch level fixes 97 bugs in Kernel, Arm, Imagination, MediaTek, Unisoc and Qualcomm components, including critical issues in Bluetooth, pKVM, HID, MediaTek modem and a Qualcomm closed-source component. Separate bulletins cover Android XR and Wear OS. No exploitation is reported; all users should apply the latest patch levels.
Fixed: Security patch level 2026-11-01 (CVE-2026-58868 Framework RCE; 119 fixes); Security patch level 2026-11-05 (all 216 CVEs in the bulletin)
Do: Apply the 2026-11-05 security patch level (or later) to all managed Android devices as soon as possible; Ensure devices receive the 2026-11-01 patch level and current Google Play system updates; Update Android XR and Wear OS devices per Google's November bulletins; Prioritise patching of Qualcomm, MediaTek and Unisoc modem/Bluetooth components on enterprise fleets; Verify MDM compliance reporting enforces the new patch levels

### [medium] Keycloak: manage-users admin escalates to manage-realm via composite role mapping (CVE-2026-96448)
https://helix.ml/threat-watch/i/keycloak-manage-users-admin-escalates-to-manage-realm-via-composite · Vulnerabilities · unpatched · since 2026-09-25 · CVE-2026-96448
On 3 Nov 2026 Abraxas Labs published a lab proof of concept showing that a holder of manage-users, a delegated help-desk role that should not reach admin powers, can map a realm or client role onto their own account. That role's own name is not an admin role, but its composites include manage-realm or realm-admin. After the mapping, the same access token reads the full realm document and carries the nested admin role. A realm administrator must have built such a composite first. The defect is in the role-mapping permission check (RolePermissionsV2.canMapRole): for any non-admin role it returns true for manage-users and never walks the role's composites. We re-read that check at tags 26.8.1 and 26.7.5 and found it unchanged in both. Red Hat and NVD describe the same check as CVE-2026-96448, published 25 Sep 2026 and rated Moderate (CVSS 3.1 6.6); the write-up's 'no CVE' statement does not hold, and the write-up does not cite the CVE. Red Hat marks Red Hat Build of Keycloak as affected. We found no fixed upstream release and no community fix as of the 27 Sep 2026 analysis by Skycloak; no exploitation has been reported, and NVD's CISA SSVC enrichment lists exploitation as none and not automatable. The related CVE-2026-94000 (group-join composite walk, Red Hat Moderate) was closed upstream on 22 Sep 2026 as issue #53060; it is a sibling, not this defect. Until a fix ships, remove admin-including composites from roles that are not meant to grant admin, and cut manage-users down to the staff who need it.
Do: Audit every realm role and client role for composites that include realm-management admin roles (manage-realm, realm-admin, manage-clients, manage-authorization and so on). Remove them from any role that is not itself meant to grant admin.; Until a fix ships, treat every manage-users holder as able to reach any admin power that sits inside such a composite. Cut manage-users down to the people who need it.; Hunt in admin events: look for role-mapping CREATE operations where the target user is the acting admin (resourcePath users/<own-id>/role-mappings/...), especially for composite roles.; Watch the Keycloak security advisories for a CVE and fixed release, and upgrade when one ships.

### [high] Keycloak: account takeover through SAML broker redirect-parameter split (no CVE yet)
https://helix.ml/threat-watch/i/keycloak-account-takeover-through-saml-broker-redirect-parameter · Vulnerabilities · unpatched · since 2026-11-03
On 3 Nov 2026 Abraxas Labs published a lab-tested proof of concept for an unauthenticated account takeover in Keycloak's SAML identity-broker HTTP-Redirect endpoint. The researcher reproduced it on 26.8.1. An attacker who holds one genuine signed HTTP-Redirect response from a SAML identity provider that the realm trusts adds a forged SAMLResponse under a percent-encoded parameter name (SAML%52esponse). The endpoint parameter binding decodes that name and takes the forged document, while the signature check rebuilds the query from raw names and still accepts the genuine signature. Keycloak then signs in as the NameID inside the forged assertion, or creates that user through first-broker-login. The preconditions are a broker with signature validation on and 'Want Assertions signed' off, which is the usual result of metadata import, and an IdP that signs HTTP-Redirect responses; POST-only IdPs never give the attacker a signed GET. We re-read the Keycloak source at tags 26.8.1 and 26.7.5 and found the same code shape in both, so earlier 26.x lines are plausible but untested. As of 4 Nov 2026 we found no CVE for this flaw in NVD, no Keycloak advisory or GHSA, no fix release (the newest tag is 26.8.1), no vendor statement, and no report of exploitation in the wild; the only public PoC is the researcher's loopback lab. Until a fix ships, turn on Want Assertions Signed for every SAML broker, make IdPs POST-only where HTTP-Redirect is not needed, and look for logins whose NameID does not match the IdP session.
Do: For every SAML identity-provider broker, turn on 'Want Assertions signed' (wantAssertionsSigned=true). Recheck brokers created by metadata import, which leaves it off. With it on, the forged unsigned document is rejected.; If an IdP does not need HTTP-Redirect responses, make it POST-binding only on the IdP side.; At the reverse proxy, reject GET requests to /realms/*/broker/*/endpoint whose query parameter names contain percent-encoding. Also reject any request carrying more than one SAMLResponse after decoding.; Hunt for abuse: look for IDENTITY_PROVIDER_LOGIN and first-broker-login user creations where the brokered NameID doesn't match the IdP's own sign-in logs for that session. Also search access logs for 'SAML%' in broker endpoint queries.; Watch the Keycloak security advisories for a CVE and fixed release, and upgrade when one ships.

### [critical] @enspirit/elo: RCE via .constructor chain (JS) and Ruby #{} interpolation (CVE-2026-44267, CVE-2026-44266)
https://helix.ml/threat-watch/i/elo-compiler-sandbox-escapes-rce-via-constructor-chain-and-ruby-interpolation-enspirit-elo-cve-2026-44267-cve-2026-44266 · Vulnerabilities · patched · since 2026-11-03 · CVE-2026-44266, CVE-2026-44267
Two GitHub advisories, both published 2026-11-03 and both rated CVSS 3.1 9.8 by their author, cover the Elo compiler in @enspirit/elo: all versions up to and including 1.0.0 are affected, and 1.0.1 is the first patched version (npm lists 1.0.1 as published 2026-04-20; the current npm latest is 1.2.1). CVE-2026-44267 (GHSA-33r5-xmm8-v6x5) is in the JavaScript emitter, which passes member access such as .constructor.constructor through unfiltered, so an Elo string compiles to a live Function call and runs JavaScript when it is handled by defaultFormats.elo.parse(), by the bin/elo CLI, or by the elo-lang.org/try playground opened with ?code= and run=1. CVE-2026-44266 (GHSA-7w38-ggh5-v542) is in the Ruby emitter, which does not escape # in double-quoted string literals or in one subtype-constraint label, so #{...} sequences, including backticks, run shell commands when the emitted Ruby executes. Both advisories print working Elo payloads inline, and both describe playground and CLI execution, which is the reporter's account and was not reproduced here. We found no report of exploitation in the wild, and neither CVE is in the CISA KEV catalogue. Upgrade to 1.0.1 or later (1.2.1 is the current npm latest).
Fixed: @enspirit/elo 1.0.1
Do: Upgrade @enspirit/elo to 1.0.1 or later (npm latest is 1.2.1) wherever it is installed, including CI and DevOps hosts that run bin/elo or bin/eloc.; Audit every code path where an attacker-influenced string reaches defaultFormats.elo.parse() or an Elo CLI call; rule engines, config DSLs and form-builder DSLs are the documented use cases most exposed.; Until upgraded, do not pass untrusted files to bin/elo -f elo or bin/eloc -t ruby -x.; Do not open elo-lang.org/try links with ?code= and run=1 parameters from untrusted sources.; For apps that embed Elo output in Ruby, review generated Ruby for #{ sequences in string literals and subtype-constraint labels, and check whether any compiled Ruby ran on production hosts.

### [critical] Linux kernel TCP use-after-free (CVE-2026-98432): Anthropic-built root exploit; Ubuntu and RHEL unfixed
https://helix.ml/threat-watch/i/linux-kernel-tcp-use-after-free-race-mptcp-linked-root-exploit-ubuntu-rhel-unpatched-cve-2026-98432 · Vulnerabilities · partial · since 2026-10-11 · CVE-2026-98432
CVE-2026-98432 is a use-after-free race in the Linux kernel's IPv4 TCP connection setup, present since Linux 4.4. When a listener accepts a connection, the child socket takes over the request's IP options without copying them. Another CPU handling a retransmitted SYN can still be building a SYN-ACK from those options when the child socket frees them. Request-socket migration (net.ipv4.tcp_migrate_req, added in 5.14) has the same flaw. A remote, unauthenticated attacker who can reach any IPv4 TCP listener can try to win the race, and a lost race only fails the handshake, so the attacker can keep retrying. The fix, from Eric Dumazet and reported by Xinyang Ge of Anthropic, frees the options after an RCU grace period. It shipped in Linux 7.2.10 and 6.18.56 on 2026-10-11, in 6.12.113, 6.6.159, 6.1.190, 5.15.223 and 5.10.272 on 2026-10-15, and in 7.3. Anthropic says an exploit written by its model ran commands as root on a server with a multipath TCP (MPTCP) listener, with no credentials, taking about 53 minutes. It has published no exploit code. GitHub repositories created since 2026-10-29 claim race triggers, but none has been verified. Neither in-the-wild exploitation nor a CISA KEV listing has been reported. The kernel CNA scores it CVSS 9.8, and Red Hat rates it Critical: its RHSB-2026-016 bulletin warns of remote code execution, while its CVE page calls a crash or memory corruption the primary impact. Oracle rates it Important (8.1). Debian, Amazon Linux, SUSE 16 and Oracle UEK have shipped fixed kernels. As of 2026-10-30, Ubuntu (16.04 to 26.10) and RHEL 8, 9 and 10, including OpenShift and RHEL CoreOS, were still unfixed. Go 1.24 and later turn on MPTCP for Linux listeners by default.
Fixed: Upstream: commit e3f33b0a1d89 (posted 2026-10-01, merged 2026-10-05, in 7.3-rc7); Linux 7.3 and later; Upstream stable: 7.2.10, 6.18.56 (2026-10-11); 6.12.113, 6.6.159, 6.1.190, 5.15.223, 5.10.272 (2026-10-15); Debian: bookworm linux 6.1.190-1 (DLA-4841-1) and linux-6.12 6.12.113-1~deb12u1 (DLA-4850-1); trixie 6.12.113-1 (DSA-6568-1); sid 7.2.10-1; Oracle Linux UEK: ELSA-2026-500397, ELSA-2026-500398, ELSA-2026-500399 (2026-10-16; OL7 to OL10); Amazon Linux: ALAS2023-2026-3335 (kernel6.12, 2026-10-29), ALAS2023-2026-3365 and ALAS2-2026-4065 (2026-10-30); SUSE 16 kernel packages at 6.12.0-160000.40.1 or later
Do: Install a fixed kernel and reboot, Kubernetes nodes and container hosts included. Upstream fixes are in 7.3, 7.2.10, 6.18.56, 6.12.113, 6.6.159, 6.1.190, 5.15.223 and 5.10.272. Debian, Amazon Linux, SUSE 16 and Oracle UEK have shipped fixes. Ubuntu and RHEL 8, 9 and 10 have not as of 2026-10-30.; Until then, drop incoming IPv4 TCP packets that carry IP options, using Red Hat's nftables rule from RHSB-2026-016 ('ip protocol tcp ip hdrlength > 5 drop'). Red Hat says this reduces exposure but does not replace patching. The rule does not survive a reboot, and traffic between containers on the same host can bypass it.; Keep IPv4 TCP listeners off untrusted networks where you can, and patch internet-facing ones first, especially hosts with MPTCP listeners; Disable MPTCP where it is not needed (sysctl net.mptcp.enabled=0). This removes the setup Anthropic's exploit used, but the bug is still reachable over plain TCP. Per program, GODEBUG=multipathtcp=0 works for Go 1.24 and later services, which turn MPTCP on by default; the Go team calls that fragile.; Optionally boot with init_on_free=1. It makes stale reads return zeroes, which limits leaks, at a reported 1 to 5% cost on free-heavy workloads. It does not fix the bug.; Watch the Ubuntu and Red Hat trackers for fixed kernels, and investigate unexplained kernel crashes on hosts with exposed TCP services

Breach data from Have I Been Pwned (haveibeenpwned.com) is licensed CC BY 4.0. Vulnerability data from the CISA KEV catalog and NVD.