Four entries, one day, all with a deadline of November 12 for federal agencies under BOD 26-04: CVE-2026-102895, CVE-2026-116779, CVE-2026-123158, and CVE-2026-123218. CISA's alert text is as thin as ever — evidence of exploitation exists, indicators of compromise are not provided, and the directive's standing requirement that agencies check whether someone got in before the patch landed is the part any operator should copy, federal or not.
GPUStack: the real-IP trust gap, fixed in June, certified exploited in November¶
GPUStack is an open-source cluster manager for running LLMs across GPU workers — the piece of software a community AI node puts in front of its model workers. The catalog entry (CVSS 9.8, critical, "improper authentication") describes unauthenticated administrative access including code upload and execution.
The project's own advisory, published in its repository on July 31, is more specific: authentication bypass via trusted loopback source — a reverse-proxy TCP peer, or the X-GPUStack-Real-IP header — grants unauthenticated admin. Affected: every version below 2.2.0. Fixed: 2.2.0, which shipped June 18.
This is the chronic failure class of self-hosting: the application believes whatever tells it its peer's address, and the trust boundary that was supposed to be "a proxy I control" degrades into "whoever can reach the port." The header variant is spoofable by anything that can open a socket to the service; the socket variant bites every deployment where the management port is reachable in a way the operator did not map. This site keeps the same knob on its own list — the IP_HEADER-style settings every app from Vaultwarden downward asks for — and the rule does not change with the product: the value is only trustworthy if the proxy is the only thing that can reach the listener, and the listener is bound where nothing else can get to it.
The timeline is the ledger entry. Fix: June 18. Public advisory: July 31. KEV certification with evidence of live exploitation: November 9. 144 days between a fix being available on the project's own release page and the moment the US government certifies that attackers are already through. If your inference cluster predates 2.2.0, you are not patching a bug — you are auditing a compromise window the length of summer.
And GPUStack is having a season. The same repository published CVE-2026-102894 on September 30 — critical, the SAML callback trusts an unverified SAMLResponse, authentication bypass and account takeover, fixed in 2.2.2 — and CVE-2026-103002 on October 1, missing authorization in the Kubernetes API proxy, fixed in 2.2.2. Then October 26 brought eight more advisories that all shipped together in 2.3.0 (October 23): inference-only API keys accepted on worker-management endpoints, cluster-proxy path normalization letting reads escape their namespace scope, cross-cluster worker registration, WebSocket proxy route hijacking by impersonating federation peers, unauthorized model-file writes on workers, cross-organization API token disclosure through provider cloning, metadata leaks in watch streams — and the one that should read familiar to anyone who has ever managed a box with multiple logins: world-readable JWT signing keys, cluster tokens, and initial administrator passwords in /var/lib/gpustack, letting any local user forge admin credentials.
Nine advisories in five weeks on one self-hosted AI tool. The AI-discovery ledger this site keeps has mostly tracked finding old bugs; this is the other half — the AI-era stack is now a mainstream target, and the fix cadence of the tooling is not remotely near caught up.
FreeSWITCH: any registered account is root on the phone system¶
FreeSWITCH is the software-defined PBX under a large fraction of community and small-organization telephony — exactly the kind of service a fire hall, a coop ISP, or a clinic runs on commodity hardware in a closet. CVE-2026-116779 (CVSS 9.8, critical, fixed in 1.11.3, released August 28): sofia_presence_handle_sip_i_message() splits the To-user of an inbound SIP MESSAGE on a plus sign and treats the left side as a chat protocol selector. Pick the api chat protocol and you reach switch_api_execute() — the API console — as the daemon. From there: configuration and credential disclosure, arbitrary call control, and FreeSWITCH API commands including operating-system command sinks.
The exposure conditions are the part that matters, because they describe almost every default deployment:
- Inbound chat is enabled on the stock internal and external profiles. Not an exotic feature. The default configurations carry the affected code path.
- Any authenticated profile account is sufficient. Not admin. Any registered phone. In a building, that is every handset with a voicemail pin, and every desk phone's provisioning credential.
- In affected configurations, stock directory users without password material can also cross the authentication barrier — the barrier you assumed was protecting the feature can be absent entirely.
Exploitation has been observed in the wild. The fix shipped August 28; NVD published the CVE on November 5; CISA certified exploitation on November 9. Sixty-nine days from "fixed version available" to "government says someone is inside," with every unpatched box's logs going back through the whole summer.
The musl star bug: corrected¶
This site published the musl star-authentication bug on November 8. Two statements in that post died within a day:
- "No CVE identifier has been assigned for this one; the portable-release notes describe it as a critical security workaround, and this site will not mint a number for it." — A number exists now. CVE-2026-123158, "OpenBSD OpenSSH on Linux contains an unexpected status code or return value vulnerability," CVSS 8.1, high. OpenSSH's position — root cause outside sshd, shipped as a workaround — was and is accurate; the catalog does not care about the org chart.
- "No public exploitation statistics existed at this site's publish time." — True when written; falsified by the calendar one day later. CISA added it to the catalog on November 9 with evidence of active exploitation, and GreyNoise's live activity page now has a certified answer to the question it was built to track.
Note what the catalog titles it: OpenSSH on Linux. The glibc world is safe by one character; the catalog's scoping agrees. The November 12 deadline and the patch-and-assume-compromised checklist from that post stand unchanged: musl box, ldd $(which sshd) | grep musl tells you in one command whether you are in the population.
Aspera Faspex, briefly¶
CVE-2026-123218: incorrect authorization in IBM Aspera Faspex 5.0.0 through 5.0.19 lets an authenticated user craft a special request and land admin rights; fixed in 5.0.19 PL1. It is in this batch because it was in the batch — most community operators will never run a high-speed file-transfer gate, and the ones who do already knew this week was patch week. The reason it gets a paragraph is the pattern, not the product: all four entries carry the same three-day clock, and none of the four required a zero-day to matter.
The honest column¶
- The GPUStack and FreeSWITCH CVSS scores (9.8) come through heise's reporting of the catalog entries; at this site's publish time, NVD had no row for CVE-2026-102895 — advisory pages lag the catalog, and the catalog lags nothing, which is how exploitation evidence now travels: certified before fully documented.
- Nobody outside CISA knows the volume or geography of the exploitation; "observed in the wild" is a certification, not a census. Treat the KEV line as the floor, not the blast radius.
- The fix-to-KEV gaps measured here — 144 days (GPUStack), 69 days (FreeSWITCH) — count from fix availability, not from announcement. Both products sat fixable and exploitable simultaneously for the whole period. That combination is this site's recurring Plex pattern, and it is the norm now, not the exception.
- The next day's batch (November 10) already carries six more — two Barracuda Email Security Gateway authentication bypasses with a deadline of November 13, a Chromium use-after-free, an Outlook elevation. The cadence is near-daily; the three-day clock is the closest thing the catalog has to a normal.
For your deployment¶
- GPUStack: inventory builds against the ladder — 2.2.0 closes the loopback bypass, 2.2.2 closes SAML and Kubernetes-proxy paths, 2.3.0 closes the October eight. Anything older than 2.2.0 is a 144-day compromise window: read auth logs to the last pre-2.2.0 date, rotate the JWT signing material and the initial admin password, and fix the file permissions in
/var/lib/gpustackyourself — the 2.3.0 tuning helps future installs, not your disk. - FreeSWITCH: anything below 1.11.3 with a reachable SIP port and one registered account is a standing shell. Upgrade, then audit who authenticated since August 28 and what API commands ran —
switch_api_execute()leaves the same traces any fs_cli session does. If your deployment does not use inbound chat, that feature class is surface you never needed; verify what your profiles carry and turn off what your phones do not require. - OpenSSH/musl: the November 8 checklist is unchanged; the new fact is that the calendar has a government signature on the urgency.
- The BOD 26-04 move every shop should copy: when you patch a KEV entry late, the directive's requirement is not "apply update" — it is check whether someone was in before the fix landed. Logs back past the patch date, credentials rotated where the logs are ambiguous, and the box treated as suspect until the check is done. Federal deadlines end on the twelfth; your logs do not.
Sources: CISA alert, November 9, 2026; CISA KEV catalog JSON (release 2026-11-10T19:03Z, queried post-add); GPUStack repository advisories (CVE-2026-102895 entry published 2026-07-31; seven further advisories 2026-10-26) and GPUStack releases (v2.2.0: 2026-06-18, v2.3.0: 2026-10-23); FreeSWITCH CVE-2026-116779, NVD, published 2026-11-05 and FreeSWITCH releases (v1.11.3: 2026-08-28); heise: attack warning for GPUStack, FreeSwitch, OpenSSH and IBM Aspera Faspex (November 10); GreyNoise sshole activity page; this site's November 8 musl post.