SecurityPatch management

Patch roundup, week of Nov 2: fix Linux and WS_FTP first, then work down the list

Patch and reboot Linux for CVE-2026-98432, and move any WS_FTP Server to a fixed version today. The rest of this week's fixes for Okta, Cisco, Snowflake, MuleSoft and plant systems can go in a normal window, and we've sorted them for you.

Cohash Security Practice November 2026 15 min read 12 chapters 3-question check
part 33 of 34 · Platform releases, explained from scratch
Week's advisories identity, network, data, OT Do we run it? match the inventory Can they reach it? no login first Patch today Linux, WS_FTP

the ideaOut of a long patch week, two jobs top the list for today.

after reading, you can
  • Sort a week of patches by reach and attacks instead of by score alone
  • Spot the fixes that need more than an install, like rotating secrets or a reboot
  • Plan around changes that bite: cached sign-ins, removed root CAs and manual upgrades

Most of this week's list can wait for a normal window, but two jobs can't. Patch Linux servers against CVE-2026-98432 and reboot them, and if you run Progress WS_FTP Server, upgrade it today. Then work down the rest in the order below.

in plain wordsTwo jobs today, section 02 this week

A patch week is a to-do list from your software vendors. Sort it before you start.

Every week, software companies publish fixes for holes they or outside researchers found. Most of those fixes can go into your next planned maintenance window. A few can't, because anyone on the internet could use the hole or attackers already are. We've sorted this week's fixes for you: what to do today, what to book this month, and what only needs a note on the calendar.

think of it like this

Picture the list a building manager gets after a safety inspection. A front door that opens for anyone gets fixed today. A worn lock on a staff cupboard goes on this month's work order. A notice that the alarm company is changing its visit schedule goes on the calendar. Doing them in the wrong order is how the front door stays open.

who should care
  • IT and security leads
  • Identity and PAM admins
  • Linux and network teams
  • Data and DevOps engineers
  • Plant and OT engineers
  • Owners whose provider patches for them
chapter 01

Why it matters to you

The two items at the top share a problem: nobody needs a password to start. The Linux flaw sits in the code that handles ordinary TCP connections, so it touches a huge share of servers. WS_FTP is a much smaller product, but a file transfer server often sits at the edge of the network, and this flaw can hand over admin credentials.

It's also a week where the scores mislead. A 10.0 in WS_FTP and a 9.9 in Dameware look like neighbours on a spreadsheet, yet Dameware's needs a login and WS_FTP's doesn't. Zyxel's switch flaw scores lower than both, and of the three it's the only one with a report of real attacks.

10.0WS_FTP Server flaw that can expose admin credentials with no login
9.8Linux kernel IPv4 TCP flaw, CVE-2026-98432
Nov 10SAP patch day and CISA's federal due date for Brotli
Nov 30BeyondTrust Remote Support and PRA 24.3 lose support
how it worksSort the week first, then patch in that orderUse the same triage every week. Start with what you actually run, then ask who can reach it and if anyone's attacking it yet.
  1. 01 Do we run it?

    Check each product and version against your inventory. If that takes more than a few minutes, the inventory is your first gap.

  2. 02 Can they reach it?

    No login and reachable from the internet goes to the top. A flaw that needs an admin account or a spot on your local network drops down.

  3. 03 Is it being attacked?

    Look at CISA's list, the vendor's page and national cyber centres. Any one of them reporting attacks moves the item up.

  4. 04 Patch and confirm

    Install the fix, then prove it took. A kernel update does nothing until the server reboots into it.

chapter 02

Fix these first

Linux kernel CVE-2026-98432. Red Hat rates this IPv4 TCP flaw Critical and started shipping RHEL fixes on November 1. Patch your distribution's kernel and reboot, because the old kernel keeps running until you do. Here's who has a fix and what the stopgap filter misses.

Progress WS_FTP Server. On this Windows file transfer server, CVE-2026-84295 (10.0) lets someone with no login read sensitive data, and that includes admin credentials. Fourteen more flaws came with it. Canada's Cyber Centre names 2025.0.3 and 2024.0.6, but most of the bugs stay open until 2025.0.4 or 2024.0.7, so we'd skip straight to those.

