Version: 4.4.0

Release Notes

What's New in Version 4.4.0

VAST Mesh Failover — Enables circular failover across three or more VAST clusters (A → B → C → A) without manual VAST intervention after initial setup. Supports both protected path–level and tenant-level failover.
Spurious S3 Event During File Recovery — When recovering files using Cyber Recovery Manager, a new S3 event may be raised if the recovery test user matches the bucket owner.

VAST Cluster Reachability Issue When Cluster Name Contains Spaces — Fixed an issue where a VAST cluster reachability error occurred when the cluster name contained spaces, including trailing or whitespace characters.
TD07 Events in Monitor State Raising Incorrect Event State — Fixed an issue where TD07 events in monitor state incorrectly raised a WARNING state event instead of a MONITOR state event, and events were not archived as False Positive after expiration.
Cyber Recovery Manager Support for Non-Default Tenants on VAST — Fixed a limitation where Cyber Recovery Manager on VAST clusters only supported the default tenant. Non-default tenants are now supported.
VAST Security Guard Job Failing Intermittently — Fixed an issue where Security Guard jobs on VAST clusters failed intermittently without a deterministic root cause.

Component	Description	Reference
CWE-1004	Cookie stored without `HttpOnly` flag, exposing session data to client-side scripts.	CWE-1004
Nginx v1.27.3	Known vulnerabilities in F5 Networks nginx 1.27.3.	Snyk
Lodash v4.17.5	Prototype Pollution and Code Injection vulnerabilities.	Snyk
NextJS v14.2.5	Known vulnerabilities in NextJS 14.2.5.	Snyk
Bootstrap v3.3.1	Known vulnerabilities in Bootstrap 3.3.1.	Snyk
CWE-614	Sensitive cookie transmitted without `Secure` attribute in HTTPS sessions.	CWE-614

CYBER-1437: Readiness Check for Pure Safe Mode — Readiness checks cannot determine if the FlashBlade is running in Safe Mode and will report ready for failover, but will fail actual failover.

Workaround: None - failover while in Safe Mode requires assistance from Pure Support.
CYBER-1546: SMB Sessions from Source Are Not Disconnected after Failover — Client SMB sessions are disconnected but will reconnect back to a read-only file system.

Workaround: Update DNS with the new IP address of the server name used by clients to access the FlashBlade SMB shares. Manually disconnecting and reconnecting client share may be required.
CYBER-1607: License State Changes to "Unlicensed" When a FlashBlade Is Removed from Inventory and Re-added — After removing a FlashBlade from inventory and re-adding it back, the device may show up as "unlicensed" in the list of managed devices in the License view.

Workaround: Manually set the state back to "user-licensed" and restart the SCA by logging into the Core Agent Appliance and running the command:
```
sudo systemctl restart sca
```
CYBER-1622: File System Export Policy Names with More Than 63 Characters Fail to Replicate — A long export name will fail to replicate from FlashBlade 4.6.3 back to 4.6.2 due to smaller name limitations on the previous version.

Workaround: Change the name of the policy to less than 63 characters.

For questions about upgrading to version 4.4.0 or assistance with any of the fixes in these release notes, contact Superna Support.