Four More Doors, Three Days to Close Them: CISA Adds GPUStack, FreeSWITCH, OpenSSH and IBM Aspera to the Exploited List

CISA alert and KEV additions November 9, 2026, alert updated November 10, 2026; federal remediation due November 12, 2026 under Binding Operational Directive 26-04

Four More Doors, Three Days to Close Them: CISA Adds GPUStack, FreeSWITCH, OpenSSH and IBM Aspera to the Exploited List

Threats

CISA NIST and the NIST Cybersecurity Framework (CSF 2.0)MITRE ATT&CK

CISA added four vulnerabilities to the Known Exploited Vulnerabilities catalog on November 9, each on evidence of active exploitation, each with a federal remediation deadline of Thursday, November 12 and a forensic triage requirement attached. The batch spans four unrelated stacks. GPUStack, the open-source GPU cluster and model-serving manager, carries CVE-2026-102895 in versions before 2.2.0: the application could treat remote requests as trusted local traffic, through certain reverse-proxy setups or a supplied X-GPUStack-Real-IP header, granting administrator access without credentials, including creating administrator API keys, modifying inference backends, reaching cloud credentials and running commands on workers; the vendor advisory documents an attack on a version 2.1.1 deployment in which malicious backends launched reverse shells. SignalWire FreeSWITCH carries CVE-2026-116779, scored 9.8, a command injection flaw in SIP MESSAGE handling in version 1.11.2 and earlier, fixed in 1.11.3, where a crafted message reaches the internal API command interface and can expose configuration files and credentials, control calls or run server commands; SignalWire confirms exploitation in the wild. OpenBSD OpenSSH carries CVE-2026-123158, the musl password bypass covered in this report on November 6 and November 9, now formally listed, fixed in portable OpenSSH 10.6p2 and distribution backports, with the running daemon restart as part of the fix. IBM Aspera Faspex carries CVE-2026-123218, scored 9.8, in versions 5.0.0 through 5.0.19, fixed in 5.0.19 PL1: IBM describes an authenticated user crafting a message to bypass authorization into privilege escalation, while its own scoring vector lists no privileges required, a gap IBM does not explain and that cautious teams should read in the attacker favor. Two clocks frame the batch. Today, November 10, is itself the due date for the Adobe Commerce and Brotli entries covered in yesterday's edition, and it is Patch Tuesday: Microsoft November release lands later today, after an October release that fixed a record 1,407 unique CVEs by the forecast count. Patching any of the four new entries does not revoke what exploitation may have already created, which is why the directive pairs the deadline with triage.

Executives

Four products, four different owners inside your organization, one Thursday deadline. The GPUStack item deserves board-level attention out of proportion to its familiarity: an AI serving manager that hands out administrator keys and holds cloud credentials is production infrastructure now, and in many companies it was installed by a research team outside the patch program. Ask for the four products by name, with a found-or-not-found answer for each, and ask what the forensic triage found, not only whether the patch applied. A clean patch report with no triage answer is half the federal requirement and the weaker half.

CIO / CISO

Sequence by exposure and by persistence. GPUStack first where it runs: upgrade to 2.2.0 or later, set force_auth_localhost=true and strip the client-supplied real-IP header at the edge until then, then review administrator API keys, inference backends and worker configurations, because minted keys survive the upgrade. FreeSWITCH to 1.11.3, with inbound SIP chat off on profiles that do not need it, noting that message authentication alone does not close the path. Faspex to 5.0.19 PL1 with the faspex-core image verified at the fix pack build, and external and guest accounts reviewed first given the scoring discrepancy. OpenSSH by configuration, musl without PAM, not by product name.

Engineers

Verify builds, not intentions. For Faspex, confirm the running container image reads the Fix Pack 1 build. For OpenSSH, update the package and restart sshd, then search authentication logs for accepted password logins on accounts that hold no password. For FreeSWITCH, check the version on every node, including integrator-installed gateways missing from the inventory, and review SIP MESSAGE traffic and configuration changes across the exposure window. For GPUStack, rotate worker and cloud credentials that a created backend could have touched. Preserve logs before patching where triage needs them; the update and the evidence compete for the same machine.

Everyone (non-IT)

Nothing in this batch asks home users for a special step. The one name a household might meet is OpenSSH, and ordinary Windows, Mac and mainstream Linux computers are outside the narrow conditions described. If you run a small server, a phone system or an AI experiment at work, the useful act is telling whoever manages it that these four names now carry a Thursday deadline, because the GPUStack and FreeSWITCH installs are exactly the ones central inventories tend to miss.