Nobody has reported attacks on WS_FTP so far, and it isn't on CISA's list as of the November 4 catalog. We'd still patch today, because nobody needs a login to try it and the credentials at stake belong to the admin.

Delinea Secret Server, self-hosted. If you missed it, Delinea rescored a login bypass to 9.9, and version 12.2.7 is affected too. Our Secret Server post covers who needs 12.3.000002 and what to look for in your logs.

Rails Active Storage. Rails apps can let a stranger write files on the server (9.8) when three things line up: they accept uploads from untrusted users, they process them with ImageMagickdefinitionSoftware that web apps often call when someone uploads a picture. It can do far more than resize, which is where the trouble starts., and ImageMagick's policy doesn't already block the coders involved. Debian's and Ubuntu's packaged policies don't. Just attaching the upload is enough. Upgrade to 8.1.4.1 or 8.0.5.2, and if you use the mini_magick processor you also need mini_magick 5.1 or later or the app fails at boot.

Here's the part teams miss. If your attachments live on the Disk service, patching isn't the end of the job: the Rails team tells you to change secret_key_base, the master key and every credential the app can read. PDF rendering can also break, because the new policy blocks Ghostscript until you allow it again in the host's policy.xml. Only 8.0 and 8.1 get these patches, so older apps have to copy the policy rules into ImageMagick's system policy or move up.

Barracuda Email Security Gateway. Barracuda changed its advisory on November 5, so re-check it if you triaged this on Monday. CVE-2026-116606 (9.3) was first listed as needing admin access and now reads as no authentication, as long as the attacker can reach the admin interface. Chained with command injection CVE-2026-111560 (8.6), it ends in root. Only ESG has the first flaw. ADC, Message Archiver, WAF, WAF Control Center and Web Security Gateway have only the second, which needs an admin login.

Zyxel GS1900 switches. Canada's Cyber Centre cites open-source reporting that CVE-2026-107441 is being exploited. Zyxel doesn't mention attacks, and it isn't on CISA's list as of the November 4 catalog. Anyone on the same network segment can use it without a login (8.8). Go and check the firmware, because Zyxel only patched models still inside their support period.

chapter 03

Identity and privileged access

fixedWatchGuard AuthPoint Gateway 7.6.0

This MFA gateway has four flaws, and the worst scores 9.2. On LDAP or AD setups, someone on the network can knock out authentication and delete the directory sync settings without logging in. WatchGuard knows of no attacks so far.

fixedOkta Access Gateway 2026.45.0

Okta only says it has security enhancements and names no CVE. Put it in your next window anyway, since that's all the detail Okta's notes give.

changedOkta agents

On-Prem MFA agent 1.8.8 has security enhancements. Provisioning Agent 3.3.2 removes root CAs Okta no longer trusts, so test any connector whose target chains to one of those roots.

fixedRSA Authentication Manager 8.9 Patch 5

We're catching up on this one, since the advisory is five weeks old. RSA rates it Critical and strongly recommends you apply it now. Do the Web-Tier Patch 5 as well.

fixedCisco ISE and ISE-PIC

CVE-2026-20241 (5.3) lets someone with no login obtain an endpoint identity certificate. The fixes were also part of Cisco's September hardening release, so you may already have them.

fixedSolarWinds Dameware 2026.3.1

Command injection CVE-2026-28336 scores 9.9 and can compromise the host being remotely controlled, but it needs a login. Remote admin tools reach everything, so don't leave this one long.

fixedBeyondTrust Password Safe

If you installed Cloud Resource Brokers yourself, they still need the fix for Brotli CVE-2026-111497, and six broker builds carry it. BeyondInsight 26.3.1 also moves its bundled OpenSSL to 3.5.9.

newBeyondTrust RS and PRA 26.3.1

Both releases came out on November 3, and appliance Base 8.4.0 now updates clusters as a unit. Teams still on 24.3 have a harder job.

