CISA Added GPUStack, FreeSWITCH and IBM Aspera Faspex to Its Exploited List Today, Due Thursday. All Three Score 9.8, and the GPUStack Advisory Is 101 Days Old
If you run GPUStack, FreeSWITCH or IBM Aspera Faspex, check your version today. CISA added all three to its Known Exploited Vulnerabilities catalog on Monday, November 9, 2026, with a due date of Thursday, November 12. GPUStack needs 2.2.0 or later. FreeSWITCH needs 1.11.3 or later. Faspex needs 5.0.19 PL1 on Linux. The CISA entries also ask for forensic triage, so on an internet-facing copy, patching alone is not the whole job.
What CISA says, from the KEV JSON
We read the catalog entries directly. All three were added November 9 with a due date of November 12, and each lists "Unknown" for ransomware campaign use. Each entry's required action cites CISA's BOD 26-04 and its "Forensics Triage Requirements", and each carries a forensic triage flag of yes. Due dates apply to U.S. federal agencies, but the list is a reasonable priority list for everyone.
GPUStack, CVE-2026-102895
GPUStack is software for running AI models across GPU hosts. CISA describes unauthenticated administrative access, including user and model changes, creation of persistent administrator API keys, disclosure of worker and cloud-provider secrets, and code execution through a POST to /v2/inference-backends/from-yaml.
The project's advisory (GHSA-gj9m-f8ph-pmhr, published July 31, 2026) gives the mechanism. With the setting force_auth_localhost left at its default of false, the code grants built-in administrator access to any request that appears to come from the loopback address. An attacker can make a request look local through a reverse proxy on the same host, or by sending a forged X-GPUStack-Real-IP: 127.0.0.1 header. No credentials are needed. It is rated CVSS 9.8 and affects versions before 2.2.0.
The advisory says it was "observed exploited in the wild" against a version 2.1.1 deployment, with attackers creating custom backends that ran reverse shells. That is the vendor's own statement, 101 days before CISA listed it.
Workarounds the advisory lists: set force_auth_localhost to true, strip client-supplied X-GPUStack-Real-IP headers at the edge, and keep the API off untrusted networks. Upgrade to 2.2.0 for the real fix.
FreeSWITCH, CVE-2026-116779
FreeSWITCH is an open-source telephony platform. CISA describes code injection that permits configuration and credential disclosure, arbitrary call control and command execution.
The advisory (GHSA-mg63-h38w-8p9p, published October 28, 2026) says an inbound SIP MESSAGE can select the api chat protocol through a plus prefix on the To user. That lets the sender run FreeSWITCH API commands, which can mean arbitrary operating system commands. The prerequisite is a single SIP MESSAGE accepted by a profile. Where MESSAGE authentication is enforced, any authenticated account on that profile is enough. Installations with the stock default directory user, which has no password, need no account at all. It is rated CVSS 9.8 and affects 1.11.2 and earlier.
Fix and workarounds, as the advisory states them: version 1.11.3 adds a per-profile enable-chat-api-proto parameter that is off unless set. Setting enable-chat to false on every profile that does not need inbound SIP chat is the only listed workaround that closes the path entirely. Enabling MESSAGE authentication (the default from 1.10.7) and removing directory users with no password reduces the risk but does not close it. Setting disable_system_api_commands to true removes only the system API, so the route still reaches other commands.
One thing we could not confirm: the advisory text we read does not say the flaw was exploited. Some outlets say it does. CISA's listing is the evidence we have that it is being exploited, and CISA has not said what it saw.
IBM Aspera Faspex, CVE-2026-123218
CISA describes an incorrect authorization flaw that could let an authenticated user craft a specific message to bypass authorization and escalate privileges.
IBM's bulletin lists Aspera Faspex 5.0.0 through 5.0.19 on Linux as affected, scores it CVSS 9.8, and says the result is full administrative privileges. The fix is 5.0.19 PL1. To confirm you have it, check that the faspex-core container image is 5.0.19 (1ce4b13, Fix Pack: 1). IBM lists no workarounds. The bulletin says nothing about known exploitation or public exploit code. The bulletin's initial publication date is November 7, 2026, but its modified date reads November 6, so the dates on it contain an error. We do not know what evidence CISA used.
Public proof-of-concept code, and when it appeared
We searched GitHub for each CVE number and read the repository metadata only. We did not open, run or evaluate any of the code, so we cannot say whether any of it works. Repositories named after a fresh CVE are often fake or booby-trapped, so do not run them.
FreeSWITCH: two repositories with the CVE in their names were created before CISA's listing. One was created November 1, 2026, four days after the advisory, and its description claims a command injection with "+20K target". The other was created November 6. Both predate the KEV entry, which came November 9. If either is real, the working exploit has been public for about a week.
GPUStack and Faspex: we found no repository named for either CVE. A general collection of CVE write-ups added a documentation folder for GPUStack on November 5 and for Faspex on November 7, which we have not read and cannot call an exploit.
Our own harvester found no proof-of-concept path fingerprints for the FreeSWITCH or GPUStack CVEs. That is the tool's coverage, not proof that none exist.
For GPUStack, the clock that matters is the vendor's, not a researcher's: its advisory says exploitation was seen in July.
What to do
Find them. GPUStack and Faspex are easy to forget because they sit behind other tools. Search your asset list and container images for all three.
Patch to GPUStack 2.2.0, FreeSWITCH 1.11.3, Faspex 5.0.19 PL1. Where you cannot patch today, apply the workarounds above.
If any of the three was reachable from the internet, treat it as possibly already compromised. For GPUStack, look for administrator API keys and inference backends you did not create, and rotate worker and cloud-provider secrets. For FreeSWITCH, look for unexpected SIP MESSAGE traffic, unfamiliar directory users and processes started by the FreeSWITCH account, and rotate credentials stored in its configuration. For Faspex, review administrator accounts and recent privilege changes.
Put none of the three management or signalling interfaces on the open internet unless you must.
How we know, and how we checked
We read the three CISA entries from the KEV JSON, the GPUStack and FreeSWITCH advisories on GitHub, and IBM's bulletin. We did not test any of the flaws and did not read exploit code. For GPUStack we ran our edge check for the path /v2/inference-backends/from-yaml since July 31, 2026: 0 matches across 105,882 edge blocks, 96,368 edge decoy hits and 5,609 origin honeypot hits. Those are real denominators, but we have no decoy for GPUStack, so zero means we saw none, not that nobody is probing. We did not run edge checks for FreeSWITCH, which is SIP rather than web traffic, or for Faspex. We make no claim to have seen any of these first, and we add no indicators to our feed because none of the three sources publishes any.
Sources
CISA Known Exploited Vulnerabilities catalog, entries for CVE-2026-102895, CVE-2026-116779 and CVE-2026-123218, added November 9, 2026. GPUStack advisory GHSA-gj9m-f8ph-pmhr. SignalWire FreeSWITCH advisory GHSA-mg63-h38w-8p9p. IBM Support bulletin 7295921.
How do AI models see YOUR brand?
AIPM has audited 250+ domains. 15 seconds. Free while still in beta.
Was this useful? Thirty seconds, no cookies, no tracking, no third parties, your address hashed and never stored. The question lives here: https://analytics.dugganusa.com/nps.html#post=cisa-kev-gpustack-freeswitch-aspera-faspex-due-november-12
Comments