Executive assessment
Today's brief leads with IXON VPN Client. All 15 selected findings retain their own technical scope, action, observed status, and evidence limits.
Panel synthesis: Themes: Actively exploited zero-days; Critical appliance and management-plane flaws; Network restriction as compensating control. Patch order: Finding 06 (HIGH Chrome V8 zero-day is exploited in the wild, fixed Chrome releases are listed, and a temporary JavaScript JIT restriction is available); Finding 02 (CRITICAL HPE AOS-CX RCE vulnerabilities have fixed versions across listed release lines and management-interface restriction controls); Finding 04 (CRITICAL OpenChoreo cluster-gateway issue has fixed versions and a restrictive NetworkPolicy control for the internal listener); Finding 01 (CRITICAL IXON VPN Client issue is fixed in 1.4.7 and later, and IXON Cloud blocks connections from versions below 1.4.7).
Finding 01 — IXON VPN Client
What changed: Successful exploitation of this vulnerability could allow an attacker to perform remote code execution on the computer running the client with elevated privileges. The following versions of IXON VPN Client are affected: VPN Client <1.4.7 (CVE-2026-75925).
Technical evidence: CVE-2026-75925; CVSS v3.1 9.6; weakness CWE-93; technical confidence High.
Why it matters: The Critical priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Analyst note: If patching is not possible, uninstall the client where it is no longer needed. IXON Cloud blocks connections from versions below 1.4.7, which IXON says prevents the vulnerability from being exploited. IXON reports no indication of exploitation and says it is aware of no public disclosure or exploit. ([ixon.cloud](https://www.ixon.cloud/Advisories/ADV-2026-08-05.pdf))
Affected: IXON VPN Client 1.4.6 and older on Windows, Linux and macOS. ([ixon.cloud](https://www.ixon.cloud/Advisories/ADV-2026-08-05.pdf))
Fix: IXON VPN Client 1.4.7 and later. ([ixon.cloud](https://www.ixon.cloud/Advisories/ADV-2026-08-05.pdf))
Action: Map CVE-2026-75925 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
[Evidence source: cisa.gov](https://www.cisa.gov/news-events/ics-advisories/icsa-26-246-02)
Finding 02 — HPE Patches Critical RCE Vulnerabilities in AOS-CX
What changed: Nearly two dozen issues, tracked collectively as CVE-2026-73749 (CVSS score of 9.8), were addressed with the updates. The cited source identifies the affected product and the available advisory or remediation status.
Technical evidence: CVE-2026-73749; CVSS v3.1 9.8; weakness CWE-284; technical confidence High.
Why it matters: The Critical priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Analyst note: Restrict CLI and web-based management interfaces to a dedicated layer 2 segment/VLAN and/or control them with firewall policies at layer 3 and above. ([csaf.arubanetworking.hpe.com](https://csaf.arubanetworking.hpe.com/2026/hpe_networking_-_hpesbnw05134.txt))
Affected: AOS-CX 10.18.0001; 10.17.1021 and below; 10.16.1051 and below; 10.13.1180 and below; 10.10.1180 and below (EOM). ([csaf.arubanetworking.hpe.com](https://csaf.arubanetworking.hpe.com/2026/hpe_networking_-_hpesbnw05134.txt))
Fix: AOS-CX 10.18.1002 and above; 10.17.1030 and above; 10.16.1060 and above; 10.13.1190 and above; 10.10.1181 and above (EOM). ([csaf.arubanetworking.hpe.com](https://csaf.arubanetworking.hpe.com/2026/hpe_networking_-_hpesbnw05134.txt))
Action: Map CVE-2026-73749 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
[Evidence source: securityweek.com](https://www.securityweek.com/hpe-patches-critical-rce-vulnerabilities-in-aos-cx/)
Finding 03 — USN-8725-1: Linux kernel vulnerabilities
What changed: Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system.
Technical evidence: CVE-2026-43071; CVSS v3.1 9.1; weakness CWE-125; technical confidence High.
Why it matters: The Critical priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Analyst note: For CVE-2026-53002, prevent the nf_conntrack_sip and nf_nat_sip modules from loading. ([access.redhat.com](https://access.redhat.com/security/cve/cve-2026-53002), [ubuntu.com](https://ubuntu.com/security/notices/USN-8725-1))
Affected: Ubuntu 16.04 LTS and Ubuntu 14.04 LTS. ([ubuntu.com](https://ubuntu.com/security/notices/USN-8725-1))
Action: Map CVE-2026-43071 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: ubuntu.com](https://ubuntu.com/security/notices/USN-8725-1)
Finding 04 — OpenChoreo: cluster-gateway internal proxy performs no caller authentication and is not read-only — data-plane Secret disclosure and arbitrary Kubernetes mutation.
What changed: OpenChoreo: cluster-gateway internal proxy performs no caller authentication and is not read-only — data-plane Secret disclosure and arbitrary Kubernetes mutation. CVE coverage: CVE-2026-73842.
Technical evidence: CVE-2026-73842; CVSS v3.1 9; weakness CWE-269, CWE-306, CWE-862; technical confidence High.
Why it matters: The Critical priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Analyst note: Restrict access to the cluster-gateway internal listener to trusted workloads with a restrictive NetworkPolicy. ([github.com](https://github.com/advisories/GHSA-rh53-xvx2-j327))
Fix: 1.0.3, 1.1.3 and 1.2.0. ([github.com](https://github.com/advisories/GHSA-rh53-xvx2-j327))
Panel assessment: Patch now: exploitation is unknown, but the flaw sits on an unauthenticated internal proxy that is not read-only, so exposure to untrusted workloads creates a high-blast-radius path into the data-plane cluster. The practical attack path is a malicious or compromised workload reaching the cluster-gateway internal listener, then using it to disclose Kubernetes Secrets and perform arbitrary Kubernetes mutations. (priority: patch now)
Action: Map CVE-2026-73842 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
[Evidence source: github.com](https://github.com/advisories/GHSA-rh53-xvx2-j327)
Finding 05 — Multiple vulnerabilities in CodeWhale
What changed: CVE coverage: CVE-2026-75911, CVE-2026-75858, CVE-2026-75912, CVE-2026-75856, CVE-2026-75915, CVE-2026-75913, CVE-2026-75857, CVE-2026-75859, CVE-2026-75914. The cited advisories disclose: Project config allow_shell override enables arbitrary shell command execution via cloned repository; rlm_eval auto-approves arbitrary Python execution, bypassing the user's approval policy; Argument Injection in git_blame Tool Allows Arbitrary File Read Without Approval; SSRF bypass - TOCTOU on DNS failure for DNS pinning; js_execution leaks parent environment to model context via missing env scrub; Argument Injection in git_show Tool Allows Arbitrary File Write Without Approval; exec_shell_interact sends LLM-controlled input to a running shell without an approval prompt; Project config instructions override enables arbitrary file read into AI system prompt via cloned repository; image_analyze follows workspace symlinks, leaking external file bytes.
Technical evidence: CVE-2026-75856; CVSS v4.0 9.2; weakness CWE-918; technical confidence High.
Why it matters: The Critical priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Panel assessment: Patch now if CodeWhale is in use where cloned repositories or tool inputs can be attacker-controlled, because the record shows multiple approval-boundary bypasses leading to shell/Python execution, file read/write, SSRF and environment leakage in a single fixed commit. (priority: patch now)
Action: Map CVE-2026-75856 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: github.com](https://github.com/advisories/GHSA-gx45-xrj5-g6c4)
Finding 06 — Google Chrome V8 Engine Zero-Day Actively Exploited
What changed: A critical vulnerability in the Chrome V8 JavaScript engine (CVE-2026-85046) is being actively exploited in the wild. Google has released a browser security update to address the flaw.
Technical evidence: CVE-2026-85046; CVSS v3.1 8.8; weakness CWE-843; technical confidence High.
Why it matters: Reported active exploitation elevates this above routine patching: validate exposure immediately, remediate, and assess for prior compromise.
Observed status: Observed in-the-wild exploitation is confirmed.
Analyst note: Temporarily set Chrome's JavaScript JIT policy to 'Do not allow sites to run JavaScript JIT', adding specific URL exceptions only where required. Google reports that an exploit for CVE-2026-85046 exists in the wild. ([support.google.com](https://support.google.com/chrome/a/answer/2657289?hl=en), [serotav.github.io](https://serotav.github.io/Writeups/v8/when-sorting-leads-to-confusion/), [chromereleases.googleblog.com](https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_01882797386.html), +1 more)
Affected: Google Chrome versions before 152.0.7977.82. ([nvd.nist.gov](https://nvd.nist.gov/vuln/detail/cve-2026-85046))
Fix: Chrome 152.0.7977.82/.83 for Windows and Mac, and 152.0.7977.82 for Linux. ([chromereleases.googleblog.com](https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_01882797386.html))
Action: Map CVE-2026-85046 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
[Evidence source: thehackernews.com](https://thehackernews.com/2026/09/google-releases-chrome-update-to-patch.html)
Finding 07 — Azure Cosmos DB Spoofing Vulnerability
What changed: Authorization bypass through user-controlled key in Azure Cosmos DB allows an authorized attacker to perform spoofing over a network. CVE coverage: CVE-2026-69857.
Technical evidence: CVE-2026-69857; CVSS v3.1 8.5; weakness CWE-639; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Analyst note: Microsoft states that it has fully mitigated the vulnerability and users need take no action. Microsoft reports 'Publicly Disclosed: No' and 'Exploited: No'. ([msrc.microsoft.com](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69857), [api.msrc.microsoft.com](https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Sep))
Action: Map CVE-2026-69857 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: msrc.microsoft.com](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69857)
Finding 08 — Inductive Automation Ignition
What changed: Successful exploitation of this vulnerability could allow any authenticated user to create projects. The following versions of Inductive Automation Ignition are affected: Ignition <=8.1.53 (CVE-2026-77393).
Technical evidence: CVE-2026-77393; CVSS v3.1 8.8; weakness CWE-276; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Analyst note: If patching is not possible, set the Gateway 'Create Project Role(s)' setting to match the Designer Role so that only users holding that role can create projects. CISA reports that no known public exploitation specifically targeting CVE-2026-77393 had been reported at publication. ([cisa.gov](https://www.cisa.gov/news-events/ics-advisories/icsa-26-246-06))
Fix: Ignition 8.1.54 or later, or the latest 8.3 version. ([cisa.gov](https://www.cisa.gov/news-events/ics-advisories/icsa-26-246-06))
Action: Map CVE-2026-77393 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
[Evidence source: cisa.gov](https://www.cisa.gov/news-events/ics-advisories/icsa-26-246-06)
Finding 09 — Tycon Systems TPDIN-Monitor-WEB3
What changed: Successful exploitation of these vulnerabilities could allow for an attacker to perform a man-in-the-middle (MitM) attack, cause a factory reset, wipe credentials, or retrieve sensitive information. The following versions of Tycon Systems TPDIN-Monitor-WEB3 are affected: TPDIN-Monitor-WEB3 <=2.2.9 (CVE-2026-77847, CVE-2026-82712, CVE-2026-82684).
Technical evidence: CVE-2026-82712; CVSS v3.1 8.8; weakness CWE-352; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Analyst note: Remove internet exposure from control-system devices and systems. Place control-system networks and remote devices behind firewalls, isolate them from business networks, and use a current VPN where remote access is required. CISA reports that no known public exploitation specifically targeting these vulnerabilities has been reported to it. ([cisa.gov](https://www.cisa.gov/news-events/ics-advisories/icsa-26-246-08))
Fix: Tycon Systems released TPDIN-Monitor-WEB3 firmware v2.4.2; a v2.2.9 unit requires the legacy Intel HEX build and upgrades directly with no intermediate version. ([cisa.gov](https://www.cisa.gov/news-events/ics-advisories/icsa-26-246-08))
Action: Map CVE-2026-82712 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
[Evidence source: cisa.gov](https://www.cisa.gov/news-events/ics-advisories/icsa-26-246-08)
Finding 10 — Pivotal Reactor Netty: Insufficiently Protected Credentials
What changed: Pivotal Reactor Netty, versions prior to 0.8.11, passes headers through redirects, including authorization ones.
Technical evidence: CVE-2019-11284; CVSS v3.1 8.6; weakness CWE-522; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Action: Map CVE-2019-11284 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2019-11284)
Finding 11 — Multiple vulnerabilities in Reactor Netty
What changed: CVE coverage: CVE-2020-5403, CVE-2023-34062, CVE-2023-34054. The cited advisories disclose: HttpServer, versions 0.9.3 and 0.9.4, is exposed to a URISyntaxException that causes the connection to be closed prematurely instead of producing a 400 response; HTTP Server, versions 1.1.x prior to 1.1.13 and versions 1.0.x prior to 1.0.39, a malicious user can send a request using a specially crafted URL that can lead to a directory traversal attack.
Technical evidence: CVE-2020-5403; CVSS v3.1 7.5; weakness CWE-20; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Analyst note: For CVE-2023-34054, disable Reactor Netty HTTP Server's built-in Micrometer integration as a temporary workaround. For CVE-2023-34062, disable Reactor Netty HTTP Server static-resource serving until patched. ([spring.io](https://spring.io/security/cve-2020-5403/), [spring.io](https://spring.io/security/cve-2023-34062/), [spring.io](https://spring.io/security/cve-2023-34054))
Fix: CVE-2020-5403: 0.9.5.RELEASE. CVE-2023-34062 and CVE-2023-34054: 1.1.13 and 1.0.39. ([spring.io](https://spring.io/security/cve-2020-5403/), [spring.io](https://spring.io/security/cve-2023-34062/), [spring.io](https://spring.io/security/cve-2023-34054))
Action: Map CVE-2020-5403 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2020-5403)
Finding 12 — Multiple vulnerabilities in Linux
What changed: CVE coverage: CVE-2026-64054, CVE-2026-64063, CVE-2026-64071, CVE-2026-64075, CVE-2026-64085, CVE-2026-64305. The cited advisories disclose: kernel, the following vulnerability has been resolved: net: shaper: reject duplicate leaves in GROUP request net_shaper_nl_group_doit does not deduplicate NET_SHAPER_A_LEAVES entries.
Technical evidence: CVE-2026-64054; CVSS v3.1 7.8; weakness CWE-415; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Action: Map CVE-2026-64054 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2026-64054)
Finding 13 — Multiple vulnerabilities in vLLM Incomplete
What changed: CVE coverage: CVE-2026-73557, CVE-2025-62164. The cited source identifies the affected product and the available advisory or remediation status.
Technical evidence: CVE-2025-62164; CVSS v3.1 8.8; weakness CWE-20, CWE-123, CWE-502, CWE-787; technical confidence Medium.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Analyst note: Leave enable_prompt_embeds disabled; restrict access to the API to trusted users. ([github.com](https://github.com/advisories/GHSA-pr7f-p5mw-fc87), [github.com](https://github.com/advisories/GHSA-mrw7-hf4f-83pf))
Affected: CVE-2026-73557: vLLM >= 0.21.0 and < 0.26.0. CVE-2025-62164: vLLM >= 0.10.2 and < 0.11.1. ([github.com](https://github.com/advisories/GHSA-pr7f-p5mw-fc87), [github.com](https://github.com/advisories/GHSA-mrw7-hf4f-83pf))
Fix: CVE-2026-73557: vLLM 0.26.0. CVE-2025-62164: vLLM 0.11.1. ([github.com](https://github.com/advisories/GHSA-pr7f-p5mw-fc87), [github.com](https://github.com/advisories/GHSA-mrw7-hf4f-83pf))
Action: Map CVE-2025-62164 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
[Evidence source: github.com](https://github.com/advisories/GHSA-pr7f-p5mw-fc87)
Finding 14 — Multiple vulnerabilities in SurrealDB
What changed: CVE coverage: CVE-2026-63733, CVE-2026-63735. The cited advisories disclose: Writes in a PERMISSIONS clause bypass table permissions; Custom API route lets authenticated callers override namespace/database scope via URL path.
Technical evidence: CVE-2026-63735; CVSS v4.0 8.6; weakness CWE-639; technical confidence High.
Why it matters: The High priority moves this beyond routine tracking and requires exposure validation, remediation, and compromise assessment.
Observed status: Observed in-the-wild exploitation status is unknown.
Action: Map CVE-2026-63735 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: github.com](https://github.com/advisories/GHSA-66r2-5gwj-gxm2)
Finding 15 — USN-8723-1: SPICE vdagent vulnerabilities
What changed: SPICE vdagent integer-overflow and filename-sanitization flaws permit denial of service or arbitrary file writes from a malicious or compromised SPICE host; Ubuntu has released fixed packages. CVE coverage: CVE-2026-57965, CVE-2026-57966.
Technical evidence: CVE-2026-57965; CVSS v3.1 5.1; weakness CWE-190; technical confidence High.
Why it matters: The Medium priority requires exposure validation and scheduled remediation through normal change control.
Observed status: Observed in-the-wild exploitation status is unknown.
Action: Map CVE-2026-57965 to owned assets, confirm the affected and fixed versions in the cited source, deploy the applicable remediation, and retain evidence of the exposure decision.
Evidence limits: fixed version or patch state unknown
[Evidence source: ubuntu.com](https://ubuntu.com/security/notices/USN-8723-1)