fixedHashiCorp Boundary

A user who can manage credential stores can make the controller fetch internal addresses, cloud metadata services among them. Vault itself isn't the flawed product. Fixed in Enterprise 1.0.2 and 0.21.6.

BeyondTrust customers on 24.3 should read our end-of-support post before the end of the month, since there's no one-step route to 26.x. RSA customers planning Patch 5 can fold it into the move to 8.9 if they haven't made it yet. If you need extra hands, see how we staff Okta and BeyondTrust work.

chapter 04

Network, developer and business platforms

OpenSSH 10.6p2. On Linux builds that use musldefinitionSome Linux systems use this small C library where most use glibc. You'll usually run into it on Alpine Linux. libc with PAM turned off, some account setups accept any password between 256 and 1024 characters (CVE-2026-123158, 8.1). Most glibc servers aren't in that group. Look at containers and small appliances instead, Alpine being the usual musl base. The CVE record points to public exploit code and OpenSSH calls the fix critical, so affected hosts can't wait for the next release.

The release notes carry a warning worth repeating to your team. OpenSSH says bugs found with AI tools are being found again independently by other researchers, so it will ship fixes more often for now. If your SSH updates wait for a twice-yearly image rebuild, that cadence is starting to look slow.

GitHub Enterprise Server. Someone with an account and SSH access can run commands as the Git service and read its secrets, which is CVE-2026-104608, though they'd need memory offsets for your exact build and a failed try kills the service. In the second bug, CVE-2026-15343, code already running in a Dependabot container can write workflow files if the installation has workflows: write. GitHub says its first fix for that was incomplete, so upgrade again even if you patched it before.

WatchGuard Fireware OS. A Firebox set up with an Active Directory auth server can be hit by whoever controls or intercepts traffic to that server (CVE-2026-112710, 9.2). WatchGuard knows of no attacks. It's a backfill from last week, so check you've got it.

Cisco. UCS Central has a remote code execution flaw for logged-in users (7.6), and Unified CM has a cross-site scripting flaw that needs someone to click a link (6.1). Finesse, used in contact centers, has a server-side request forgery flaw with a public write-up, and Packaged and Unified CCE customers have to upgrade the Finesse component themselves. None of the Cisco items has a workaround, and Cisco knows of no malicious use.

ServiceNow. Brazil Patch 2 arrived on November 5 with 348 fixes, some of them for security problems. The details sit in KB3228372, which we couldn't read, so we won't guess at severity. From last week's batch, CVE-2026-103094 is the one to look at: it could leave a user's plaintext password in a system table. Our ServiceNow page has more on the platform.

MuleSoft. This is the easy one to miss, because nothing happens by itself this month. CloudHub and CloudHub 2.0 paused automatic patching for the November cycle, so apps only get 4.13.2, 4.12.6, 4.9.24 or 4.6.37 if someone upgrades them by hand. Put a name next to that job.

IBM Sterling B2B Integrator. A protocol downgrade flaw (CVE-2026-18668, 6.5) is fixed in 6.2.1.3 and 6.2.2.2. UiPath Orchestrator: job.created webhooks now always send source fields as names, so update any integration that expects numbers. InterSystems IRIS for Health: CVE-2026-111594 gets no product fix. You have to set the superserver to require TLS, because the "Enabled" setting still lets clients connect without it.

chapter 05

Data tools, and the eMudhra certificate fallout

Two Snowflake driver updates will produce the same help desk call. JDBC 4.4.1 is a real security fix: tokens could collide when one identity signs in to more than one account or role. Go driver 2.4.0 moves the token cache. After either upgrade, people using browser SSO, MFA or OAuth with cached tokens have to sign in once more, so warn them first and check any scheduled job that counts on a cached token.

On the dbt side, 2.0.11 hardens credential redaction in logged Databricks SQL and locks down the DuckDB database behind checks and dbt show. It also renames --run-cache-mode to --state-mode, and the old flag only survives as a deprecated alias, so change your CI scripts while you're there. dbt-core 1.11.17 moves git credentials for dbt deps into a credential helper. dbt doesn't label that a vulnerability fix, though it's still a good change. See our dbt page for version notes.

