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.
part 33 of 34 · Platform releases, explained from scratchthe 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.
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.
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.
- 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
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.
-
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.
-
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.
-
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.
-
04 Patch and confirm
Install the fix, then prove it took. A kernel update does nothing until the server reboots into it.
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.
Identity and privileged access
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
| Product | What's wrong | Fix |
|---|---|---|
| WAGO CC100, Edge Controller, PFC100/200 G2, PFC300, TP600, WP400 | PHP2Shell, when the built-in web server is on | Firmware 4.10.4 (FW32). FW31 users install the IPK security patch until then |
| Festo Didactic FactoryViews and MES4 | PHP2Shell in the bundled web stack | FactoryViews 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.3 | PHP2Shell, no login needed | 3.5.4 or later |
| Mettler Toledo OCTO Image Server | PHP2Shell. The vendor rates the risk low on internal networks | PHP 8.2.35 |
| Subnet PowerSYSTEM Center | Low-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 routers | Command 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.
The main fixed versions in one table
| Product | Issue | Score | Install |
|---|---|---|---|
| Linux kernel | CVE-2026-98432 | 9.8 | Your distribution's kernel update, then reboot |
| Progress WS_FTP Server | CVE-2026-84295 and 14 more | 10.0 | 2025.0.4 or 2024.0.7 |
| Delinea Secret Server (on-prem) | CVE-2026-115829 | 9.9 | 12.3.000002 |
| Rails Active Storage | GHSA-f3w6-w445-fwh9 | 9.8 | 8.1.4.1 or 8.0.5.2 |
| Barracuda ESG | CVE-2026-116606, CVE-2026-111560 | 9.3 | 9.4.0.030 or patches BNSF-40425, BNSF-40430 |
| Zyxel GS1900 | CVE-2026-107441 | 8.8 | 2.90(xxxx.3)C0 for your model |
| WatchGuard AuthPoint Gateway | CVE-2026-121639 and 3 more | 9.2 | 7.6.0 |
| WatchGuard Fireware OS | CVE-2026-112710 | 9.2 | 2026.4, 12.12.4, or 12.5.22 on T15/T35 |
| SolarWinds Dameware | CVE-2026-28336 and 2 more | 9.9 | 2026.3.1 |
| OpenSSH (musl, no PAM) | CVE-2026-123158 | 8.1 | 10.6p2 |
| GitHub Enterprise Server | CVE-2026-104608, CVE-2026-15343 | High | 3.22.3, 3.21.8, 3.20.10, 3.19.14 |
| Cisco UCS Central | CVE-2026-76506 | 7.6 | 2.1(2c). 2.0 and earlier migrate |
| Cisco ISE and ISE-PIC | CVE-2026-20241 | 5.3 | 3.1 P12, 3.2 P11, 3.3 P12, 3.4 P7, 3.5 P4 (ISE only) |
| Cisco Unified CM | CVE-2026-76419 | 6.1 | 15SU5. Release 14 migrates |
| Cisco Finesse, Unified CCX | CVE-2026-20362 | 7.2 | Finesse 15.0(1) SU2 ES1, CCX 15.0(1) SU1 |
| HashiCorp Boundary | CVE-2026-13303 | 8.7 | Enterprise 1.0.2 or 0.21.6 |
| IBM Sterling B2B Integrator | CVE-2026-18668 | 6.5 | 6.2.1.3 or 6.2.2.2 |
| RSA Authentication Manager | RSA-2026-17 | Critical (RSA) | 8.9 Patch 5 and Web-Tier Patch 5 |
| Okta Access Gateway | Security enhancements | n/a | 2026.45.0 |
| Okta agents | Security enhancements, root CA removal | n/a | MFA agent 1.8.8, Provisioning Agent 3.3.2 |
| ServiceNow | KB3228372 | Not stated | Brazil Patch 2 |
| Snowflake JDBC | Token-cache key collisions | n/a | 4.4.1 |
| Terraform Enterprise | CVE-2026-111943 | n/a | 2.1.1 |
| MuleSoft runtime | November patches | n/a | 4.13.2, 4.12.6, 4.9.24 LTS, 4.6.37 LTS |
What's coming next
- Nov 10SAP 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.
- Nov 12Oracle pre-release notice
Oracle publishes its heads-up the Thursday before each patch update, which gives you time to book the window.
- Nov 17Oracle Critical Security Patch Update
Oracle now fills the months between its quarterly updates with these, so don't assume January is next.
- Nov 30BeyondTrust 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.
- Dec 1CloudHub December release
Automatic patching comes back, with sandbox updates on December 15 to 19 and production on December 20 and 21.
What to do now
What to do now, by who you are
- 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.
- 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.
- 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.
- 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.
# 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.
Harden so the next one hurts less
Four habits that make every patch week shorter
- 01Keep 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.
- 02Check 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.
- 03Re-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.
- 04Know 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.
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.
- 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.
- 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.
- 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.
- 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.
- 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.
What this could look like
We made these three setups up, but you'll probably recognise one
- 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.
- 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.
- 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.
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.
What to take from this
- 01
Patch Linux for CVE-2026-98432 and reboot. The new kernel doesn't protect you until it's the one running.
- 02
Take WS_FTP Server to 2025.0.4 or 2024.0.7. Nothing lower closes all fifteen flaws.
- 03
After the Rails fix, rotate secrets if attachments sit on the Disk service. The patch can't recall anything already read.
- 04
Give the November MuleSoft upgrade to a named person, because CloudHub won't do it this month.
- 05
Warn Snowflake users before JDBC 4.4.1 or Go 2.4.0, since cached sign-ins stop working once.
- 06
Search for the two removed root CAs before you install Terraform Enterprise 2.1.0 or 2.1.1.
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.
Three questions, about a minute
Pick an answer and we'll tell you if it's right, and why it is or isn't. The score stays in this browser.
-
Q1You run a WS_FTP server. A colleague installed 2025.0.3 because that's the version the Cyber Centre alert names. Are you done?
show the answer
B. No, you still need 2025.0.4 for most of the fifteen flaws That version covers just three of the flaws, though the 10.0 is one of them. The rest, the 9.9 command injection too, stay open until you're on the higher pair of versions.
-
Q2Your Rails app uses ImageMagick and stores attachments on the Disk service. You've upgraded Active Storage. What's left?
show the answer
C. Change secret_key_base and every secret the app can read A flaw on the Disk service could have let someone read files, and an upgrade can't undo that. The Rails team says to change those secrets and not to keep the old ones as a fallback.
-
Q3CloudHub 2.0 has always patched your apps for you, and now it's the November cycle. What do you do?
show the answer
D. Have a named person upgrade the apps by hand Automated sandbox and production patching is paused for the November cycle, so apps only get the patches if someone upgrades them manually.