Version 6.7.1-2, Build (20260825)

Security & Third-Party Components
Every GA and hot fix release is inventoried in the Stratusphere UX — Third-Party & Open Source Software Inventory, which publishes a per-release list of the CVEs resolved — enumerated by CVE identifier and by the component whose update addressed them — alongside the component list and the CycloneDX 1.7 SBOM. Refer to that article when you need to confirm which vulnerabilities a given hot fix remediates.

Release Notes

Stratusphere version 6.7.1-2 updates to resolve security vulnerabilities:

• Addressed 23 High and Critical severity vulnerabilities identified by vulnerability scanning in the appliance service dependencies, primarily by upgrading golang.org/x/crypto from v0.50.0 to v0.52.0.

Web UI:

• Fixed an issue where deep links from CommandCTRL into Diagnostics > Individual Views did not apply the machine filter, so the view opened without being scoped to the requested machine.
• Fixed an issue where Diagnostics > Detailed Views left an empty Basis Search key pair in the JSON API call, which caused a “No records returned” message when filtering on a column such as Owner Name.
• Removed placeholder tabs for future versions under Diagnostics > Individual Views.
• Removed placeholder tabs for future versions under Overview that displayed as disabled.

CID Key:

• Fixed a security incompatibility that prevents earlier Connector ID Keys from obtaining a certificate from a Hub running at a higher security posture with EMS disabled, causing the TLS handshake and registration to fail. Since the fix is delivered in the Connector ID Key itself, Liquidware recommends upgrading your installations with the 6.7.1-3 version of the Connector ID Key included in this release to continue communicating with Hubs running at higher security levels.

Hub, Database & Collectors:

• Fixed a write gap in the tntdbconf utility, which wrote property changes directly into tntdb.conf and could expose a partial write to processes monitoring the file. The updated file is now put in place with an atomic rename, and the original is restored automatically if the replacement fails.
• Fixed an issue where transparent CAC authentication failed when the User Principal Name on the CAC certificate did not match the letter case of the User Principal Name stored in Stratusphere. The corrected user identity module with updated version number is packaged with the appliance again; it shipped in the earlier 6.7.0-5 hotfix images but was omitted from the final one due to incorrect versioning.
• Fixed an issue where CAC could not be enabled after a hotfix upgrade, because the smaller hotfix upgrade images did not contain the lwl-stig-base-dod-cac package.
• Fixed a race condition where standalone backend services on a standalone Hub wouldn’t start post-upgrade if the local database service took longer to start up.

Procedure:

IMPORTANT: The following resolution applies ONLY to Stratusphere appliances running Stratusphere 6.7.0-2 or later. 6.7.0-2+ appliances will be upgraded to the latest 6.7.1 hotfix version.

1. All appliances should show version 6.7.0-2 in the console status page and within the "/etc/tnt-release" file.
2. If a hub, database, or collector appliance show a lower version, consult the Stratusphere Upgrade & Migration Guidance document for instructions and then return to this KB article. 
3. The upgrade should automatically fail to apply if attempted on any version previous to 6.7.0-2. You may apply Cumulative Hotfix for Stratusphere 6.7.0-5 to your 6.7.0-5 appliances if you are not ready to upgrade to 6.7.1, but the 6.7.0-5 hotfix has no security updates or bug fixes after April 14, 2026.

Preparation

• On a local desktop with access to the Internet, download the Stratusphere upgrade image by clicking the following link: https://cdn.liquidware.com/stratusphere/releases/stratusphere-6.7.1-2.img  
• COMING SOON: Alternatively, once Liquidware activates the online upgrade repository, Hub appliances with internet access will get notified of the update at the top of the console status page and the Stratusphere web UI, with an option to download the latest image on the Upgrades > Offline tab.

• (Recommended) Shut down and take a snapshot of the Hub, Database, and Collector appliances.
• Power up all your Stratusphere appliances: Hub, Database, and Collectors.
• (Recommended) Keep the local appliance hypervisor console to the Stratusphere Hub, Database, and Collector open during the upgrade process. 
  • This is helpful because the user can observe the upgrades running and their status, reboot activity, and uptime on the console status screens.

Upload Update

To upload the update, complete the following steps:

• Log in to the Administration section of the Stratusphere Hub Web UI.
• Navigate to the Hub Administration > Upgrades > Offline tab.
  • COMING SOON - As mentioned above, Hub Administration > Upgrades > Online tab will also allow you to download the image directly to the hub from an online repository.

The screen displays a page with either a Browse or Choose File button depending on your browser.

• Click the Browse or Choose File button, navigate to the location where the stratusphere-6.7.1-2.img file was stored when you downloaded it from the link above. Select the file, then open it.
• Click the Upload Update button. A progress bar with the message “Upload in Progress (This may take several minutes)” will be displayed as the upgrade image is uploaded to the Hub.