Smaller client updates: SnowSQL 1.5.4 tightens signature checks on auto-upgrade downloads, and Snowflake CLI 3.32.1 lets snow dbt execute run check and clone. Databricks' legacy Simba JDBC 2.8.6 updates lz4-java, Jackson and libthrift.

The eMudhra certificate compromise keeps rippling out, and this is where it can break things. Terraform Enterprise 2.1.0 and 2.1.1 both reject the eight compromised intermediates and drop two whole roots from the bundle: connections to hosts chaining to emSign Root TLS CA G3 or Comodo AAA Certificate Services will fail. Search your VCS, registry and proxy certificates for those chains before you upgrade. If you're already on 2.1.0, you've got this change now.

PTC lists Creo+, Creo Parametric 10.0 to 13.4 and Windchill Workgroup Manager as impacted, with steps in a support article. GitLab removed trust in its 19.5.3 release and the matching backports, and self-hosted Runner and AI Gateway need their own upgrades. Our Java and eMudhra post explains the background.

chapter 06

Plant and OT systems

PHP2Shell has now reached industrial products. CISA lists the PHP flaws as exploited, but that describes the bugs in general and nobody has said these products were attacked. Our PHP2Shell post has the full story, and our OT security page has more on these networks.

tableRecent industrial advisories. Patch in the next planned outage unless the system is reachable from outside the plant network
ProductWhat's wrongFix
WAGO CC100, Edge Controller, PFC100/200 G2, PFC300, TP600, WP400PHP2Shell, when the built-in web server is onFirmware 4.10.4 (FW32). FW31 users install the IPK security patch until then
Festo Didactic FactoryViews and MES4PHP2Shell in the bundled web stackFactoryViews 1.12.2. No fix for MES4 with xampp, so use the php.ini settings and firewall rules
Welotec SMART EMS up to 3.5.3PHP2Shell, no login needed3.5.4 or later
Mettler Toledo OCTO Image ServerPHP2Shell. The vendor rates the risk low on internal networksPHP 8.2.35
Subnet PowerSYSTEM CenterLow-privileged users reach admin resources, plus SQL injection (9.0)Upgrade to 2026 Update 1.1, or see CISA ICSA-26-307-01 for older lines
WAGO controllers (CODESYS)Unauthenticated denial of service (7.5) and code run from a crafted project file (7.8)Firmware 4.10.0
Welotec TK100 and TK500 routersCommand injection for high-privileged users (7.2)TK100 3.5.116, TK500-v2 1.0.124, TK500-v3 1.0.123

MES4 is the awkward one. Festo says older deployments run PHP up to 7.3, which no longer gets patches, and one of its suggested Apache settings carries a significant performance cost. Plan that system's replacement now. A firewall rule that only lets the HMI panels of manual workstations talk to it is a stopgap and nothing more.

chapter 07

The main fixed versions in one table

