SSHole joins the KEV catalog with GPUStack, FreeSWITCH and Faspex
CISA confirms exploitation of SSHole (OpenSSH) and of flaws in GPUStack, FreeSWITCH and IBM Aspera Faspex: what is new, where sources differ, priorities.

On 9 November 2026 CISA, the US cybersecurity agency, added four vulnerabilities with the same deadline to its Known Exploited Vulnerabilities (KEV) catalog. We have already covered three of them one by one: GPUStack (CVE-2026-102895), SignalWire FreeSWITCH (CVE-2026-116779) and IBM Aspera Faspex (CVE-2026-123218). The fourth is SSHole (CVE-2026-123158), the OpenSSH flaw on Linux with musl and without PAM: in our latest article it was not yet in the catalog, and now CISA confirms it is being exploited.
SecurityWeek and Security Affairs, which reported on the catalog update, add a few details and some discrepancies. Below is the overall picture and what is new for each product.
The picture: four entries, one deadline
| CVE | Product | CVSS 3.1 | Issue | Fixed version |
|---|---|---|---|---|
| CVE-2026-102895 | GPUStack | 9.8 | administrator access without authentication | 2.2.0 |
| CVE-2026-116779 | SignalWire FreeSWITCH | 9.8 | code injection via SIP MESSAGE | 1.11.3 |
| CVE-2026-123158 | OpenSSH (SSHole) | 8.1 | password authentication bypass | 10.6p2 |
| CVE-2026-123218 | IBM Aspera Faspex | 9.8 | incorrect authorization, administrator privileges | 5.0.19 PL1 (according to SecurityWeek) |
For US federal agencies the deadline is 12 November 2026, three days after the addition, under directive BOD 26-04 as referenced in the catalog entries. For Faspex, FreeSWITCH and OpenSSH, use in ransomware campaigns is listed as “unknown”. No source identifies threat actors or campaigns.
The sources disagree on two side details: Security Affairs dates the OpenSSH addition to 6 November and cites directive BOD 22-01, while the catalog entry shows 9 November and BOD 26-04.
In MITRE ATT&CK terms, all four fall under T1190 (Exploit Public-Facing Application) when the service is reachable from the network; SSHole leads to logins with valid accounts over SSH (T1078, T1021.004), FreeSWITCH to command execution (T1059).
OpenSSH SSHole: exploitation now confirmed by CISA
The flaw is the one described in our two articles: according to NVD, OpenSSH sshd before 10.6p2, on Linux with musl and without PAM, accepts any password between 256 and 1,024 characters for some account configurations. The CVSS vector has high attack complexity (AC:H), consistent with the conditions required.
What is new is the KEV listing, the first official acknowledgement of exploitation: on 6 November Spain’s INCIBE-CERT and Hungary’s NKI reported no confirmed attacks, and there was only honeypot data reported by a private company. The sources do not agree on the timeline: SecurityWeek writes that exploitation started over the weekend, days after the fixes, while that first root login had been recorded on 6 November.
The NVD entry, updated on 10 November, lists among its references two public proofs of concept on GitHub, the Alpine Linux advisory and a GreyNoise page dedicated to SSHole events.
IBM Aspera Faspex: the fixed version and a silence
In our 7 November article the fixed version was not stated explicitly. According to SecurityWeek, IBM fixed the flaw on Friday 7 November with Aspera Faspex 5.0.19 PL1; this matches the NVD configuration, which lists versions up to but excluding 5.0.19.1 as affected.
Both outlets note, however, that IBM’s advisory does not mention exploitation, and Security Affairs found no public confirmation of attacks. The only indication is the KEV listing: it is not worth waiting for vendor confirmation before updating.
SignalWire FreeSWITCH: exploitation known since 28 October
According to SecurityWeek, SignalWire’s advisory, published on 28 October, already reported in-the-wild exploitation, without details on the attacks. The NVD entry dates from 5 November and the catalog addition from 9 November: if you run an installation that has not been updated since late October, look for signs of compromise, not just for the fix.
GPUStack: who saw the attacks
Security Affairs reports that exploitation against a version 2.1.1 deployment was flagged by researcher Javier Sixto, with no group identified. SecurityWeek writes instead that the flaw had been flagged as exploited as early as the end of July: it is the only source to say so and gives no further details.
Impact for European and Italian companies
The four products belong to different areas: AI infrastructure, VoIP telephony, SSH access on musl-based containers, images and devices, and file exchange with customers and suppliers. What they share is services that are often reachable from the Internet or by partners, and in three cases a 9.8 score with a network attack vector.
The KEV catalog only binds US federal agencies, but it is a useful reference for priorities. For entities in scope of NIS2, handling exploited vulnerabilities is part of the required security measures; where these platforms process personal or health data, a compromise can also trigger notification duties under the GDPR.
What to do now
- Take an inventory of the four products, including Alpine images and containers that run
sshdand musl-based appliances. - Update, starting with exposed instances: GPUStack 2.2.0, FreeSWITCH 1.11.3, OpenSSH 10.6p2 or your distribution’s fixed package (then restart
sshd), Aspera Faspex 5.0.19 PL1 as per the IBM advisory. - If you cannot update, CISA asks you to apply the vendor’s mitigations or stop using the product. For SSHole the stated mitigation is
PasswordAuthentication no. - Look for traces on instances left exposed with vulnerable versions, using the indicators from our dedicated articles: unexpected administrator API keys in GPUStack, SIP MESSAGE requests whose To field starts with
api+in FreeSWITCH, new administrators in Faspex, successful password logins on accounts with*in/etc/shadow. - Preserve logs before restoring: CISA points to its own forensic triage requirements.
How ARXDOME helps
ARX Shield shows open vulnerabilities by machine and by package, with those already exploited highlighted. ARX Expose and ARX Scout show which public addresses expose SSH, SIP or web interfaces, that is, where to start. ARX Sentry collects inventory and login logs from Linux servers, useful for the SSHole checks.
Last updated:


