CVE Watch: Fully Patched N-central Servers Are Mining Monero
Nov. 6 to Nov. 16: a public chain is planting miners on N-central servers running the latest hotfix, Check Point gateways were rooted ahead of an ESXi wiper, and FreeSWITCH, GPUStack and IBM Faspex hit KEV at 9.8. A paste-ready heads-up for each.
Window: Nov. 6 to Nov. 16, 2026. CISA added 13 vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog in these ten days, but the most urgent problem isn’t on it: a public exploit chain called 4EverAble2Shell is planting cryptominers on N-able N-central servers, including ones running the latest hotfix. Check Point gateways were hit by a chain that ended with a wiper on an ESXi host, and FreeSWITCH, GPUStack and IBM Aspera Faspex all reached KEV with 9.8 scores. Below is every entry that cleared the bar (Critical or High, or exploited regardless of score), each with a ready-to-paste “Heads up”. SonicWall’s CVE-2026-19868 ran in last week’s Watch and hasn’t changed since.
| CVE | Vendor + product | CVSS | Exploited? | PoC | CISA KEV |
|---|---|---|---|---|---|
| CVE-2026-90436 | N-able N-central (bundled Apache Axis 1.x) | 9.8 Critical (CISA-ADP) | Known (researchers; N-able hasn’t confirmed) | Public | No |
| CVE-2026-123039 | Check Point Quantum gateways and management (Gaia) | 7.8 High | Known | None known | Yes, Nov. 13 |
| CVE-2026-116779 | SignalWire FreeSWITCH | 9.8 Critical | Known | None known | Yes, Nov. 9 |
| CVE-2026-102895 | GPUStack | 9.8 Critical | Known | None known | Yes, Nov. 9 |
| CVE-2026-123218 | IBM Aspera Faspex | 9.8 Critical | Known (CISA) | None known | Yes, Nov. 9 |
| CVE-2026-116606 | Barracuda Email Security Gateway | 9.3 Critical (v4.0) | Known | Public checker (reported) | Yes, Nov. 10 |
| CVE-2026-111560 | Barracuda ESG, ADC, WAF, WSG, BMA, WCC | 8.6 High (v4.0) | Known | None known | Yes, Nov. 10 |
| CVE-2026-123158 | OpenSSH on musl without PAM (Alpine and others) | 8.1 High | Known | Public | Yes, Nov. 9 |
| CVE-2026-125350 | Google Chrome (Chromium) | 8.8 High (CISA-ADP) | Known | None known (private exploit in use) | Yes, Nov. 10 |
| CVE-2026-114713 | UnrealIRCd | 8.6 High | Known | Public (reported) | Yes, Nov. 13 |
| CVE-2026-20320 | Cisco BroadWorks | 7.5 High | Known (CISA); Cisco has no direct evidence | None known | Yes, Nov. 10 |
| CVE-2026-76964 | SAP NetWeaver AS ABAP (ICM) | 10.0 Critical | No evidence | Private (reported) | No |
| CVE-2026-89126 | SAP Web Dispatcher | 10.0 Critical | No evidence | Private (reported) | No |
CVE-2026-90436: N-able N-central remote code execution chain (4EverAble2Shell)
4EverAble2Shell is a public exploit chain that takes an N-central server from no login to root. N-central is N-able’s remote monitoring and management platform for MSPs, and the chain abuses CVE-2026-90436 in Apache Axis 1.x, an end-of-life library through version 1.4, together with a separate N-central privilege escalation that has no CVE yet (Previdian tracks it as VULN-2026-0009). The Axis bug is unsafe handling of SOAP faults that lets an unauthenticated attacker instantiate classes remotely, which here gives command execution as the nable account before the privilege step finishes the job. An attacker needs network reach to the server, and N-able says the chain requires the Legacy API to be enabled. Because N-central pushes commands to every managed endpoint, a compromised server is a direct line into an MSP’s customers.
Heads up: CVE-2026-90436 is 9.8 from CISA’s enrichment (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H); Apache rates it critical without a score. Not on KEV, and EPSS is 1.1% (67th percentile), which badly undersells it. Exploit is PUBLIC: researcher Sean Bales published 4EverAble2Shell and a sister chain, Agent2Shell (SYSTEM on Windows agents and probes), late Nov. 11 ET, after dumping 33 Able2Shell exploits on Nov. 8. KNOWN campaign: Huntback counts at least 21 compromised N-central servers in seven countries from attacker mining-pool stats, 19 of them on the latest build 2026.4.1.26 (HF2), all dropping XMRig; first full-chain attempts hit 09:16 UTC Nov. 12, with Previdian seeing probes from 08:30. N-able’s Nov. 12 advisory said it saw no signs of compromise; it published IoCs Nov. 13. No named actor. Access: remote over the internet, no auth, no user interaction, fully automated. Fix: HF2 does NOT stop this chain. Disable the Legacy API per N-able’s KB, keep it off the internet, and Huntress says to pull exposed servers offline until N-able ships guidance; Apache has a patch commit but no Axis 1.x release. Hunt for requests to /dms/services/ServerUI referencing jline.internal.TerminalLineSettings, xvd.service units, files under /tmp/.xvd or /var/tmp/.xvd, and 157.20.241[.]16. Dates: Axis CVE published Nov. 6; chain published Nov. 11/12 as full disclosure, with Bales publicly criticizing N-able’s response time, so not coordinated. Scanning: KNOWN (Previdian; Censys counted 1,728 exposed N-central instances). Advisory: https://status.n-able.com/
Sources: BleepingComputer, Huntback, Previdian, Huntress, CSO Online, N-able HF2 notes, N-able Legacy API KB, Apache.
CVE-2026-123039: Check Point Gaia DynamicCLI local privilege escalation
This bug turns any local foothold on a Check Point gateway or management server into root. It affects Quantum Force firewalls, management and log servers, Multi-Domain servers and Maestro on R82.20, R82.10, R82 and R81.20 before the fixed Jumbo Hotfix takes, plus end-of-support R81.10 and R81. The type is incorrect permission assignment: the root-owned DynamicCLI daemon listens on a world-writable socket at /tmp/dynamic_socket and doesn’t check who’s calling. Attackers reached it after breaking in through the PHP2Shell flaws (CVE-2026-109618 and CVE-2026-109619), per Check Point Research. The business impact is a fully owned perimeter device, and in this campaign a destroyed VMware ESXi host behind it.
Heads up: CVE-2026-123039 is CVSS 7.8 High from Check Point (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). KEV: yes, added Nov. 13, federal deadline Nov. 16. EPSS 2.2% (83rd percentile). Exploitation is KNOWN: Check Point says it saw active exploitation against “a couple of dozen customers”; no public PoC reported. Campaign: KNOWN per Check Point Research, in waves on Oct. 30 (Israeli organizations) and Nov. 2, deploying the TSGA backdoor as slot_CPconfigdaemon and TSProxy as /lib/libcpfwcommon.so (both PhiliKit variants), then a wiper called destroy_v6 on ESXi with a DREAM_ANNEXATION.txt note. Actor: unknown. The Hacker News ties PhiliKit to China-nexus Armory Castle (UNC5221), but Check Point says it can’t attribute with high confidence, so treat any link as SUSPECTED. Access: local and authenticated, but it was chained behind remote, internet-facing PHP2Shell initial access; CISA rates it not automatable on its own. Fix: Jumbo Hotfix R82.20 Take 14, R82.10 Take 52, R82 Take 132 or R81.20 Take 174; no fix for R81.10/R81. Interim workaround in sk1000362 is disabling dynamic_server, which breaks Dynamic CLI commands. After patching, ls -l /tmp/dynamic_socket should show 0660, not 0777, and check /var/log/dynamicCli.log. Patch the PHP2Shell bugs too. Dates: exploited as a zero-day from Oct. 30; sk created Nov. 8; CVE and research published Nov. 12; reporter not disclosed. Scanning: none reported. Advisory: https://support.checkpoint.com/results/sk/sk1000362
Sources: Check Point sk1000362, Check Point Research, The Hacker News, CISA, CVE record.
CVE-2026-116779: SignalWire FreeSWITCH code injection
Why now: SignalWire’s advisory is dated Oct. 28 and the CVE Nov. 5, but exploitation was confirmed and CISA added it to KEV on Nov. 9.
This flaw lets a remote caller run commands on a FreeSWITCH telephony server by abusing inbound SIP chat messages. It affects FreeSWITCH 1.11.2 and earlier and is fixed in 1.11.3. The type is code and command injection (CWE-77/78), in how chat messages reach FreeSWITCH’s API command handling, which the fix now gates behind a new per-profile setting that’s off by default. An attacker only needs to reach a SIP profile: chat is on by default on the stock internal and external profiles, and where message auth is enforced, any single account will do, including the passwordless default user in the stock vanilla config. The business impact is a hijacked phone platform, with call fraud, eavesdropping and a foothold in the network all on the table.
Heads up: CVE-2026-116779 is CVSS 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) in SignalWire’s GitHub advisory. KEV: yes, added Nov. 9. EPSS 2.5% (85th percentile). Exploitation is KNOWN: the advisory says it “has been observed in the wild”, with no details. No public PoC reported. No named campaigns or actors. Access: remote over the internet wherever SIP is exposed, no real auth in default configs, no user interaction, and CISA rates it automatable. Fix: upgrade to 1.11.3. Until then, set enable-chat=false on every profile that doesn’t need inbound SIP chat; the advisory says auth-messages or disable_system_api_commands=true alone are NOT enough. Also give the stock default user a password or set allow-empty-password to false. Dates: credited to Örn Arnarson and Gunnlaugur (discovery date not disclosed); advisory Oct. 28, CVE Nov. 5; handled through a vendor advisory, but coordination isn’t described. Scanning: none reported. Advisory: https://github.com/signalwire/freeswitch/security/advisories/GHSA-mg63-h38w-8p9p
Sources: SignalWire advisory, CVE record, eSecurityPlanet, The Hacker News.
CVE-2026-102895: GPUStack authentication bypass
Why now: the CVE was published Nov. 4, and CISA added it to KEV on Nov. 9 after in-the-wild exploitation was reported.
This bug lets anyone skip login on GPUStack, an open-source manager for GPU clusters that serve AI models. It affects GPUStack before 2.2.0. The type is authentication bypass by spoofing: GPUStack trusts requests that appear to come from localhost, and by default doesn’t force auth for them. An attacker gets that trust by sending a forged X-GPUStack-Real-IP: 127.0.0.1 header, or for free when a reverse proxy on the same host makes every request look local. The business impact is a takeover of expensive GPU infrastructure, with the attacker able to run their own code on it.
Heads up: CVE-2026-102895 is CVSS 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) from GPUStack’s advisory. KEV: yes, added Nov. 9. EPSS 0.52% (45th percentile). Exploitation is KNOWN: the advisory says it was observed against a v2.1.1 deployment, where attackers created custom backends that ran reverse shells, reported by Javier Sixto (ulex.fr). No public PoC reported. No named campaigns or actors. Access: remote over the internet, no auth, no user interaction, easily scripted (it’s one header). Fix: upgrade to 2.2.0. Mitigations per the advisory: set force_auth_localhost=true, strip client-supplied X-GPUStack-Real-IP at your edge, and keep the API off untrusted networks. eSecurityPlanet notes upgrading doesn’t revoke admin API keys an attacker already made, so audit keys and custom backends. Dates: discovery not disclosed; CVE published Nov. 4 (the GitHub advisory shows Jul. 31, which doesn’t match); KEV Nov. 9; coordination not described. Scanning: none reported. Advisory: https://github.com/gpustack/gpustack/security/advisories/GHSA-gj9m-f8ph-pmhr
Sources: GPUStack advisory, CVE record, eSecurityPlanet.
CVE-2026-123218: IBM Aspera Faspex incorrect authorization
This flaw lets a crafted message get past authorization checks in IBM Aspera Faspex, the file-exchange platform companies use to send large files to partners. It affects Faspex 5.0.0 through 5.0.19 and is fixed in 5.0.19 PL1 (Linux). The type is incorrect authorization (CWE-863). IBM’s text describes an authorized user crafting a message, but its own CVSS vector says no privileges are needed, so the access requirement is unclear. The business impact is exposure of the sensitive files Faspex exists to move, and IBM’s scoring rates confidentiality, integrity and availability all High.
Heads up: CVE-2026-123218 is CVSS 9.8 from IBM (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). KEV: yes, added Nov. 9. EPSS 0.54% (46th percentile). Exploitation: KNOWN per CISA’s listing, but IBM’s bulletin doesn’t mention it and no attack details or actors are public. No PoC known. No campaigns or named actors. Access: network-reachable; whether you need a Faspex account is contested (IBM’s prose vs. its PR:N vector), so assume internet-facing servers are at risk; CISA rates it automatable. Fix: patching is required, IBM lists no workarounds. Confirm the faspex-core container reports 5.0.19 (1ce4b13, Fix Pack: 1). Dates: reporter and discovery not disclosed; IBM bulletin and CVE published Nov. 7 (the bulletin’s modified date says Nov. 6, an IBM inconsistency); normal vendor bulletin. Scanning: none reported. Advisory: https://www.ibm.com/support/pages/node/7295921
Sources: IBM bulletin, CVE record, eSecurityPlanet.
CVE-2026-116606: Barracuda Email Security Gateway authentication bypass (with CVE-2026-111560)
Why now: these ran in last week’s Watch as suspected; on Nov. 9 Barracuda confirmed exploitation and CISA added both to KEV on Nov. 10.
CVE-2026-116606 lets an unauthenticated attacker restore a crafted backup and rewrite a Barracuda Email Security Gateway’s global configuration. It affects ESG before 9.4.0.030 (patches BNSF-40425 and BNSF-40430), while companion CVE-2026-111560 also hits Load Balancer ADC, WAF, Web Security Gateway, Message Archiver and WAF Control Center. The first is an authentication bypass through an alternate path, the second a root command injection in the timezone field that needs admin rights. Together they form a chain: reach the admin interface, gain admin control, then run commands as root. The business impact is root on the box that handles an organization’s email.
Heads up: CVE-2026-116606 is CVSS v4.0 9.3 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) and CVE-2026-111560 is 8.6 (same, PR:H), both from Mandiant; Barracuda labels the 9.3 “High”. KEV: both added Nov. 10. EPSS has jumped to 10.9% (96th percentile) and 9.1% (95th). Exploitation is KNOWN: Barracuda says it found activity “affecting a small number of organizations” but hasn’t said which CVE was used or shared IOCs. A public checking tool reportedly appeared on GitHub Nov. 5 (secondary report, unverified). No named campaign or actor. Barracuda itself was breached Nov. 1 to 2 in an Artex-tool intrusion via an exposed cloud key, per SecurityWeek, but no source links that to these CVEs, so don’t conflate them. Access: remote, admin UI reachability required, no auth for 116606, no user interaction, automatable per CISA. Fix: patch; if automatic patching was off, apply manually and turn it back on, and confirm the patch IDs on the box because Mandiant’s and Barracuda’s version boundaries don’t match. Restrict the admin UI to internal networks as a mitigation, not a fix. Dates: reported to Barracuda in October per Mandiant; CVEs and advisory Nov. 2, coordinated. Scanning: none reported. Advisory: https://trust.barracuda.com/security/pre-authentication-authorization-bypass-command-injection
Sources: Barracuda, CISA, BleepingComputer, Mandiant MNDT-2026-0042, SecurityWeek.
CVE-2026-123158: OpenBSD OpenSSH authentication bypass (SSHole)
Why now: covered in full last week; since then CISA added it to KEV (Nov. 9) and GreyNoise has confirmed a growing number of successful intrusions.
SSHole lets an attacker log in over SSH with any password between 256 and 1,024 characters on certain accounts. It affects OpenSSH before 10.6p2 on Linux built with musl libc and without PAM, such as Alpine. The type is an authentication bypass rooted outside sshd, in how musl handles oversized passwords. An attacker needs SSH reachable with password authentication on and an account whose password field is *. The business impact is unauthenticated root on servers, containers and embedded gear.
Heads up: CVE-2026-123158 is CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). KEV: yes, added Nov. 9. EPSS is now 18.9% (97th percentile), up sharply from last week. Exploit is PUBLIC and GreyNoise calls it trivial. KNOWN campaign activity: as of Nov. 16, GreyNoise counts 45 confirmed post-exploitation sessions from 10 attacker IPs, including a cluster it calls GT10 that drops a Python runtime and “TAC Agent” (C2 tac[.]vpnla[.]org) with victims across Asia-Pacific and France. No APT or named actor. Remote, no auth, no user interaction, scriptable. Fix: OpenSSH 10.6p2 or your distro’s backport, then restart sshd; PasswordAuthentication no is a sufficient stopgap. glibc distros and UsePAM yes aren’t affected. Dates: found by Özgün Kültekin of Wakefield; fix and CVE Nov. 5; first public exploit about four hours later. Scanning: KNOWN, with GreyNoise logging over 98 million TCP/22 SYNs since Nov. 5. Advisory: https://www.openssh.org/releasenotes.html#10.6p2
Sources: OpenSSH, GreyNoise, CVE record, Alpine.
CVE-2026-125350: Google Chrome XML use-after-free
This is a memory-safety bug in Chrome’s XML handling that attackers are already using. It affects Chrome before 157.0.8103.50 and, per CISA, other Chromium-based browsers such as Edge and Opera until they ship the fix. The type is use-after-free (CWE-416), giving code execution inside the browser sandbox. An attacker reaches it by getting the victim to load a crafted web page. The business impact is a foothold on employee machines, usually as the first step in a chain with a sandbox escape.
Heads up: CVE-2026-125350 is CVSS 8.8 from CISA’s enrichment (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H); Chromium rates it High. KEV: yes, added Nov. 10. EPSS 0.96% (62nd percentile). Exploitation is KNOWN: Google says an exploit exists in the wild, making this Chrome’s eighth exploited zero-day of 2026. The exploit is PRIVATELY held; no credible public PoC. Campaigns and actors: not disclosed. Access: remote over the internet, needs a user to visit a page, no login; delivery can be automated through malicious or compromised sites. Fix: update to 157.0.8103.50/.51 and relaunch, and push the matching Edge and Opera updates; no workaround. The same release fixed a second XML use-after-free (CVE-2026-125346) not marked exploited. Dates: reportedly reported anonymously about three days before the fix; fix shipped Nov. 9; CVE published Nov. 10; Google is withholding bug details, standard for an exploited Chrome bug. Scanning: not applicable to a browser bug. Advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html
Sources: Chrome Releases, BleepingComputer, CISA, CVE record.
CVE-2026-114713: UnrealIRCd improper neutralization of delimiters
This bug lets any ordinary IRC user issue commands with the authority of the server itself. It affects UnrealIRCd 6.0.0 through 6.2.7 and is fixed in 6.2.7.1. The type is improper neutralization of delimiters (CWE-140): the labeled-response module echoes the IRCv3 “label” tag into replies without escaping it. An attacker just connects as a normal user to a network with two or more linked servers and smuggles server-to-server commands. The business impact is a hijacked chat network, where attackers can kill and ban users at will.
Heads up: CVE-2026-114713 is CVSS 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N); the maintainer calls it the most critical UnrealIRCd issue in 15 years. KEV: yes, added Nov. 13, federal deadline Nov. 16. EPSS 0.51% (44th percentile). Exploitation is KNOWN: maintainer Bram Matthys (Syzop) says attackers began exploiting it the day after the Nov. 7 fix. Public exploit code is reported in GitHub repositories. Campaigns, goals and actors: unknown. Access: remote over the internet, only an ordinary IRC connection needed, no user interaction, automatable per CISA; single-server setups aren’t exposed. Fix: upgrade to 6.2.7.1, or apply the no-restart hot-patch ./unrealircd hot-patch bundle-20261107 on every linked server (not available on Windows). Workaround: blacklist-module "labeled-response";. Review logs since Nov. 7 for KILL or GLINE actions no operator issued. Dates: found in an AI-assisted audit (reporter not disclosed); fix Nov. 7; CVE published Nov. 8; the maintainer shipped the fix and advisory himself. Scanning: none reported. Advisory: https://forums.unrealircd.org/viewtopic.php?t=9487
Sources: The Hacker News, CVE record, UnrealIRCd release notes, CISA.
CVE-2026-20320: Cisco BroadWorks XML external entity injection
Why now: patched Aug. 19, but CISA added it to KEV on Nov. 10. Cisco then updated its advisory to say it was exploited (Nov. 12) and walked that back the next day.
This flaw lets an attacker read data from Cisco BroadWorks, the platform carriers use to run hosted voice services. It affects the Application Delivery Platform, Application Server, Profile Server and Xtended Services Platform before RI.2026.07. The type is XML external entity (XXE) injection, because the OCI-P service resolves external entities by default. An unauthenticated attacker sends a crafted XML message to OCI-P. The business impact is leaked configuration and subscriber data from a telecom platform that often serves many downstream customers.
Heads up: CVE-2026-20320 is CVSS 7.5 from Cisco (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). KEV: yes, added Nov. 10. EPSS 0.98% (63rd percentile). Exploitation: KNOWN per CISA, but Cisco now says it has no direct evidence of active exploitation. No public PoC reported. Campaign: SUSPECTED. A secondary report summarizing SecurityWeek describes a Chinese-speaking actor hitting a European telecom and at least 13 downstream organizations, and the CVE record references Malbear Labs’ “Operation Snowball” write-up on an autonomous AI intrusion campaign; we haven’t verified either. Access: remote, no auth, no user interaction, automatable per CISA. Fix: Cisco says patching to RI.2026.07 is required and there are no workarounds; restricting OCI-P to trusted hosts and alerting on DOCTYPE/ENTITY declarations are reasonable mitigations, not fixes. Dates: credited to Sandesh M Gawai; advisory Aug. 19 through Cisco’s normal coordinated process; KEV Nov. 10. Scanning: none reported. Advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-bworks-xxe-uwUd7CEt
Sources: Cisco, CISA, Shattered, Malbear Labs.
CVE-2026-76964: SAP NetWeaver ICM memory corruption (with CVE-2026-89126, “ICM2Shell”)
These two maximum-severity bugs sit in the components that take web traffic into SAP systems. CVE-2026-76964 is in the Internet Communication Manager of SAP NetWeaver AS ABAP (kernels 7.53 through 9.20, SAP Note 3778530), and CVE-2026-89126 is in SAP Web Dispatcher and related kernels (SAP Note 3778556). Both are memory corruption, the second a heap-based buffer overflow. They’re reachable over the network without logging in, and the pair was reportedly demonstrated as a full unauthenticated remote code execution chain. The business impact is a takeover of the ERP systems that run finance, HR and supply chain.
Heads up: both are CVSS 10.0 Critical from SAP (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H). Not on KEV; EPSS 0.43% (38th percentile) each. Exploit: PRIVATE as far as is known. BleepingComputer reports them under the name ICM2Shell, and reporting credits Onapsis with handing SAP a working exploit; we couldn’t reach Onapsis’s own write-up. No exploitation, campaigns or actors reported, and CISA’s enrichment says exploitation: none. Access: remote over the internet wherever ICM or Web Dispatcher is exposed, no auth, no user interaction. Fix: apply SAP Notes 3778530 and 3778556 (patch levels are in the notes, which need an SAP login); no workaround verified. The same Patch Day fixed four more ICM/Web Dispatcher bugs, including CVE-2026-89119 (CSRF, 9.6), so patch the kernel as a set. Dates: discovery not disclosed; released on SAP Patch Day, Nov. 10, CVEs the same day; coordinated through SAP. Scanning: none reported yet, but a working exploit exists privately and internet-facing Web Dispatchers are common, so don’t wait for KEV. Advisory: https://support.sap.com/en/my-support/knowledge-base/security-notes-news/november-2026.html
Sources: SAP November 2026 Patch Day, BleepingComputer, CVE-2026-76964 record, CVE-2026-89126 record.
Hunt Lead candidates
- CVE-2026-90436 (N-central 4EverAble2Shell): concrete IOCs (request path and class name,
xvd.service,.xvdpaths, attacker IP, XMRig) from Huntback and BleepingComputer, and the victim pool is MSPs. - CVE-2026-123039 (Check Point DynamicCLI): Check Point Research documents the full chain with file paths for TSGA and TSProxy, plus vendor socket and log checks.
- CVE-2026-123158 (SSHole): GreyNoise publishes attacker IPs, session tags and the TAC Agent C2 for a live cluster.
- CVE-2026-102895 (GPUStack): one forged header is easy to detect in proxy logs, and attacker-created backends running reverse shells give a clear host signal.
CVE at a glance
- CVSS
- 9.8 Critical (v3.1)
- EPSS
- 1.1% chance of exploitation in the next 30 days (higher than 66.8% of CVEs)
- Exploited in the wild
- Not on CISA’s KEV list
- Public exploit
- Yes, reported in 1 GitHub repository
- CVSS
- 7.8 High (v3.1)
- EPSS
- 2.2% chance of exploitation in the next 30 days (higher than 82.7% of CVEs)
- Exploited in the wild
- Yes, on CISA’s KEV list since Nov 13, 2026
- Public exploit
- Yes, reported in 2 GitHub repositories
- CVSS
- 9.8 Critical (v3.1)
- EPSS
- 2.5% chance of exploitation in the next 30 days (higher than 84.7% of CVEs)
- Exploited in the wild
- Yes, on CISA’s KEV list since Nov 9, 2026
- Public exploit
- Yes, reported in 2 GitHub repositories
- CVSS
- 9.8 Critical (v3.1)
- EPSS
- 0.5% chance of exploitation in the next 30 days (higher than 44.4% of CVEs)
- Exploited in the wild
- Yes, on CISA’s KEV list since Nov 9, 2026
- Public exploit
- None reported in public exploit databases
- CVSS
- 9.8 Critical (v3.1)
- EPSS
- 0.5% chance of exploitation in the next 30 days (higher than 45.6% of CVEs)
- Exploited in the wild
- Yes, on CISA’s KEV list since Nov 9, 2026
- Public exploit
- Yes, reported in 1 GitHub repository
- CVSS
- 9.3 Critical (v4.0)
- EPSS
- 10.9% chance of exploitation in the next 30 days (higher than 95.9% of CVEs)
- Exploited in the wild
- Yes, on CISA’s KEV list since Nov 10, 2026
- Public exploit
- Yes, reported in a Nuclei template and 1 GitHub repository
Data from NVD, FIRST EPSS and CISA KEV, refreshed automatically. We report whether public exploit code exists but never link to it: fake proof-of-concepts that infect researchers are common.