tableMain fixed versions for the week of November 2. Scores come from the vendor or CVE record, and n/a means we found none
ProductIssueScoreInstall
Linux kernelCVE-2026-984329.8Your distribution's kernel update, then reboot
Progress WS_FTP ServerCVE-2026-84295 and 14 more10.02025.0.4 or 2024.0.7
Delinea Secret Server (on-prem)CVE-2026-1158299.912.3.000002
Rails Active StorageGHSA-f3w6-w445-fwh99.88.1.4.1 or 8.0.5.2
Barracuda ESGCVE-2026-116606, CVE-2026-1115609.39.4.0.030 or patches BNSF-40425, BNSF-40430
Zyxel GS1900CVE-2026-1074418.82.90(xxxx.3)C0 for your model
WatchGuard AuthPoint GatewayCVE-2026-121639 and 3 more9.27.6.0
WatchGuard Fireware OSCVE-2026-1127109.22026.4, 12.12.4, or 12.5.22 on T15/T35
SolarWinds DamewareCVE-2026-28336 and 2 more9.92026.3.1
OpenSSH (musl, no PAM)CVE-2026-1231588.110.6p2
GitHub Enterprise ServerCVE-2026-104608, CVE-2026-15343High3.22.3, 3.21.8, 3.20.10, 3.19.14
Cisco UCS CentralCVE-2026-765067.62.1(2c). 2.0 and earlier migrate
Cisco ISE and ISE-PICCVE-2026-202415.33.1 P12, 3.2 P11, 3.3 P12, 3.4 P7, 3.5 P4 (ISE only)
Cisco Unified CMCVE-2026-764196.115SU5. Release 14 migrates
Cisco Finesse, Unified CCXCVE-2026-203627.2Finesse 15.0(1) SU2 ES1, CCX 15.0(1) SU1
HashiCorp BoundaryCVE-2026-133038.7Enterprise 1.0.2 or 0.21.6
IBM Sterling B2B IntegratorCVE-2026-186686.56.2.1.3 or 6.2.2.2
RSA Authentication ManagerRSA-2026-17Critical (RSA)8.9 Patch 5 and Web-Tier Patch 5
Okta Access GatewaySecurity enhancementsn/a2026.45.0
Okta agentsSecurity enhancements, root CA removaln/aMFA agent 1.8.8, Provisioning Agent 3.3.2
ServiceNowKB3228372Not statedBrazil Patch 2
Snowflake JDBCToken-cache key collisionsn/a4.4.1
Terraform EnterpriseCVE-2026-111943n/a2.1.1
MuleSoft runtimeNovember patchesn/a4.13.2, 4.12.6, 4.9.24 LTS, 4.6.37 LTS

What's coming next

  1. Nov 10
    SAP patch day, Brotli due

    SAP's monthly notes come out on the day CISA's federal due date for Brotli CVE-2026-111497 falls. If the same team handles both, they'll want that day clear.

  2. Nov 12
    Oracle pre-release notice

    Oracle publishes its heads-up the Thursday before each patch update, which gives you time to book the window.

  3. Nov 17
    Oracle Critical Security Patch Update

    Oracle now fills the months between its quarterly updates with these, so don't assume January is next.

  4. Nov 30
    BeyondTrust 24.3 support ends

    Anyone still on Remote Support or Privileged Remote Access 24.3 runs out of support here. There's no one-step upgrade, so start early.

  5. Dec 1
    CloudHub December release

    Automatic patching comes back, with sandbox updates on December 15 to 19 and production on December 20 and 21.

chapter 08

What to do now

What to do now, by who you are

Business ownertoday
  • Ask IT or your provider two things: have the Linux servers been patched and rebooted, and do we run WS_FTP?
  • Ask for it in writing if a provider runs your servers. A yes with a date is what you want.
  • If you have Zyxel GS1900 switches in an office, ask whoever looks after them to check the firmware.
IT and operationsthis week
  • Today: patch and reboot Linux, then do WS_FTP. Barracuda ESG and Zyxel come right after.
  • Upgrade AuthPoint Gateway, Dameware and Fireware, and check the admin interfaces aren't open to the internet.
  • Put one person's name on the MuleSoft upgrades. Nothing happens on its own this month.
  • Find every Password Safe Resource Broker you installed yourself. Those don't update for you.
Developers and data teamsthis week
  • Upgrade Rails Active Storage. On the Disk service, rotate your secrets too.
  • Rebuild musl-based images with OpenSSH 10.6p2 if they run sshd without PAM.
  • Warn users before rolling out Snowflake JDBC 4.4.1 or Go 2.4.0, because cached sign-ins stop working.
  • Change --run-cache-mode to --state-mode in dbt CI scripts, and fix any UiPath webhook consumers.
Security teamthis week
  • If WS_FTP faced the internet, assume someone could have read the admin credentials. Rotate them.
  • Search for certificates chaining to emSign Root TLS CA G3 or Comodo AAA before Terraform Enterprise 2.1.x goes in.
  • Re-check Barracuda and Zyxel against CISA's list next week. Both could move.
