.png){kind=logo}
Upgrade Recommendations
-
If you have not upgraded to 3.6.0 yet, upgrade directly from 3.5.x to 3.6.1 to get 3.6 features and the latest security fixes in one step.
-
If you are on 3.6.0, upgrade to 3.6.1 for the latest security and reliability fixes.
-
For a fresh installation, use the 3.6.1 installer package.
Release Notes
3.6.1 is a maintenance release with no new features. The main changes are as follows:
-
Installer-generated certificates' Root CA now honors its configured lifetime (default 10 years). Installs from 3.6.0 and earlier generated a root CA expiring one year after install day; 3.6.1 fixes this for new installs.
-
Installer temporary files now moved to installer-owned directories, so installation no longer fails on hosts with a locked-down or
noexec/tmp. -
Upgrades stop misreporting installer-managed
systemdconfig lines as customer drift and the install state keeps accurate packaged component versions to ensure upgrade detection stays correct. -
Bundled components refreshed: OpenSearch 2.19.6, Node.js 22.23.1, Kafka 3.9.1-2, Dashboards 2.19.5-5, plus updated service images with security fixes.
Known Issue: Git scans fail on hosts with no Git package at platform installation
When no system Git package is present, the installer deploys its bundled Git to /usr/local with root-only permissions (700). Platform services run as a non-root user, so Git scans fail with GIT-500 ... executable file not found in $PATH. The platform installation itself completes without errors; the problem first appears when running a Git scan. Hosts with Git already installed are not affected.
WORKAROUNDS
Pick one workaround:
-
Repair permissions on the bundled Git (for air-gapped environments):
sudo chmod -R a+rX /usr/local/bin/git /usr/local/bin/git-* \ /usr/local/bin/scalar /usr/local/libexec/git-core /usr/local/share/git-core
-
If the host can reach RHEL repositories, switch to the distribution's Git:
sudo rm /usr/bin/git # remove the installer's symlink sudo dnf install git-core
Neither workaround requires a service restart.
Verify with sudo -u <service user> git --version, then run a Git scan.
Vulnerabilities Status
Customer-Installer
|
Component |
Critical
|
High
|
Medium < 90 days |
Low
|
|
|
0 |
0 |
2* |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
2* |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
2* |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
1 |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
2* |
0 |
|
|
0 |
0 |
0 |
0 |
* This security fix introduces a breaking change. A non-breaking resolution with refactored code is planned for the next major release.
Kubernetes
|
Component |
Critical
|
High
|
Medium > 90 days |
Low
|
|
|
0 |
0 |
2* |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
2* |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
2* |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
3** |
42** |
21** |
|
|
0 |
10** |
139** |
120** |
|
|
0 |
0 |
0 |
0 |
|
|
0 |
0 |
2* |
1 |
|
|
0 |
1*** |
0 |
0 |
|
|
9*** |
14*** |
18*** |
0 |
* This security fix introduces a breaking change. A non-breaking resolution with refactored code is planned for the next major release.
** The majority of these vulnerabilities come from OS packages that do not yet have a fixed version available.
*** Currently on the latest version. Resolution depends on a vendor-provided update.
Download Links
Release packages can be download from: InfoSec Global Inc.
Access credentials are required for all download links.