November 2026 First-Week Patch Scorecard: Next.js, OpenSSH, WordPress, SonicWall and Plex on One Page (Checklist)
In the first week of November critical patches landed for Next.js, OpenSSH, WordPress, SonicWall and Plex, some already exploited. We collected the fixed versions, a priority order and a patch-tracking template for your team on one page.
In brief: The first week of November 2026 brought another stack of critical patches; this article collects, in one table, the versions we verified in primary or reliable news sources. First: internet-facing systems that are already being exploited: WordPress 7.1.4 (CVE-2026-119977, CISA KEV 3 November), OpenSSH 10.6p2 (SSHole, exploitation about 40 hours after the patch), SonicWall SonicOS 7.3.4-7013 / 8.2.3-8015 (CVE-2026-19868, CISA KEV 6 November) and Plex Media Server 1.43.3.10861 (Plex2Shell, QNAP NAS compromises). Then: Next.js 16.4.5 / 15.5.29 (3 November; seven flaws, one high) and Linux kernel updates. The PHP, Drupal, Node.js and Microsoft items from October's scorecard still stand; they should be done by now unless a newer version has appeared. This article is as of 9 November 2026; things may have changed.
Last updated: 9 November 2026
The patch table on one page
| Software | What happened? | Fixed versions | Status / priority | Detail |
|---|---|---|---|---|
| WordPress | CVE-2026-119977: race condition in the core upgrade process; unauthenticated code execution; CISA KEV 3 November; Wordfence blocked 13,095 attacks in 24 hours | 7.1.4 (28 October) | URGENT (internet-facing, exploited) | WordPress article |
| OpenSSH | “SSHole” CVE-2026-123158: password-authentication bypass on musl-based systems (Alpine, OpenWrt, Buildroot, Yocto); real exploitation about 40 hours after the patch | 10.6p2 (5 November) or turning off password authentication | URGENT (musl systems with SSH exposed) | SSHole article |
| SonicWall SonicOS | CVE-2026-19868: authentication/MFA bypass in the SAML-based SSL VPN; CISA KEV 6 November | Gen7: 7.3.4-7013; Gen8: 8.2.3-8015 | URGENT (SAML SSL VPN users; no workaround) | SonicWall article |
| Plex Media Server (QNAP NAS) | Plex2Shell chain (4 CVEs); CISA KEV 20 October; QNAP reported NAS compromises | 1.43.3.10861 | URGENT if internet-exposed; updating is not enough, a clean reinstall is advised | Plex2Shell article |
| Next.js | 3 November: 7 flaws (1 high cache disclosure, 6 medium) | 16.4.5, 15.5.29 | High (those using Cache Components, self-hosting, Edge routes); a cheap upgrade for everyone else | Next.js article |
| Linux kernel | OpenAI's pipeline built exploits for 948 local privilege-escalation flaws; patches reach distributions in stages | Your distribution's security updates | Medium-high (multi-tenant servers, CI, container nodes first) | Linux kernel article |
| AI coding assistant settings files | Settings files with passwords/keys in public repositories (Apiiro) | Not a patch: scan repositories, rotate secrets | High (any leaked secrets) | Settings files article |
Carry-overs from October: PHP2Shell (PHP 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35), Drupal (10.6.19 / 11.3.19 / 11.4.10), Node.js (26.12.1 / 24.22.1 / 22.23.4), Windows October updates. For detail see the October patch scorecard.
Prioritisation: in what order?
- Exploited, internet-facing flaws that bypass authentication or run code: WordPress 7.1.4, OpenSSH 10.6p2 (musl systems), SonicWall (SAML SSL VPN), Plex (if internet-exposed). Today.
- Components with lower exploitation likelihood but high impact: Next.js 16.4.5/15.5.29 (especially multi-tenant and self-hosted apps). This week, after testing in staging.
- Kernel and infrastructure updates: your distribution's kernel security updates and a reboot plan. Start this week.
- Secret hygiene: scan agent folders and repositories; rotate any secrets found before cleaning up.
- Compromise checks: for Plex/QNAP and OpenSSH, not just patching but looking for traces (unexpected keys, files, services).
- Unsupported versions: in addition to October's list, systems that can't receive updates (old WordPress, embedded devices with old OpenSSH).
This order is a suggestion; adjust it to your sector regulations and risk appetite. For the prioritisation logic see our Microsoft patch article and patch management plan.
Why so fast?
Two examples this week show the pace: for OpenSSH the proof of concept appeared about four hours after the patch and real exploitation about 40 hours later; for WordPress, the fix shipped on 28 October and the flaw was on the KEV list by 3 November. A “monthly patch day” may no longer be enough for critical internet-facing systems. The answer is not panic but routine: inventory, an owner, a time target and a staging environment.
Patch tracking template
Keep these columns in a simple spreadsheet:
| System | Owner | Software/version | Affected? | Patch date | Test | Secrets rotated? | Notes |
|---|---|---|---|---|---|---|---|
| E.g. Corporate site | Name Surname | WordPress 7.1.3 | Yes | 10 Nov | Login/form test | Not needed | Auto-updates were off; now on |
For each row, have a written answer to: who is responsible, which version are we on, when was it fixed, how was it tested?
10-point weekend checklist
- Are WordPress installs on 7.1.4 or later? Was the version verified?
- On musl-based systems (Alpine, OpenWrt, Buildroot, Yocto), is OpenSSH 10.6p2, or is password authentication off?
- Are SonicWall devices on 7.3.4-7013 / 8.2.3-8015, and were VPN logs reviewed?
- Is Plex Media Server 1.43.3.10861; if a Plex server was internet-exposed, was a clean reinstall considered?
- Is Next.js 16.4.5 / 15.5.29; if
use cacheis used, was the cache refreshed? - Are kernel security updates and reboots planned on Linux servers?
- Were repositories scanned for agent folders such as
.claude/and.cursor/, and were secrets found rotated? - Are the October items (PHP2Shell, Drupal, Node.js, Windows) complete?
- Were unsupported versions listed and migration dates written down?
- Does every system have a written patch owner and time target?
Maintenance with Aktaş Digital
In web applications and custom software we set up version tracking, patching and testing routines. To have your systems' current state reviewed, use our quote form. To clarify maintenance responsibilities see our maintenance and SLA guide. Related services: web applications.
Frequently Asked Questions
Do I have to patch everything at once?
No; follow the priority order above. Exploited, internet-facing systems first, the rest within this week or month after testing.
Does this table cover everything?
No; it covers only the items named here, based on verified sources. Follow the security advisories of the vendor of each piece of software you use.
How do I check for compromise after patching?
A patch does not remove payloads installed earlier. For Plex/QNAP and SSHole, look for unexpected keys, files and services; if in doubt, a clean reinstall and secret rotation are needed.
I don't use Next.js. Do I need this table?
The WordPress, SSH, VPN and Linux kernel items are independent of Next.js. Decide which rows concern you from your inventory.
An agency manages my software. What should I ask for?
Written confirmation for each row: version, patch date, test result and whether secrets were rotated.
Conclusion
The first week of November again showed that the time from patch to exploitation is measured in hours. Handle WordPress, OpenSSH, SonicWall and Plex first, Next.js and the kernel next; don't forget secrets and traces. The first step: copy this table and write an owner and a date next to every row.