check-versions (example commands)example output
# We made these versions up, so yours will look different. It's example output, and you should only run it on systems you own.
$ uname -r
5.14.0-570.el9.x86_64
# Compare this with your distribution's fixed kernel. If the package is new and this is old, you still need the reboot.
$ ssh -V
OpenSSH_10.6p1
$ ldd /usr/sbin/sshd | grep -E 'musl|pam'
/lib/ld-musl-x86_64.so.1
# musl shows up and pam doesn't: move this host to 10.6p2.
$ bundle list
  * activestorage (8.0.5.1)
  * mini_magick (4.13.2)
# Needs activestorage 8.0.5.2 and, on the mini_magick processor, mini_magick 5.1 or later.
chapter 09

Harden so the next one hurts less

Four habits that make every patch week shorter

  1. 01
    Keep admin interfaces off the internet

    Barracuda's flaw only works if an attacker can reach the admin interface, and Barracuda itself says private ones are less exposed. Put these consoles behind a VPN or jump host, and do the same for WS_FTP's web admin.

  2. 02
    Check that the reboot happened

    Report on the running kernel, since the installed package tells you nothing about what's in memory. A weekly list of servers where the two differ will find the ones nobody rebooted.

  3. 03
    Re-read advisories you've already triaged

    Barracuda changed its authentication field days after publishing, and Fortinet still lists many products as under investigation for the Linux flaw. Set a reminder to look again at anything you marked as low risk.

  4. 04
    Know what you bundle

    PHP inside controller firmware, Brotli inside a broker's .NET runtime, certificates inside a Terraform image. Ask vendors for a component list, because a scanner might not see inside these packages.

chapter 10

If you've been breached

If someone's already in, here's the order we'd work in

This applies most to WS_FTP, Rails apps, Barracuda ESG and the PHP2Shell systems. Contain first, then look, then clean up.

  1. 01Containfirst hour
    • Take the system off the internet or behind a VPN-only rule. Leave it powered on so memory and logs survive.
    • On WS_FTP, stop outside access to the web admin and pause automated transfer jobs until you know which accounts are clean.
  2. 02Investigatefirst day
    • On WS_FTP, review admin sign-ins, new accounts and file activity going back to before the fix came out.
    • On Rails apps, look for files that shouldn't be there and for uploads with odd image types.
    • On Barracuda ESG, check the running configuration against a backup you trust. The flaw works by restoring a crafted one.
  3. 03Removefirst days
    • Rebuild anything where an attacker may have run commands. Don't try to clean a device that gave up root.
    • Rotate every credential the system held: WS_FTP admin and user passwords, Rails secret_key_base and master key, cloud and database keys.
  4. 04Recoverfirst week
    • Bring systems back on the fixed version, behind the access rules from section 09.
    • Watch the rotated accounts closely for the next few weeks. Attackers often come back with whatever they copied.
  5. 05Report and learnas required
    • Call your lawyer and your cyber insurer early. Files on a transfer server often belong to customers, which can start notification clocks.
    • Write down how you found out and how long patching took. Then go fix whichever step was slowest.
chapter 11

What this could look like

We made these three setups up, but you'll probably recognise one

