The pattern across the critical CVEs this week, 2 to 8 November 2026, is authentication that looks enforced but is not: MFA on a SonicWall VPN, password checks in OpenSSH on musl-based Linux, loopback trust in an AI cluster manager, and a Microsoft 365 sign-in where the victim entered the MFA code and the session still went to the attacker. Patch SonicWall CVE-2026-19868 first: it lets an attacker with valid credentials for a non-SAML login method skip SAML multi-factor authentication on SSL VPN, and CISA lists it as exploited. WordPress CVE-2026-119977 is the exception to the pattern, a race in the core updater rather than an authentication gap.
CISA added 3 vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog between 2 and 8 November 2026: WordPress on 3 November, Apple on 4 November and SonicWall on 6 November. None of the three scores 9.0 or above, and only unverified exploit code has surfaced, for WordPress. We also cover three flaws whose CVE records were published in the window but which CISA listed on 9 November, the day after it closed, because they were exploited and their three-day federal deadlines fall this week.
Which vulnerabilities should you patch first this week?
Patch SonicWall CVE-2026-19868 first, WordPress CVE-2026-119977 second, and IBM Aspera Faspex CVE-2026-123218 third. All five featured flaws are confirmed exploited, so the ranking turns on impact: whether the flaw defeats a security control, how large its internet-facing install base is, and only then CVSS. That is why SonicWall’s 7.5 ranks above Faspex’s 9.8.
OpenSSH CVE-2026-123158 (SSHole) ranks fourth only because it needs a specific configuration: on any Alpine or other musl-based host that exposes SSH with password login, treat it as the first priority, since Previdian reported a first exploitation attempt less than nine hours after the CVE was published on 5 November. GPUStack CVE-2026-102895 ranks fifth because its install base is narrower, although the vendor reports exploitation.
CVE-2026-19868: SonicWall SonicOS SSL VPN SAML MFA bypass
What it is: CVE-2026-19868 is an authentication flaw (CWE-308, use of single-factor authentication) in SonicWall SonicOS SSL VPN that lets an attacker who holds valid credentials for an alternate authentication method log in without completing SAML-enforced multi-factor authentication.
Affected products and versions: SonicOS SSL VPN configured to use SAML, on Gen7 7.3.3-7015 and older and Gen8 8.2.2-8015 and older, per the CVE record. SonicWall’s notice for SNWLID-2026-0014 lists the fixes as SonicOS 7.3.4-7013 and later for Gen7 and 8.2.3-8015 for Gen8. The same advisory fixes six other SonicOS vulnerabilities, including pre-authentication buffer overflows in the SSL VPN service and the TACACS+ authentication client that can take the service down, so move to the latest release for your platform rather than a single-CVE build. The Canadian Centre for Cyber Security’s description of the Gen8 range as prior to 8.2.2-8015 conflicts with the CVE record, which lists 8.2.2-8015 itself as affected.
Severity: CVSS 7.5 from CISA-ADP (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N). SonicWall scores it 7.1 with the same vector except PR:L, which is the more accurate reading, since the attack starts from valid credentials for another login method. EPSS 0.00621, as shown on OpenCVE on 11 November 2026.
Exploitation status: Confirmed in the wild by CISA, which added it to KEV on 6 November 2026, the same day SonicWall published the advisory. SonicWall says its PSIRT investigated a report indicating potential exploitation. Federal remediation due date 20 November 2026.
Patch status: The Gen7 fix, 7.3.4-7013, has been available since 20 October 2026, and the Gen8 fix, 8.2.3-8015, was released on 6 November 2026, the day the CVE was published. No vendor workaround has been published.
What to do: Upgrade SonicOS to the latest release for your platform, at least 7.3.4-7013 on Gen7 or 8.2.3-8015 or later on Gen8, on every firewall that runs SSL VPN with SAML. As interim hardening, not a vendor fix, make sure SSL VPN access that is meant to require SAML cannot be completed another way: remove local and LDAP users from SSL VPN access so every connection goes through the SAML flow. Review SSL VPN authentication logs as far back as logs allow, covering the full period the affected firmware ran with SAML, for logins that completed without a matching identity-provider sign-in, and reset passwords for accounts that can authenticate through an alternate method.
CVE-2026-119977: WordPress Core race condition during upgrades
What it is: CVE-2026-119977 is a time-of-check time-of-use race condition (CWE-367) in WordPress Core. During a full-package core upgrade, WordPress extracted the new files into a predictable, web-accessible directory under wp-content/upgrade, where an unauthenticated attacker who won a race against the extraction could reach the staged installer and execute code.
Affected products and versions: WordPress 4.7.0 through 7.1.3, across every maintained branch. Fixed in 7.1.4, released 28 October 2026 as a security release carrying 22 fixes, with backported releases for every branch back to 4.7, including 7.0.8, 6.9.11, 6.8.12, 6.7.11 and 6.6.11, down to 4.7.39.
Severity: CVSS 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, assigned by Wordfence as CNA). WordPress itself rates the issue Low, because the race needs a full-package update in progress and a web-reachable staging tree. EPSS 0.01199, as shown on OpenCVE on 11 November 2026.
Exploitation status: Confirmed in the wild. Added to CISA KEV on 3 November 2026. Federal remediation due date 6 November 2026. Wordfence reported blocking 13,095 attacks targeting the flaw in a 24-hour period, according to BleepingComputer on 4 November; those are blocked attempts, not confirmed compromises.
Patch status: Fixed in WordPress 7.1.4 and the branch backports. The fix appends 16 cryptographically random characters to the staging directory name, writes a blank index.php into wp-content/upgrade so the folder cannot be listed, and refuses to promote a staged wp-config.php. One catch remains: the update that installs the fix still runs the old unpacking code, so it creates a predictable directory one last time, wp-content/upgrade/wordpress-7.1.4-no-content/.
What to do: Deny web access to wp-content/upgrade at the web server or vhost level, confirm it returns 403, and only then update. Do not place an .htaccess file inside wp-content/upgrade itself, because the old updater clears that directory before extracting. On nginx use location ^~ /wp-content/upgrade/ { deny all; }; on Apache, RedirectMatch 403 ^/wp-content/upgrade/ outside the WordPress block. WordPress applies security releases in the background by default, so the vulnerable upgrade can run without an administrator. For detection, search access logs for successful requests to the staged installer: grep -h 'wp-content/upgrade/' access.log* | grep -E 'setup-config|install' | grep '" 200 ', paying particular attention to the window around your update to 7.1.4.
CVE-2026-123218: IBM Aspera Faspex 5 authorization bypass
What it is: CVE-2026-123218 is an incorrect authorization flaw (CWE-863) in IBM Aspera Faspex 5 that lets an attacker gain full administrative privileges on the file transfer server.
Affected products and versions: IBM Aspera Faspex 5.0.0 through 5.0.19. Fixed in 5.0.19 PL1; container deployments should run the faspex-core image at 5.0.19 Fix Pack 1.
Severity: CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, assigned by IBM as CNA). IBM’s description refers to an authorized user while its vector scores no privileges required. EPSS 0.00705, as shown on OpenCVE on 11 November 2026.
Exploitation status: Confirmed in the wild by CISA, which added it to KEV on 9 November 2026, the day after this window. Federal remediation due date 12 November 2026. IBM’s bulletin, published 7 November 2026, does not describe exploitation, and no first-observed date is public.
Patch status: Fixed in Faspex 5.0.19 PL1, per IBM’s bulletin of 7 November 2026.
What to do: Upgrade every Faspex 5 server to 5.0.19 PL1 now, given the three-day federal deadline. Review administrator accounts and recent configuration changes on Faspex; as general hardening, since IBM lists no workaround, restrict the administrative interface to trusted networks.
CVE-2026-123158: OpenSSH password authentication bypass on musl (SSHole)
What it is: CVE-2026-123158 is an authentication bypass (CWE-394) in OpenSSH on Linux systems built with musl libc and without PAM, where an account whose password field is set to an asterisk can be logged into with any password of roughly 257 to 1,024 bytes: musl’s crypt function returns an asterisk when it fails, SHA-512 crypt fails for keys over 256 bytes, and the result matches the stored asterisk. OpenSSH credits the discovery to Özgün Kültekin of Wakefield.
Affected products and versions: OpenSSH before 10.6p2 on Linux built with musl libc and without PAM, with password authentication enabled. Alpine Linux is the best-known example; OpenWrt, Buildroot, Yocto and many container images also use musl. Two further conditions narrow real exposure: an account whose password field holds an asterisk, and at least one other local account carrying a real SHA-crypt hash, from which sshd borrows a salt.
Severity: CVSS 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, assigned by MITRE as CNA), while OpenSSH’s release notes call 10.6p2 a critical security workaround. EPSS 0.16501, as shown on OpenCVE on 11 November 2026, the highest of this week’s featured CVEs.
Exploitation status: Confirmed in the wild. SANS Internet Storm Center saw the first attempts on its honeypots on 5 November 2026. Previdian reported a first exploitation attempt less than nine hours after the CVE was published and said it confirmed root access on an Alpine honeypot, according to The Hacker News; that is a single-source report. GreyNoise recorded the first successful exploitation it observed on 7 November 2026 at 00:46:51 UTC and reports the first public exploit was published on 5 November. Added to CISA KEV on 9 November 2026, the day after this window. Federal remediation due date 12 November 2026.
Patch status: Fixed in OpenSSH 10.6p2, released 5 November 2026, which makes sshd refuse a match when the stored password field is too short to be a real hash. Alpine published patched packages the same day for every branch back to 3.16: 10.6_p2-r0 on edge, 10.3_p1-r2 on 3.24, 10.2_p1-r1 on 3.23, 10.0_p1-r11 on 3.22 and 9.9_p2-r1 on 3.21, with older branches following the same pattern. Either setting PasswordAuthentication to no, with no Match block re-enabling it, or switching to a PAM-enabled build with UsePAM yes removes the exposure until the update is installed; both need sshd restarted.
What to do: On Alpine, install the patched package for your branch rather than building 10.6p2 from source, then restart sshd. Elsewhere on musl, upgrade to 10.6p2. Disable password authentication on any internet-facing SSH service and use keys. Direct root logins through the bug need PermitRootLogin set to yes; the upstream default, prohibit-password, blocks password logins as root, but other accounts whose password field is an asterisk stay open, so check PermitRootLogin, any Match blocks, and which accounts on exposed hosts have an asterisk password. Note for anyone scanning: in lab testing the bypass only succeeds on a second or later password attempt within the same connection, so single-attempt checks can miss a vulnerable host, and version strings alone can misreport a patched one.
CVE-2026-102895: GPUStack authentication bypass
What it is: CVE-2026-102895 is an authentication bypass (CWE-287) in GPUStack, an AI inference cluster manager, which treats requests that appear to come from the loopback address as administrator requests, letting an unauthenticated attacker gain admin access when GPUStack sits behind a same-host reverse proxy, or by sending a forged X-GPUStack-Real-IP header.
Affected products and versions: GPUStack versions before 2.2.0. Fixed in 2.2.0.
Severity: CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, assigned by GitHub as CNA). EPSS 0.00555, as shown on OpenCVE on 11 November 2026.
Exploitation status: Confirmed in the wild. The GPUStack advisory states the flaw has been observed exploited against a version 2.1.1 deployment, with attackers running reverse shells; it gives no date for that exploitation. Added to CISA KEV on 9 November 2026, the day after this window. Federal remediation due date 12 November 2026. The CVE record was published on 4 November 2026, while the GitHub advisory page shows an earlier publication date of 31 July 2026.
Patch status: Fixed in GPUStack 2.2.0.
What to do: Upgrade GPUStack to 2.2.0. Until then, set force_auth_localhost to true, make sure no reverse proxy presents external traffic as loopback, and strip client-supplied X-GPUStack-Real-IP headers at the edge. Audit the list of inference backends for entries you did not create, and review worker hosts for unexpected processes.
New hacking technique: PhantomDOM, a browser-in-the-middle operation against Microsoft 365
What researchers demonstrated: Browser-in-the-middle phishing is an established technique; what is new is the operation the ZeroBEC team documented in PhantomDOM on 5 November 2026, a custom setup that shows victims a reconstructed copy of the Microsoft 365 sign-in page while the real sign-in runs in a browser the attacker controls. We found no independent coverage, so this rests on ZeroBEC’s single write-up.
How it works:
What to do: Require a compliant or managed device in Conditional Access for Microsoft 365 sign-ins: the relayed sign-in completes in the attacker’s unmanaged browser, so it fails the device check. Move users to FIDO2 security keys or passkeys, as ZeroBEC recommends: the key’s origin check fails on the phishing page, and the cross-device passkey flow needs Bluetooth proximity to the signing device, which a remote attacker does not have. Remove weaker fallback sign-in methods that a relay can still use, and after a suspected relay, revoke sessions and refresh tokens and rotate credentials.
CISA KEV additions, 02 Nov to 08 Nov 2026
CISA added 3 CVEs to KEV in the window.
| CVE | Product | CVSS | Date added to KEV | Federal due date |
|---|---|---|---|---|
| CVE-2026-119977 | WordPress Core | 8.1 (Wordfence) | 3 Nov 2026 | 6 Nov 2026 |
| CVE-2024-27834 | Apple Safari, iOS, iPadOS, macOS, tvOS and watchOS | 5.5 (NVD) | 4 Nov 2026 | 18 Nov 2026 |
| CVE-2026-19868 | SonicWall SonicOS SSL VPN | 7.5 (CISA-ADP); 7.1 (SonicWall) | 6 Nov 2026 | 20 Nov 2026 |
Apple CVE-2024-27834 is a WebKit flaw fixed in May 2024, in Safari 17.5, iOS and iPadOS 17.5 and 16.7.8, macOS Sonoma 14.5, tvOS 17.5 and watchOS 10.5. CISA listed it after Sekoia attributed watering-hole attacks on phones to Russia’s APT29 with moderate to high confidence, according to Daily Security Review, with a compromised third-party script serving attacker code between 27 August and 3 September 2026; a 2024 bug entering KEV in 2026 means devices that skipped those updates are being targeted. Under Binding Operational Directive 26-04, issued on 10 June 2026 and replacing BOD 22-01, CISA sets each entry’s federal deadline from four variables rather than a severity score: whether the asset is publicly exposed, whether the flaw is KEV-listed, whether exploitation can be automated, and whether it yields total or partial control. Those combine into sixteen profiles across five tiers. A KEV-listed flaw that grants total control carries a three-day deadline and a mandatory forensic triage; other high-risk combinations get three days without the triage; most KEV entries get 14 days. That is why deadlines this week range from three days for WordPress, Faspex, SSHole and GPUStack to 14 days for SonicWall and Apple. On 9 November 2026, after the window, CISA added four more CVEs: SSHole, IBM Aspera Faspex and GPUStack covered above, and SignalWire FreeSWITCH CVE-2026-116779, which did not make this week’s five featured CVEs and will be covered next week. Full entries are in the CISA Known Exploited Vulnerabilities catalog.
Related reading
- Weekly Report: New Hacking Techniques and Critical CVEs, 26 Oct to 01 Nov 2026: PHP2Shell, Ivanti Connect Secure and GitLab, last week’s exploited flaws in shared components.
- Weekly Report: New Hacking Techniques and Critical CVEs, 19 to 25 Oct 2026: the Arista VeloCloud Orchestrator and Plex Media Server (Plex2Shell) KEV entries.
How FireCompass helps
Each of this week’s exploited flaws depends on a condition you can only check from outside: whether an SSL VPN uses SAML, whether a WordPress site exposes its upgrade directory, whether an SSH service on a musl-based host accepts passwords, and whether an AI cluster manager answers on the internet. FireCompass discovers internet-facing assets continuously and validates exploitability with proof of exploit, so the answer is a tested path, not a guess from a version string, with a false positive rate under 2 percent, against 40 to 70 percent from leading DAST tools. Previdian reported the first SSHole exploitation attempt less than nine hours after the CVE was published, faster than any quarterly or annual test cycle.
See which of your internet-facing assets an attacker would reach first.
Frequently asked questions about critical CVEs this week
Which CVEs were actively exploited this week?
CISA added 3 exploited CVEs to KEV between 2 and 8 November 2026: WordPress CVE-2026-119977, Apple CVE-2024-27834 and SonicWall CVE-2026-19868. OpenSSH CVE-2026-123158 was also exploited in the window, and it was added to KEV on 9 November 2026 with GPUStack CVE-2026-102895, which its vendor reports exploited, and IBM Aspera Faspex CVE-2026-123218.
What is the most critical CVE this week?
SonicWall CVE-2026-19868 is the most urgent vulnerability of 2 to 8 November 2026. It lets an attacker with valid credentials for a non-SAML login method bypass SAML multi-factor authentication on SonicOS SSL VPN, and CISA added it to KEV as exploited on 6 November 2026 with a federal due date of 20 November 2026.
Is SSHole (CVE-2026-123158) being exploited?
Yes. Previdian reported a first attempt less than nine hours after OpenSSH CVE-2026-123158 was published on 5 November 2026 and root access on an Alpine honeypot, a single-source report, and GreyNoise recorded successful exploitation on 7 November. It affects Linux systems built with musl libc and without PAM, such as Alpine, and CISA added it to KEV on 9 November.
How do I fix SSHole on Alpine?
Install the patched openssh package for your Alpine branch and restart sshd, rather than building OpenSSH 10.6p2 from source. Alpine published fixes on 5 November 2026 for every branch back to 3.16, including 10.6_p2-r0 on edge, 10.3_p1-r2 on 3.24, 10.2_p1-r1 on 3.23 and 10.0_p1-r11 on 3.22. Setting PasswordAuthentication to no, or using a PAM-enabled build with UsePAM yes, removes the exposure in the meantime.
How do I fix WordPress CVE-2026-119977?
Deny web access to wp-content/upgrade at the web server or vhost level, confirm it returns 403, and then update to WordPress 7.1.4 or your branch’s fixed release, such as 7.0.8, 6.9.11 or 6.8.12. Do not put an .htaccess file inside the upgrade folder itself, because the old updater clears it before extracting. WordPress applies security releases in the background by default, so the vulnerable upgrade can run without an administrator.
How do I fix SonicWall CVE-2026-19868?
Upgrade SonicOS to the latest release for your platform, at least 7.3.4-7013 on Gen7 or 8.2.3-8015 on Gen8, per SonicWall advisory SNWLID-2026-0014, which also fixes six other flaws. There is no vendor workaround. Remove local and LDAP users from SAML-protected SSL VPN access, and review logins as far back as logs allow.
How many vulnerabilities did CISA add to KEV this week?
CISA added 3 vulnerabilities to KEV between 2 and 8 November 2026: WordPress on 3 November, Apple on 4 November and SonicWall on 6 November. No additions were found for 2, 5, 7 or 8 November. CISA then added four more on 9 November: OpenSSH, IBM Aspera Faspex, GPUStack and SignalWire FreeSWITCH.
Why can a CVSS 7.5 outrank a 9.8?
A CVSS 7.5 is rated High, and it can outrank a 9.8 when the flaw is confirmed exploited and removes a control on an internet-facing gateway. In the week of 2 to 8 November 2026, SonicWall CVE-2026-19868 scored 7.5 but bypassed MFA on SSL VPN, so its exploitation status and position mattered more than its score. CISA’s own directive, BOD 26-04, works the same way: since June 2026 it sets federal deadlines from exposure, exploitation, automatability and impact rather than from a severity score.
