On 9 November 2026 the US Cybersecurity and Infrastructure Security Agency added four vulnerabilities to its Known Exploited Vulnerabilities catalog, citing evidence of active exploitation. They affect an AI cluster manager, a telephony platform, a file-transfer platform and the OpenSSH server. Three let an attacker skip authentication or authorisation checks outright, and the fourth lets a peer that the telephony system accepts run internal administrative commands. Catalog listing is the signal many patch programmes key on, so all four now belong near the top of a remediation queue.
What CISA confirmed, and what the records add
The agency’s alert names each flaw by identifier and product and states that exploitation has been observed. It does not say who is exploiting them, how many systems are affected, which sectors have been hit, or whether the four are being used together. Nothing in the alert links the additions to one another. They appear in the same notice because they met the catalog’s criteria on the same day, not because of a shared campaign.
The technical detail below comes from the public CVE records for each flaw. Two of those records go a little further than the alert. The GPUStack record says exploitation was observed in the wild against a 2.1.1 deployment, and the FreeSWITCH record says exploitation has been observed in the wild. All four records also carry CISA’s own exploitation rating of “active”. Beyond that, none gives scale, actors or a timeline.
The four flaws, highest rated first
CVE-2026-102895, GPUStack authentication bypass. The record says versions before 2.2.0 of this open-source GPU cluster manager for AI model serving could treat a request as coming from the machine itself, and therefore as the built-in administrator, when local authentication enforcement was off, which was the default. A remote request could be made to look local, for example through a reverse proxy running on the same host. The record lists the result as unauthenticated administrative access: changes to users and models, creation of lasting administrator API keys, exposure of worker and cloud-provider secrets, and code execution. It is scored 9.8 (critical). The fix is version 2.2.0. Teams that front the service with a proxy on the same machine should check how their deployment forwards client details.
CVE-2026-116779, FreeSWITCH command execution. Before version 1.11.3, an accepted inbound text message to this open-source telephony platform could be routed so that its sender could run the platform’s internal API commands, including commands that reach the operating system, with the privileges of the FreeSWITCH process. The record says inbound chat is on in the stock internal and external profiles and that any authenticated profile account is enough, and that default directory users without password material can remove even that barrier in affected configurations. It lists configuration and credential disclosure, call control and command execution as consequences. It is also scored 9.8. Version 1.11.3 contains the fix, and the practical priority is any instance whose SIP service is reachable from untrusted networks.
CVE-2026-123218, IBM Aspera Faspex authorisation bypass. According to the record, Aspera Faspex 5.0.0 through 5.0.19 lets an authorised user craft a particular message that bypasses authorisation and grants full administrative rights. The scoring vector in the record lists no privileges required, which sits oddly with the “authorised user” wording, and the record does not reconcile the two, so assume an ordinary account is the minimum an attacker needs. IBM’s remediation entry names 5.0.19 PL1 (Fix Pack 1) on Linux and says to confirm that the core container image reports 5.0.19 with Fix Pack 1. Administrative control of a file-transfer platform means access to whatever the platform moves.
CVE-2026-123158, OpenSSH password bypass on musl-based Linux. The record says the SSH daemon in releases before 10.6p2 can accept a wrong password when built against the musl C library without PAM support. The cause is a missing safeguard for a case where the system misreads whether a stored string is a real password hash. For some account configurations, any password between 256 and 1,024 characters long is accepted. Alpine Linux is the example platform given. This is the lowest-rated of the four, at 8.1 (high), with high attack complexity and a CISA note that it is not automatable, which is why it is listed last even though OpenSSH is the most familiar name. The exposure is narrow, limited to musl builds without PAM, but where that combination exists and SSH is reachable, the impact is full account access.
Order of work
CISA’s alert repeats the logic of Binding Operational Directive 26-04, which directs federal civilian agencies to prioritise high-risk catalog entries on publicly exposed assets where a successful attack gives total control, and to defer lower-risk items. The directive binds only those agencies, and CISA encourages everyone else to adopt the same risk-based approach. For a small team the same reasoning gives a sensible sequence:
- Inventory first. Find out where each product runs, including inside container images and appliances that nobody thinks of as servers.
- Patch exposed instances before internal ones. The records name GPUStack 2.2.0, FreeSWITCH 1.11.3, OpenSSH 10.6p2 and Aspera Faspex 5.0.19 with Fix Pack 1 as the fixed releases.
- Where patching must wait, shrink exposure: restrict SSH to management networks, keep the SIP service off the open internet, and make sure GPUStack is not reachable through a proxy that lets clients influence the address it sees.
- Check for compromise, not just for the vulnerable version. The directive stresses checking whether the system was compromised before the fix landed. Review SSH logs for successful logins that nobody can account for, and look for new administrator accounts or API keys on Aspera and GPUStack, and unexpected API activity on the telephony server.
What remains unknown
The alert gives no indicators of compromise, no attribution and no victim profile, and the records do not say how long exploitation has been under way. Until fuller reporting appears, treat exploitation as confirmed and everything about scale and actors as unknown. The full list of catalog entries is tracked on our exploited vulnerabilities page.
Frequently Asked Questions
Which vulnerabilities did CISA add to the exploited-vulnerabilities catalog on 9 November 2026? Four: CVE-2026-102895 in GPUStack, CVE-2026-116779 in FreeSWITCH, CVE-2026-123218 in IBM Aspera Faspex and CVE-2026-123158 in OpenSSH. CISA says it saw evidence of active exploitation for each.
Which OpenSSH versions and systems are affected by CVE-2026-123158? The record covers releases before 10.6p2 running on Linux with the musl C library and without PAM, Alpine Linux being the example. On those configurations, some accounts accept any password between 256 and 1,024 characters.
Which of the four flaws bypass authentication or authorisation? GPUStack and OpenSSH let an attacker get past authentication, and Aspera Faspex lets a user get past authorisation checks to reach administrator rights. FreeSWITCH instead lets an accepted peer run internal commands.
What should I do first about these four flaws? Find every instance, patch the internet-facing ones first and look for signs of earlier compromise. The records name GPUStack 2.2.0, FreeSWITCH 1.11.3, OpenSSH 10.6p2 and Aspera Faspex 5.0.19 with Fix Pack 1 as the fixed releases.
Source: Cybersecurity and Infrastructure Security Agency (CISA). CVE record data from the CVE Program.