01 Attacker 02 WS_FTP admin internet-facing 03 Upgrade andVPN 04 Supplierfiles
scenario 01High risk
A small manufacturer swapping files with suppliers
the setup
A Windows server runs WS_FTP so suppliers can drop drawings and orders. The web admin page is reachable from the internet because that's how it was set up years ago.
what happens
Someone reads the admin credentials through CVE-2026-84295 and never has to log in. From there they've got each supplier's account, and the files that came with it.
what to do
Upgrade to 2025.0.4, move the web admin behind a VPN, rotate admin and supplier passwords, and check recent file activity.
01 Craftedupload 02 ImageMagick 03 Fixed ActiveStorage 04 App secrets
scenario 02High risk
A software company on Rails with customer uploads
the setup
An older Rails app still uses ImageMagick for profile pictures and stores attachments on the Disk service. Any signed-up customer can upload a file.
what happens
A crafted upload lets someone read files the app can read, secret_key_base and cloud keys among them. Patching alone doesn't take those secrets back.
what to do
Do the upgrade first, Active Storage and mini_magick together. Then someone has to change secret_key_base, the master key and each credential in the app's config, because the old ones might be out.
01 Paused auto-patch 02 Named owner 03 Stale runtime
scenario 03Medium risk
A mid-size firm with MuleSoft and Snowflake
the setup
Integrations run on CloudHub 2.0, which has always patched itself. Analysts use BI tools over Snowflake JDBC with browser SSO.
what happens
November's runtime never arrives because nobody knows it's manual this month. A driver upgrade then logs out every analyst at the start of month-end close.
what to do
Name someone to run the Mule upgrades, and schedule the JDBC rollout with a note to users about signing in once more.
chapter 12

How Cohash helps

Many of the platforms on this list sit in our cybersecurity and identity practice, and you can ask us about any item. If you aren't sure what you run, start with an assessment. For a specific platform, look at Delinea, Okta or Snowflake. Last week's list is in the previous roundup.

key takeaways

What to take from this

  1. 01

    Patch Linux for CVE-2026-98432 and reboot. The new kernel doesn't protect you until it's the one running.

  2. 02

    Take WS_FTP Server to 2025.0.4 or 2024.0.7. Nothing lower closes all fifteen flaws.

  3. 03

    After the Rails fix, rotate secrets if attachments sit on the Disk service. The patch can't recall anything already read.

  4. 04

    Give the November MuleSoft upgrade to a named person, because CloudHub won't do it this month.

  5. 05

    Warn Snowflake users before JDBC 4.4.1 or Go 2.4.0, since cached sign-ins stop working once.

  6. 06

    Search for the two removed root CAs before you install Terraform Enterprise 2.1.0 or 2.1.1.

fact-checked November 2026 against vendor and official documentation · where to go next
  1. How Cohash delivers Okta: scope, roles and architecture
  2. How Cohash delivers BeyondTrust: scope, roles and architecture
  3. How Cohash delivers RSA SecurID: scope, roles and architecture
  4. Hire vetted Okta engineers
  5. Identity and access management
  6. Book a 30-minute working session with a senior engineer
01What's the most urgent patch this week?

Start with the Linux kernel update for CVE-2026-98432, since an attacker doesn't need a login and you've probably got a lot of those servers. If you run WS_FTP Server, treat it the same. And reboot, or the Linux fix isn't doing anything.

02Our provider manages the servers. Is any of this still our problem?

Yes, ask them. Have them confirm in writing that Linux hosts were patched and rebooted, and that any WS_FTP server is on 2025.0.4 or 2024.0.7. Keep the reply with your audit records.

03Is WS_FTP being attacked?

We haven't found a report of it, and it isn't on CISA's list as of the November 4 catalog. That can change fast with a flaw that exposes admin credentials, so we'd patch now and keep watching.

04Does the OpenSSH password bypass touch my servers? We run plenty of Linux.

Only if sshd runs on Linux with musl libc and PAM turned off, and even then only for some account setups. Most mainstream glibc servers aren't in that group. Check your Alpine-based containers and small appliances.

05My Snowflake users got asked to sign in again. Did something break?

JDBC 4.4.1 and Go driver 2.4.0 store cached tokens in a new way, and tokens saved by older versions aren't reused. People on browser SSO, MFA or OAuth sign in once more and it settles down.

06Terraform Enterprise can't connect since we upgraded it. What happened?

Versions 2.1.0 and 2.1.1 dropped emSign Root TLS CA G3 and Comodo AAA Certificate Services from its trusted list. Any host chaining to those roots now fails verification, so that host needs a certificate from another CA.

07My Barracuda admin page is private. Do I still need to bother?

You're less exposed, and Barracuda says so. You still want the patch, because anyone who gets onto that internal network can reach the page, and the chain ends in root on ESG.

up next in this track

Keep the thread going.

