CISA Gave Federal Agencies Until Thursday, November 12 to Fix Three Flaws: GPUStack's Unauthenticated Admin, FreeSWITCH's SIP Message Command Execution and IBM Aspera Faspex's Authorization Bypass
If you run GPUStack, FreeSWITCH or IBM Aspera Faspex 5, check the version today. CISA added all three to its Known Exploited Vulnerabilities catalog on Monday, November 9 and set a federal deadline of Thursday, November 12. For two of them the vendor itself says attacks have been seen. For the third, IBM's bulletin says nothing about attacks and CISA's listing is the only exploitation signal we found.
What has been reported
The CISA dates come from the KEV catalog JSON. The rest comes from the vendors' own advisories, read for us by agents. None of the three publishes indicators such as IP addresses or file hashes.
- GPUStack, CVE-2026-102895 (fixed in 2.2.0): GPUStack is software for running AI models across GPU machines. Per its GitHub advisory, versions before 2.2.0 treat any request that appears to come from the same machine as the built-in administrator. Two ways make a remote request look local: a reverse proxy on the same host (every request then arrives from 127.0.0.1), or a forged X-GPUStack-Real-IP header. The result is administrator access with no login, which includes creating permanent administrator API keys and, through an administrator-only endpoint that accepts a YAML definition, running code on worker machines. The advisory says it "has been observed exploited in the wild against a v2.1.1 deployment" and that attackers created custom backends that ran reverse shells. Severity is 9.8 out of 10. Workarounds in the advisory: set force_auth_localhost to true, make sure your reverse proxy cannot make outside traffic look local and strip any client-supplied X-GPUStack-Real-IP header, and keep the API off untrusted networks.
- FreeSWITCH, CVE-2026-116779 (fixed in 1.11.3): FreeSWITCH is open-source phone-system software. Per SignalWire's advisory of October 28, in 1.11.2 and earlier an incoming SIP MESSAGE can name the "api" chat handler, which runs FreeSWITCH commands with the privileges of the server. That means command execution on the machine, disclosure of configuration and credentials, and control of calls. Chat is on by default in the stock profiles. The advisory says "Exploitation of this path has been observed in the wild," and gives no date, victim or detail. If message authentication is enforced, any single account on the profile is enough, and installs that still carry the stock default user can be reached with no account at all. Severity is 9.8. The advisory's workaround is to set enable-chat to false on every profile that does not need inbound SIP chat. It says that requiring message authentication alone, or disabling the system API command, does not close the path. The fix adds a per-profile setting, enable-chat-api-proto, which is off unless you set it.
- IBM Aspera Faspex 5, CVE-2026-123218 (fixed in 5.0.19 PL1): Per IBM's bulletin of November 7, versions 5.0.0 through 5.0.19 let a user craft a message that bypasses authorization and gains full administrative privileges. Severity is 9.8 out of 10. IBM lists no workaround and says to upgrade. The bulletin's text says an authenticated user, while its scoring vector says no privileges are required; those two do not agree, and we cannot tell you which is right. The bulletin does not say the flaw is exploited. CISA's catalog entry describes an authenticated user. The bulletin's own dates are inconsistent (published November 7, modified November 6).
What it means
All three give an outsider administrator-level control of a machine that sits in a sensitive place: the one that runs your AI workloads and holds cloud keys, the one that carries your calls, the one that moves your large files. GPUStack and FreeSWITCH have vendor statements of attacks. The federal clock is short because CISA judged all three to be in use against real targets.
What to do
- GPUStack: upgrade to 2.2.0 or later. If you cannot yet, set force_auth_localhost to true, strip X-GPUStack-Real-IP at your proxy, and take the API off the internet. Then list the administrator API keys and the custom inference backends and delete any you did not create, since a permanent key survives the upgrade.
- FreeSWITCH: upgrade to 1.11.3. Until then set enable-chat to false on every profile that does not need it, delete any directory user with no password, and review logs for SIP MESSAGE requests whose recipient names a handler before a plus sign.
- Aspera Faspex 5: upgrade to 5.0.19 PL1 and confirm the faspex-core container reports Fix Pack 1. Review administrator accounts and recent administrative actions for anything you did not do.
- For all three, treat a machine that was reachable before patching as possibly taken, because the vendor or CISA says exploitation has happened. Rotate secrets the machine could read.
What is not known
Who is attacking, how many have been hit, and when it started. Whether the Faspex flaw has been exploited by anyone beyond CISA's listing. Whether public exploit code exists: our exploit harvester has logged no GitHub repository under any of the three CVE identifiers as of this writing. That absence is the harvester's view of CVE-named repositories, not proof that none exists.
How we know, and how we checked
We read the GPUStack and FreeSWITCH GitHub advisories and IBM's bulletin through agents, and took the added and due dates from the CISA catalog JSON. We tested nothing. For GPUStack we searched 258,890 edge blocks, 55,639 edge decoy hits and 1,721 origin honeypot hits since October 1 for the administrator-only endpoint path: zero matches. Our scan also matched 15 requests to generic paths (WordPress user lists and a bare api-keys path), which are routine probing and not GPUStack. We run no GPUStack, FreeSWITCH or Faspex, and the other two flaws are not reachable by a web path our tool can match, so we did not run an edge check for them. We add no indicators to our feed: none are published.
Sources
GPUStack GitHub security advisory GHSA-gj9m-f8ph-pmhr. SignalWire FreeSWITCH GitHub security advisory GHSA-mg63-h38w-8p9p, October 28, 2026. IBM Support, "Security Bulletin: IBM Aspera Faspex has addressed a vulnerability that could allow authorization bypass," November 7, 2026. CISA Known Exploited Vulnerabilities catalog, entries added November 9, 2026.
Every indicator in this post is in the feed. Free.
1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.