SEM 2026.4 release notes
Release date: October 20, 2026
Here's what's new in SEM 2026.4. You can find the applicable system requirements here.
Skipping a version? If you're upgrading from more than one version back, don't rely on this page alone — review the release notes aggregator to see everything that changed across the versions you’re skipping
To view release notes, system requirements, and product guide (formerly known as administrator guide) PDFs for supported versions of SEM, see SEM previous versions.
New features and improvements in SEM
SEM Manager and Agents JDK Update
SEM Manager and Agents updated to JDK 25 LTS to provide a current LTS runtime with improved stability, performance, garbage collection, and security. Custom Agent Java deployments must be updated to Java 25.
SEM Manager deployment on Red Hat Enterprise Linux (RHEL)
SEM now supports SEM Manager as an RPM application on customer-managed RHEL 9.8. This deployment path is used for FIPS and requires OS, repository, network, firewall, storage, and time-sync readiness before installation. The FIPS edition supports new installations only. See Install the SEM Manager FIPS edition on Red Hat Enterprise Linux.
Dedicated FIPS edition
This version introduces a dedicated FIPS edition for FIPS 140-3-aligned deployments. It is delivered as an RPM application for customer-managed RHEL 9.8 with OS FIPS mode enabled.
Debian SEM appliances remain non-FIPS and cannot be converted in place.
IPv6 and dual-stack support
IPv6 and dual-stack support has been added for both FIPS and non-FIPS deployments. SEM can run in IPv4-only or dual-stack mode for administration, syslog collection, agent communication, and event monitoring.
STIG Compliance (password policy enhancement)
This version adds STIG-focused password and security hardening for stronger compliance readiness, especially with the FIPS and platform security baseline.
Certificate, LDAP, and Trust Store Improvements
Certificate, LDAP, and trust-store behavior of FIPS and non-FIPS deployments has been improved in this version. Instead of relying only on the leaf certificate, SEM trusts the root or farthest-available Certificate Authority (CA).
Trust store behavior is improved and non-TLS LDAP configuration support is removed.
Platform Connect Improvements
This version validates key Platform Connect API flows, such as datacenter listing, tenant creation, and tenant reactivation. Workflow for handling installation, timeout, checksum, and network-reachability scenarios is improved. Improved default anomaly detection registry eliminates the blank use-case experience while plugin synchronization completes. Platform Connect is not available in the FIPS mode.
Anomaly Detection
New use cases and event actions have been added to help analysts identify suspicious behavior, route anomalies to rules, and investigate related historical events.
New use cases include Ransomware/File Integrity Monitoring, Port Scanning, and Password Spraying.
The Send to Rules and Send to Historical Events actions are available in a three-dot menu when a detection use case is selected. Use Send to Rules when an anomaly should trigger an established rule, notification, escalation, or response process. With the Send to Historical Events, you can review historical events to identify recurring sources, accounts, destinations, or time-based patterns.
Compliance Reporting and Query Packs
This version introduces query packs as a guided compliance-reporting workflow in Historical Events & Reports. The first pack, NIST 800-53 (Rev 5.2.0), groups 28 new queries by control family, bringing the total number of available queries to 41.
Generate all of the pack's reports at once as a single ZIP file, or schedule the pack to run and deliver automatically. See Use query packs for compliance reports.
Debian Updates
Debian was updated to 12.15, bringing updated environments, maintenance updates, bug fixes, and security improvements.
General improvements
- Updated Spring Framework to 6.2.19.
Fixed CVEs
At SolarWinds, we prioritize the swift resolution of CVEs to ensure the security and integrity of our software. In this release, we have successfully addressed the following CVEs.
Third-party CVEs
| CVE-ID | Vulnerability title | Description | Severity |
|---|---|---|---|
| CVE-2023-3635 | Okio Denial of Service Vulnerability | GzipSource does not handle an exception that might be raised when parsing a malformed gzip buffer. This may lead to denial of service of the Okio client when handling a crafted GZIP archive, by using the GzipSource class. | 7.5 High |
| CVE-2024-12798 | Logback-core Arbitrary Code Execution Vulnerability | ACE vulnerability in JaninoEventEvaluator by QOS.CH logback-core upto including version 0.1 to 1.3.14 and 1.4.0 to 1.5.12 in Java applications allows attacker to execute arbitrary code by compromising an existing logback configuration file or by injecting an environment variable before program execution. Malicious logback configuration files can allow the attacker to execute arbitrary code using the JaninoEventEvaluator extension. A successful attack requires the user to have write access to a configuration file. Alternatively, the attacker could inject a malicious environment variable pointing to a malicious configuration file. In both cases, the attack requires existing privilege. | 5.9 Medium |
Installation or upgrade
For new installations, you can download the installation file from the product page on https://www.solarwinds.com or from the Customer Portal. For more information, see the SEM Installation and Upgrade Guide.
For upgrades, see Upgrade SEM in the SEM Administrator Guide to determine the upgrade path, review best practices for SEM upgrades, and upgrade the SEM components.
Known issues
SEM manager application for FIPS mode
When switching between IPv4 and IPv6, the SEM manager application for FIPS mode needs to be restarted and may need certificates remade if flipping between IPv4 and IPv6
Mac OS installation
Currently, there is no macOS agent.
Resolution or workaround: There is no workaround at the moment. SolarWinds is working on providing this in a future version.
End of life
| Version | EoL announcement | EoE effective date | EoL effective date |
|---|---|---|---|
| 2024.4 | October 20, 2026: End-of-Life (EoL) announcement – Customers on SEM version 2024.4 or earlier should begin transitioning to the latest version of SEM. | November 20, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SEM version 2024.4 or earlier will no longer actively be supported by SolarWinds. | November 20, 2027: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SEM version 2024.4. |
See the End of Life Policy for information about SolarWinds product life cycle phases. To see EoL dates for earlier SEM versions, see SEM release history.
Legal notices
© 2026 SolarWinds Worldwide, LLC. All rights reserved.
This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.