What shipped, what changed underneath, and what it means for your upgrade.

  1. 01HashiCorp Vault 2.2 explained: TPM login, post-quantum PKI and the October fixes
  2. 02Upgrading to SailPoint IdentityIQ 9.0: what breaks and what to fix first
  3. 03Terraform 1.17 explained: what's new, who it touches and how we'd upgrade
  4. 04BeyondTrust Remote Support zero-day: patch it, then check who got in
  5. 05Patch PHP and Node.js this week: what broke and who's exposed
  6. 06OpenShift support dates through 2027: which clusters run out first and how to plan the upgrades
  7. 07Oracle's October security patches: what to fix first in EBS, PeopleSoft and Access Manager
  8. 08Oracle Java drops four root certificates over eMudhra: patch, then test what breaks
  9. 09Delinea Secret Server auth bypass: why the FIDO2 hotfix isn't enough
  10. 10IBM Verify Access flaws let attackers run code without a login: patch to 11.0.3.2
  11. 11Foundry Workflows retire on December 1. We'd start moving yours to Agent Framework now
  12. 12Vertex AI is retiring text-embedding-005 and three other embedding models: how to re-embed before search breaks
  13. 13dbt drops v1.3 to v1.7 from its platform on January 31, 2027: get pinned jobs onto a release track before they're deleted
  14. 14Brotli CVE-2026-111497 is now on CISA's exploited list, and you probably run more copies than you think
  15. 15Auth0 moved the Rules and Hooks deadline: Hooks stop on 30 April 2027, Rules on 31 January 2028
  16. 16Still on Okta Classic Engine? Three features stop working on March 5, 2027, and two of them block the upgrade
  17. 17Patched GitLab, still exposed: the CI regex bug CISA lists as exploited, and the Ruby step people miss
  18. 18Patched Ivanti Connect Secure in October? Two more exploited bugs, and the AD cleanup
  19. 19Patch roundup, week of Oct 26: upgrade Secret Server today, then work down the list
  20. 20UiPath 2023.10 support has run out and 2024.10 is next. What we'd upgrade first
  21. 21Password Safe 24.3 runs out of support in December, and 26.3 is still one upgrade away
  22. 22Upgrade Entra Connect Sync before April 2027 and move users off Microsoft's SMS codes
  23. 23Chrome drops XSLT on 17 November. What breaks in InterSystems, and the fix for your version
  24. 24Agent Builder, Evals and saved prompts shut on 30 November. Here's what to pull out first
  25. 25BeyondTrust Remote Support and PRA 24.3 lose support in November, and there's no one-step upgrade
  26. 26OpenShift 4.19 is running out of support. Do you park on 4.22 or keep going to 5.0?
  27. 27Terraform Enterprise 2.1 moves VCS ingress into your agents. What to change before October 2027
  28. 28Mule 4.12 Edge leaves standard support this month. Upgrade to 4.13 before CloudHub does it for you
  29. 29RSA SecurID primary support ends in stages from December. Here's how you get to 8.9
  30. 30Delinea Secret Server login bypass: why 12.2.7 won't save you from this 9.9
  31. 31Entra password reset won't take directory phone numbers from February 2027. Who gets stuck?
  32. 32Linux kernel CVE-2026-98432: why switching off MPTCP won't save you, and what to patch
  33. 33Patch roundup, week of Nov 2: fix Linux and WS_FTP first, then work down the list
  34. 34SonicWall's SSL VPN bug lets a valid password skip SAML and your MFA
all learning tracks →
01 VPN loginpage 02 Alternatepassword 03 SAMLskipped 04 No MFAprompt 05 Inside thenetwork
Security · 15 minSonicWall's SSL VPN bug lets a valid password skip SAML and your MFA

A password for another login skips SAML. MFA never asks.

read next
next step

Tell us what you're running. We'll tell you what we'd do first.

A 30-minute working session with a senior engineer. No slides.

useful to bring
  • The platform and the version you're on
  • Where you need to get to, and by when
  • What's custom: rules, plugins, integrations
  • Any audit finding or deadline driving it