After the upload finishes, the progress bar displays the message: “Download Completed. Verifying Image,” indicating that the Hub is verifying the integrity of image file that was uploaded.

After the image is verified, the message “Upload Completed Successfully" appears at the top of the page.

Install Update on Hub and Database

• Click the Install Update button to install the upgrade on the Stratusphere Hub.
• The UI displays a progress bar with the message “Install in Progress (This might take several minutes)."
• As soon as the upgrade starts, all services on the appliance are turned off. The UI then displays the message “Stratusphere is being upgraded after which the Hub will be rebooted. You will be logged out in 10 seconds. Please wait at least 15 minutes to log back in." The user is then logged out of the Web UI automatically and a generic “Stratusphere is down" message is displayed.
• At this point, you could:
  • Close the browser tab and open the Hub and/or Database console windows
  • Observe their status screens to see messages at the top like “Updates are Running”.
  • On AWS & Azure, you can use your preferred SSH client to SSH into the appliance with your console credentials for your appliance and run: watch -c cat /tmp/status command to view the console status screen.
  • Alternatively, use the appliance console screen on AWS / Azure and refresh the appliance console web page to manually update the status screens to check whether the updates are running and for the uptime since a reboot.
• If a separate Database appliance is connected, its upgrade is initiated first and is rebooted automatically at the end of the upgrade.
• The Hub then upgrades itself and reboots as well. In some cases, the appliances might reboot again.
• Once the upgrade is completed and the appliance(s) reboot:
  • Observe the uptime on the Hub appliance status screen at the top left of the screen next to "top -"
  • Wait at least 15-30 minutes after the reboot of the Hub for all internal services to start before opening the web browser and accessing the UI again.
• If the version number did not change, or if the login page did not load as expected, or the “Stratusphere is down” message does not clear, or if there are any “HTTP Status 404 – Not Found” errors once you log in, then refer to the After upgrade, the Web UI displays a 404 Error topic in the Troubleshooting KB article.

Install Update on Collectors

If there are any Collectors on this installation of Stratusphere, complete the following steps:

• Navigate to the Collector Administration > Collectors tab of the Web UI.
• Select each 6.7.0-5 Collector in the list one at a time and click the Upgrade button.
• The Collectors then upgrade and reboot themselves.
• After they reboot, wait about 15 minutes, then verify their Status is OK on the Collector Administration > Collectors tab

Validate and Complete the Update

This hotfix will update the tnt-release and kernel version.  You may confirm that each appliance is updated by logging in and running uname -rv; rpm -q tnt-release.  The output should match the values here:

$ uname -rv; rpm -q tnt-release
4.18.0-553.156.1.el8_10.x86_64 #1 SMP Tue Aug 18 05:18:46 PDT 2026
tnt-release-6.7.1-2_202608250958.cbdf687.noarch

The blue banner at the bottom of the UI and Collector Admin Version column should show the hotfix build number 6.7.1-2 (20260825)

Connector ID installers at Hub Administration > Connector ID Keys > Connector ID Key Software will be updated to version 6.7.1-3

Update Connector ID agents

To update Connector ID Key agents for persistent machines, complete the following steps:

1. Log in to the Stratusphere Hub Web UI Administration section.
2. Navigate to Hub Administration > Connector ID Keys > Connector ID Keys Properties tab.
3. Select the appropriate machine group in the Configure properties for dropdown list.
4. Scroll down and select the Automatically update Connector ID Keys when new software versions are installed in the Stratusphere Hub checkbox.
5. Scroll down and click the Save button.
6. The CID Keys then automatically download the installer for the updated version and upgrade themselves on their next callback.

Machines with PowerShell disabled will need the 6.7.0-10 or greater Connector ID installer.. As well, for non-persistent machines, your master or gold images need to be updated with the new CID Key software.  To update Connector ID Key agents for these machines, complete the following steps:

1. Log in to the Stratusphere Hub Web UI Administration section.
2. Navigate to the Hub Administration > Connector ID Keys > Connector ID Key Software tab.
3. Download the appropriate installer for your environment.
4. Open your gold image as an Administrator and follow the instructions outlined in the appendixes of the Stratusphere Installation & Configuration Guide to update agents on gold images.

Before completing the upgrade and removing the snapshots, Liquidware recommends waiting for a few hours to ensure that the CID Keys agents call back in a round robin manner through their list of Collectors. Make sure that the following are true:

• New data is being collected and saved within the database.
• New data is visible within the Web UI.

After you verify that the installation has upgraded and is working properly, remove the snapshots from the Stratusphere appliances.

The upgrade process is complete.

Troubleshooting:

For troubleshooting, see the following KB articles and/or contact Liquidware Support:

• Troubleshooting 6.7.x Hotfix upgrade