October 2026
Portal 8.4.4000.60
CTERA Portal version 8.4.x is first released with version 8.4.4000.23 and includes a number of new features, which are described in What's New in CTERA Portal Version 8.4.x.
Upgrading the CTERA Portal
When upgrading from 8.2.x, you must upgrade from version 8.2.1500.58 or later.
Portals that only have one NIC can be upgraded to this version and continue with a single NIC. Portals configured to run with dual-NICs (earlier versions of 8.4.X) can also continue to function with dual-NICs. The second NIC is used when MCP and n8n services are configured.
The CTERA Portal is upgraded as described in Upgrading a CTERA Portal.
Pre-upgrade Requirements
If SHA-1 certificates are in use, they must be replaced with SHA-2-based signatures before starting the upgrade.
You cannot upgrade the portal while running a storage node migration.
General Considerations
If you are using the Thumbnails service, after upgrading the portal, from the from 8.2.1500.58 or later, you must disable and then re-enable the service.
After the first server boot at the end of the upgrade, portal components are loaded on to the data pool. Only after these components have successfully been loaded will the user interface become available.
Storage Node Considerations
You cannot upgrade the portal while running a storage node migration.
When storage nodes are deprecated and a deprecated storage node is being used, the upgrade stops with an error message.
When storage node names are changed. The upgrade includes updating the names in the user interface.
New Features
| ID Number | Description |
|---|---|
| PIM-9662, PIM-10483, PIM-10832, PIM-10963, PIM-10967, PIM-10969, PIM-10973, PIM-10974, PIM-10975 | Improvements to Fusion Direct: * Support for Microsoft Azure Blob Storage as the storage node. * Better performance handling bulk changes. |
| PIM-9982, PIM-9983, PIM-9984, PIM-9985, PIM-9986, PIM-9987, PIM-9988, PIM-9989, PIM-9990, PIM-10149, PIM-10227, PIM-10505, PIM-10533, PIM-10534, PIM-10535, PIM-10536, PIM-10537, PIM-10538, PIM-10539, PIM-10540, PIM-10541, PIM-10542, PIM-10587, PIM-10633, PIM-10634, PIM-10757, PIM-10827, PIM-10835, PIM-10886, PIM-11087 | Improved security, including resolving CVE-2026-65927, CVE-2026-79677, CVE-2026-4800, CVE-2026-41293, CVE-2026-4800, CVE-2026-65182, CVE-2026-66422, CVE-2026-68525, CVE-2026-68569, CVE-2026-65183, CVE-2026-65905, CVE-2026-65637, CVE-2026-73180, CVE-2026-78437, CVE-2026-78383, CVE-2026-75973, CVE-2026-86350, CVE-2026-76183, CVE-2026-86248, CVE-2026-77756, CVE-2026-77791, CVE-2026-77762, CVE-2026-87022, CVE-2026-73581 |
| PIM-10123 | Improved performance when migrating a large folder. |
| PIM-10301, PIM-10352 | A new option in the Virtual Portal Settings page: Allow end users to browse groups for collaboration. When on, the default, end users can select Active Directory groups to collaborate with. |
| PIM-10309, PIM-10502 | MCP OAuth Resource Server compliance has been implemented with the MCP service, making it compatible with multiple AI MCP clients. |
| PIM-10355 | More information is displayed about the collaborators when specifying content for collaboration: |
| PIM-10649, PIM-10725, PIM-10726, PIM-10736, PIM-10751, PIM-10776, PIM-10839 | Improvements to Fusion Direct. |
| PIM-10838, PIM-10846 | The MCP service endpoint is now https://<portal-host>/mcp for the Portal URL. |
| PIM-11009 | The status of Nginx and Envoy have been added to portal-manage.sh |
Resolved Issues
| ID Number | Description |
|---|---|
| PIM-8087 | The error returned when attempting to access a bucket without the correct permissions was misleading. |
| PIM-10190, PIM-10840 | The Edge Filer Syslog service frequently failed. |
| PIM-10244 | Filenames containing a + or - symbol were not listed is search results. |
| PIM-10315 | Upgrading from portal version 8.3.3300.x failed. |
| PIM-10342 | Two different total number of files were displayed in the dashboard. |
| PIM-10381, PIM-10382, PIM-10383, PIM-10384 | S3 metadata was not stored in the portal database after performing an S3 API PUT operation with CTERA Fusion Gateway. |
| PIM-10465 | The snapshot cleaner task ran continuously back-to-back which caused high CPU usage and replication lag alerts. |
| PIM-10476 | After changing provisioning, CTERA Drive Share/Protect agents could not connect to the portal. |
| PIM-10490 | Retrieving or copying files using the S3 API and CTERA Fusion Gateway failed when the filename contained the + character or URL-encoded special characters. |
| PIM-10563 | Microsoft Azure Blob Storage storage nodes could not connect to the portal when Direct Mode was disabled and Use HTTPS was enabled. |
| PIM-10596, PIM-10604 | Accessing files using the S3 API and CTERA Fusion Gateway failed or was very slow when the load was high. |
| PIM-10597 | Local quota values lagged behind the database values, which caused the replication database to lose synchronization. |
| PIM-10609 | Moving a local folder whose name contains German umlauts in macOS NFD form into a portal cloud drive created the folder but left it unresolvable through WebDAV, causing child uploads to be skipped. |
| PIM-10619 | In CTERA Portal version 8.4.4000.53, accessing the portal from CTERA Drive Connect failed. |
| PIM-10646 | Searching using a value that contained a dot (.) failed from Windows File Explorer. |
| PIM-10783 | Using the S3 API and CTERA Fusion Gateway to load over 60,000,000 files, failed. |
| PIM-10808 | In CTERA Portal version 8.4.4000.53, when both Direct Mode and antivirus protection are configured, the portal could become unresponsive. |
| PIM-10812, PIM-10813 | After a temporary DNS failure, Active Directory authentication failed. |
| PIM-10821 | In CTERA Portal version 8.4.4000.53, attempts to reshare a folder with an external user, by selecting resend option, failed. |
| PIM-10828 | Using the S3 API and CTERA Fusion Gateway with an object key length of 1024 bytes failed and a key length greater than 1024 bytes returned an HTTP 500 error instead of a Bad Request / KeyTooLong error. |
| PIM-10847 | From CTERA Portal version 8.4.4000.51, performance was degraded when accessing the portal using the WebDAV protocol. |
| PIM-10919, PIM-11054 | /etc/hosts was rewritten with mode 640 (umask 027), which caused the hosts file to be unreadable and the primary database became full and the portal became inaccessible. |
| PIM-10964 | With Fusion Gateway, the S3 endpoint was enabled on the portal but the corresponding S3 endpoint role was not displayed in the server roles. |
| PIM-10997 | In CTERA Portal version 8.4.4000.53, when Messaging and FIPS were implemented, Kafka Connect entered a continuous restart loop. |
Edge Filer 7.13.6000.26
CTERA Edge Filer version 7.13.x was first released with version 7.13.6000.3 and included new features, which are described in What’s New in CTERA Edge Filer Version 7.13.x.
Upgrading a CTERA Edge Filer from an Earlier 7.x Version
CTERA recommends that you only upgrade to a new version from an immediate previous version. If you have an older version, upgrade in steps, first to an intermediate previous version and then to the new version. For example, to upgrade from 7.11.x to 7.13.x, first upgrade to 7.12.x and only then to this version.
Due to the PHP2Shell Remote Code Execution (RCE) Security Vulnerabilities CVE-2026-109618 and CVE-2026-109619, CTERA strongly recommends upgrading to this version.
After upgrading the edge filer, downgrading the edge filer is not possible.
Upgrading the software of an edge filer running an earlier 7.x version can be performed automatically when the edge filer is connected to a CTERA Portal and the latest edge filer firmware TGZ file is uploaded to the portal.
Resolved Issues
Resolved the PHP2Shell Remote Code Execution (RCE) Security Vulnerabilities CVE-2026-109618 and CVE-2026-109619.
Edge Filer 7.12.5400.28
CTERA Edge Filer version 7.12.x was first released with version 7.12.5400.5 and included new features, which are described in What’s New in CTERA Edge Filer Version 7.12.x.
Upgrading a CTERA Edge Filer from an Earlier 7.x Version
CTERA recommends that you only upgrade to a new version from an immediate previous version. If you have an older version, upgrade in steps, first to an intermediate previous version and then to the new version. For example, to upgrade from 7.11.x to 7.13.x, first upgrade to 7.12.x and only then to this version.
Due to the PHP2Shell Remote Code Execution (RCE) Security Vulnerabilities CVE-2026-109618 and CVE-2026-109619, CTERA strongly recommends upgrading to this version.
After upgrading the edge filer, downgrading the edge filer is not possible.
Upgrading the software of an edge filer running an earlier 7.x version can be performed automatically when the edge filer is connected to a CTERA Portal and the latest edge filer firmware TGZ file is uploaded to the portal.
Resolved Issues
Resolved the PHP2Shell Remote Code Execution (RCE) Security Vulnerabilities CVE-2026-109618 and CVE-2026-109619.
Known Issues
| ID Number | Description |
|---|---|
| — | macOS Spotlight is not supported. |
| APP-28061 | Read only and Read/Write permissions follow the Samba convention of using the less strict permission. Workaround: Make sure all users that have the read only permission are in a group that only has a read only permission and not in a group that has read/write permission. |
| APP-28193 | The last cloud share in the Shares page is displayed OFFLINE, even though it is online. |
| APP-30498 | Previous versions of a file in a nested share are not displayed in a different SMB session. |
CTERA Edge Filer 7.11.5100.39
CTERA Edge Filer version 7.11.x was first released with version 7.11.4900.3 and included new features, which are described in What’s New in CTERA Edge Filer Version 7.11.x.
Upgrading a CTERA Edge Filer
CTERA recommends that you only upgrade to a new version from an immediate previous version. If you have an older version, upgrade in steps, first to an intermediate previous version and then to the new version. For example, to upgrade from 7.11.x to 7.13.x, first upgrade to 7.12.x and only then to this version.
Due to the PHP2Shell Remote Code Execution (RCE) Security Vulnerabilities CVE-2026-109618 and CVE-2026-109619, CTERA strongly recommends upgrading to this version.
After upgrading the edge filer, downgrading the edge filer is not possible.
Upgrading the software of an edge filer running an earlier 7.x version can be performed automatically when the edge filer is connected to a CTERA Portal and the latest edge filer firmware TGZ file is uploaded to the portal.
Resolved Issues
Resolved the PHP2Shell Remote Code Execution (RCE) Security Vulnerabilities CVE-2026-109618 and CVE-2026-109619.
Edge Filer 7.13.6000.25
CTERA Edge Filer version 7.13.x was first released with version 7.13.6000.3 and included new features, which are described in What’s New in CTERA Edge Filer Version 7.13.x.
Upgrading a CTERA Edge Filer from an Earlier 7.x Version
CTERA recommends that you only upgrade to a new version from an immediate previous version. If you have an older version, upgrade in steps, first to an intermediate previous version and then to the new version. For example, to upgrade from 7.11.x to 7.13.x, first upgrade to 7.12.x and only then to this version.
After upgrading the edge filer, downgrading the edge filer is not possible.
Upgrading the software of an edge filer running an earlier 7.x version can be performed automatically when the edge filer is connected to a CTERA Portal and the latest edge filer firmware TGZ file is uploaded to the portal.
New Features
| ID Number | Description |
|---|---|
| APP-29827, APP-30849, APP-30886 | The support report content has been expanded to help with troubleshooting. |
| APP-30599,APP-30658 | Performance improvements, especially when there are many empty cloud folders and cloud folders without exceptions. |
| APP-30723, APP-30727, APP-30875, APP-30879, APP-30881, APP-30885, APP-30903, APP-30907, APP-30908, APP-30987, APP-30989, APP-30990, APP-30998 | Improvements to searches: * Monitoring the CTERA Search service has been added to the Services page. This service is enabled when the Advanced Search option has been installed on the CTERA Portal. * The search results page size has been increased to 200. * Search results require TLS validation. * A maximum number of returned results can be set. For details contact CTERA Support.  |
| APP-30804, APP-30805 | Improved security, including resolving CVE-2026-64600. |
| APP-30829, APP-30830, APP-30836, APP-30839 | macOS Spotlight improvements including changing the default number of worker processes to 5 and making this value configurable by running CLI. For details, contact CTERA Support. |
Resolved Issues
| ID Number | Description |
|---|---|
| APP-29474 | Audit logs could be set up to write to a share that pointed to an archive folder. |
| APP-30184 | POSIX ACLs were not enforced on shares on a second volume. |
| APP-30806, APP-30838 | There was a high RAM usage during a migration. |
| APP-30816 | In CTERA Edge Filer version 7.13.6000.19, if a folder was deleted while a nested file was open, the nested file is not deleted. |
| APP-30828 | A user could be added to both the blocked users group and the excluded users group. |
| APP-30831 | From CTERA Edge Filer version 7.13.6000.16, rebooting the edge filer intermittently prevented full deduplication of files. |
| APP-30832 | macOS Finder could produce different search queries based on whether Enter was pressed or not after typing the search term. |
| APP-30874 | Audited SMB traffic consumed writable tmpfs (temporary file system). |
| APP-30899, APP-30900, APP-30902 | Improvements when a Fusion Direct cloud folder is configured: * When Azure storage is used. * Uploading small files from the edge filer to the portal. |
| APP-30935, APP-30975, APP-30976 | When NAS was down, users and groups crashed. |
| APP-30988 | Directory names ending with a space or period displayed in macOS as empty. |
Drive Connect 5.3.2
Windows
New and Improved Features
*.localhost hostnamenow resolves to127.0.0.1 / ::1without extra configuration.- Microsoft PowerPoint files open faster.
- Windows no longer goes to sleep while a file transfer is running, so transfers aren’t interrupted.
Resolved Issues
- The client prompted you to pick a certificate when accepted issuers were not listed by the WebDAV server.
- Read-only files could not be pinned and kept on the local disk.
- Moving a file from a subfolder to the root cloud folder now syncs right away.
- Opening Microsoft Word files took a long time.
- Partial reads from Microsoft PowerPoint caused performance problems.
Known Issues
- In some cases, when Drive Connect is connected to a CTERA Portal version 8.2.1500.8.6 or earlier, SSO might not prompt the client mount. If this happens, enter the following URL in the browser:
https://portal_address/ServicesPortal/activate?scheme=x-cteradriveconnect-action:websso
macOS
New and Improved Features
*.localhost hostnamenow resolves to127.0.0.1 / ::1without extra configuration.- Microsoft PowerPoint files open faster.
- Videos stored as placeholder files now play smoothly in QuickTime Player.
Resolved Issues
- The client prompted you to pick a certificate when accepted issuers were not listed by the WebDAV server.
- Read-only files could not be pinned and kept on the local disk.
- Moving a file from a subfolder to the root cloud folder now syncs right away.
- Opening Microsoft Word files took a long time.
- Partial reads from Microsoft PowerPoint caused performance problems.
- Improved handling of Microsoft PowerPoint:
- Opening Microsoft PowerPoint files stalled the machine or increased CPU usage.
- In Integrated mode, there was an issue opening online PowerPoint files.
- Windows was significantly faster opening Microsoft PowerPoint files
Known Issues
- In some cases, when Drive Connect is connected to a CTERA Portal version 8.2.1500.8.6 or earlier, SSO might not prompt the client mount. If this happens, enter the following URL in the browser:
https://portal_address/ServicesPortal/activate?scheme=x-cteradriveconnect-action:websso