SolarWinds Platform 2025.2 release notes
Release date: June 10, 2025
Here's what's new in SolarWinds Platform 2025.2.
Learn more
- See the release notes aggregator to view release notes for multiple versions
and multiple SolarWinds Platform products on a single page. - See SolarWinds Platform 2025.2 system requirements to learn about prerequisites for running and installing SolarWinds Platform 2025.2.
- See the SolarWinds Platform 2025.2 Administrator Guide to learn how to work with SolarWinds Platform.
New features and improvements in SolarWinds Platform
Intelligent Maps parity and migration
-
Connections now support multiple links. You can connect more than a single interface between two entities. This covers one of the last major differences between Network Atlas and Intelligent Maps to make the migration of Network Atlas maps to Intelligent Maps possible.
-
Background color is now supported in text boxes.
-
Hyperlinks for lines are now supported.
-
Dark Mode is supported in Intelligent Maps.
-
Pills on connections can now be disconnected from the line to improve map readability.
Dashboard improvements
-
Added support for Custom Properties in Modern Dashboard Global Filters
-
Updated My Deployment tabs
-
Server: In previous versions, users configured High Availability in this tab. Starting with this version, the tab shows all SolarWinds servers, including their status and additional polling details. This tab displays the following SolarWinds Platform servers:
-
Main Polling Engine (MPE)
-
Additional Polling Engine (APE)
-
Additional Web Server (AWS)
-
Remote Collector
-
Standby HA servers (MPE and APE)
-
-
Pools (new tab): High Availability status and configuration were moved to this new tab. The tab was redesigned completely to show more relevant information regarding HA pools and to make it easier to manage them.
-
Recurring/scheduled maintenance windows
-
Added support for scheduling recurrent maintenance windows. You can schedule maintenance windows daily, weekly or monthly. You can also pick if you want to mute alerts for the devices or unmanage devices, and quickly assign supported entities to the maintenance windows.
-
Entities can have more than one recurring maintenance window, allowing users to schedule different maintenance timings on the same devices.
-
Maintenance windows can be found on the Manage Nodes page by selecting a node and then hovering over the Maintenance Mode button.
-
Existing functionality is preserved, including schedule management via SDK or API.
Alert variables for dependencies
-
Added alert variables to show dependency relationships in alert actions. The variables help answer what entities are affected if something goes down.
The new alert variables are
${N=SwisEntity;M=NodeDependencies}
and${N=SwisEntity;M=NodeDependenciesWithLinks}
.
gMSA support for WinRM polling
-
Added support for using gMSA (group managed service accounts) credentials when polling via WinRM.
gMSA is supported for all generic regular WinRM polling of Nodes/Volumes/Interfaces, AssetInventory, IPAM and SRM polling.
SAM has extended support with the exception of SAM real-time explorer, Service Control Manager, real-time Event Log Viewer, and AppInsight for Exchange.
Performance and other improvements
-
Improved Agent/polling scalability: Polling engines can now collect data from up to 1,000 agents and 60,000 SAM components (agent-based). This is an increase from 500 agents and 40,000 SAM components (agent-based) per polling engine.
-
Added more details on Windows Server connection methods for WMI, WMI (DCOM), and WMI (WinRM). These details include highlighting the connection mode in Add Node screens and displaying information about the last poll method in the Polling Details widget.
Two new reports were added to better understand Windows Node connections:
-
Windows Nodes Connection Summary: This report provides details on the connection mode setting (WinRM Preferred, WinRM Only, WMI Only) and the connection mode used.
-
Windows Nodes with WMI Fallback: This report lists nodes that use the WinRM Preferred method and are falling back to WMI.
-
-
Increased performance of PerfStack metric palette.
-
Increased performance of Capacity Forecasting widgets and reports.
-
Added the ability to manually change a SolarWinds Engine role via the API from Additional Polling Engine (Active) to Additional Polling Engine (Standby). Previously, this change was only possible through an uninstallation/reinstallation process. A new API verb called
SelectiveSwitchover
was introduced to facilitate the change. -
Full IPv6 address is now required in some Log Viewer conditions, such as
starts with
,ends with
, orcontains
). -
To improve security in the Log Viewer, SNMP community is no longer stored with traps. You can still use SNMP community in rule conditions.
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.
SolarWinds CVEs
SolarWinds would like to thank our Security Researchers below for reporting on the issue in a responsible manner and working with our security, product, and engineering teams to fix the vulnerability.
CVE-ID | Vulnerability Title | Description | Severity | Credit |
---|---|---|---|---|
CVE-2025-26394 | SolarWinds Observability Self-Hosted Open Redirection Vulnerability | SolarWinds Observability Self-Hosted is susceptible to an open redirection vulnerability. The URL is not properly sanitized, and an attacker could manipulate the string to redirect a user to a malicious site. The attack complexity is high, and authentication is required. | 4.8 Medium | Shahzin Sajid, Al Sabah Salim, and Shabeer Ali from the QatarEnergyLNG SOC team |
CVE-2025-26395 | SolarWinds Observability Self-Hosted DOM based reflective XSS Vulnerability | SolarWinds Observability Self-Hosted was susceptible to a XSS vulnerability using one of the fields in the URL that was not properly sanitized. The attack requires authentication using an administrator level account and user interaction is required. | 7.1 High | Shahzin Sajid, Al Sabah Salim, and Shabeer Ali from the QatarEnergyLNG SOC team |
Third-party CVEs
CVE-ID | Vulnerability title | Description | Severity |
---|---|---|---|
CVE-2024-9143 | OpenSSL Denial of Service vulnerability | Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding. The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions. Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. | 4.3 Medium |
CVE-2025-22869 | OpenSSH Denial of Service Vulnerability | SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted. | 7.5 High |
Fixed customer issues
Case number | Description | |
---|---|---|
00229327, 01773376 | When an external node's polling method is changed to ICMP, the node is polled and its status is displayed correctly. |
|
00757778, 01814500, 01885398 | SolarWinds Information Service (SWIS) no longer creates redundant files containing the SolarWinds-Orion key in the |
|
00806670, 01891212 | Polling services no longer push changes to rules while the services are being restarted. If the services for multiple polling engines are started at the same time, they can fail to start with the error such as the following:
|
|
00854188, 01193488 | If the SolarWinds Platform database is configured to use the AWS RDS endpoint instead of the AG listener, the Configuration Wizard no longer fails during a centralized upgrade with the following error:
|
|
01052957, 01429913, 01491822, 01523790. 01544348, 01763329, 01766637, 01812913 | Performance Analysis Dashboard (PerfStack™) charts are no longer slow to load. | |
01072152, 01801035 | Users can create and use account and view limitations based on Undefined values. | |
01512799, 01558490, 01864272, 01901522, 01941652 | The mechanism to download firmware vulnerability settings now uses the SolarWinds Platform proxy settings that allow the SolarWinds Platform server to make connections through a proxy server with authentication. Not using these settings could cause firmware vulnerability downloads to fail. |
|
01520455, 01684877, 01682272, 01616923, 01769959, 01750539, 01800483, 01731252 | The speed of agent reconnection has been improved. This decreases the amount of time before an agent reconnects to the SolarWinds Platform after a polling engine restart or failover. | |
01581882 | Database types are no longer mismatched in some files, which was causing query performance issues. | |
01685123, 01765176 | Users without map management rights can view shared maps, but they can no longer access the map editor. | |
01722168 | Group membership and status information shown on an additional web server matches the information shown on the main polling engine. |
|
01724270, 01792715 | Obsolete alert conditions no longer trigger false positive alerts. | |
01727113, 01736257 | When you unmanage a node or mute alerts, the Audit Event timestamps in the Message Center are in the same timezone as the ones on the Node Details page. | |
01781158 | If the LDAP port is blocked in a SolarWinds Platform deployment, an unhandled error is no longer returned. | |
01786484 | When you attempt to create a new map with the same name as an existing map, a number is added to the end of the new map name, and the new map and container are created without error. | |
01789258 | A custom property that was created in EOC and pushed to the SolarWinds Platform can be deleted in the SolarWinds Platform. | |
01794634 | The Manage Entities page can now be access only by users with admin or node management permissions. | |
01798154 | Alert history cleanup is now based on the alert history retention period rather than the events retention period. | |
01803075, 01863592 | When the SolarWinds Platform is installed on an Azure SQL Managed Instance, the Database Details page loads correctly instead of displaying the following error message:
|
|
01813022 | Platform Notifications (bell icon) now expire automatically after 30 days. This retention setting can be adjusted in the Polling Settings page under Notifications Retention. | |
01831725 | The SolarWinds Installer no longer allows a user to install EOC on a server where other SolarWinds Platform Self-Hosted products are installed. This would have corrupted the database. | |
01832734 | If a monitored AIX DB2 database supports "big endian" encoding, DB2 AIX monitoring no longer fails with the following error message:
|
|
01839072 | Network Atlas objects that have no defined shape or are not linked to any entity are now imported correctly. Non-entity objects are replaced with a circle. | |
01883907, 01926441 | *The time zone setting is no longer ignored when you bulk schedule maintenance or mute alerts. |
|
01884132, 01894127, 01901990 | For some nodes, including Windows Server 2008 and Windows Server 2022 nodes, List Resources no longer fails with errors such as the following:
|
|
01886755, 01893985, 01891571, | *Filtering entities and editing row properties on the Manage Entities page works as expected. |
|
01888132 | If a service account has more than 1,000 GCP projects, all projects are retrieved. The project selection wizard is paginated. |
|
01890968 | Exiting NOC mode from a modern dashboard no longer results in an error with the message |
|
01899647, 01901433 | SolarWinds Information Service (SWIS) by default uses |
*This fix was added after the RC release.
Installation or upgrade
For new SolarWinds Platform deployments, download the installation file from the product page on https://www.solarwinds.com or from the Customer Portal. For more information, see Get the installer.
To activate your product in an existing SolarWinds Platform deployment, use the License Manager.
For upgrades, go to Settings > My Deployment to initiate the upgrade. The SolarWinds Installer upgrades your entire deployment (all SolarWinds Platform products and any scalability engines).
For more information, see the SolarWinds Platform Product Installation and Upgrade Guide.
For supported upgrade paths, see Upgrade an existing deployment.
Known issues
Last updated: May 20, 2025
Stacked polling engine licenses get unassigned after upgrading to version 2025.2 (modules only)
If you're using SolarWinds Platform module licenses with stacked additional polling engine licenses and upgrade to 2025.2 or run the migration.exe /migrate
command, stacked licenses may become unassigned.
Resolution or workaround: Reassign the licenses to appropriate polling engines.
-
In the web console, go to Settings > All Settings > License Manager.
-
Select the license that was unassigned and click Assign.
-
Select a polling engine and click Assign again to confirm.
End of life
Integration with the SolarWinds Platform requires a supported version of the platform.
Version | EoL announcement | EoE effective date | EoL effective date |
---|---|---|---|
2023.1 | February 11, 2025: End-of-Life (EoL) announcement - Customers on SolarWinds Platform version 2023.1 or earlier should begin transitioning to the latest version of SolarWinds Platform. | March 13, 2025: End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for SolarWinds Platform version 2023.1 or earlier will no longer actively be supported by SolarWinds. | March 13, 2026: End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for SolarWinds Platform version 2023.1 or earlier will no longer actively be supported by SolarWinds. |
2022.4 | June 4, 2024: End-of-Life (EoL) announcement - Customers on SolarWinds Platform version 2022.4 or earlier should begin transitioning to the latest version of SolarWinds Platform. | July 4, 2024: End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for SolarWinds Platform version 2022.4 or earlier will no longer actively be supported by SolarWinds. | July 4, 2025: End-of-Engineering (EoE) - Service releases, bug fixes, workarounds, and service packs for SolarWinds Platform version 2022.4 or earlier will no longer actively be supported by SolarWinds. |
See the End of Life Policy for information about SolarWinds product life cycle phases. To see EoL dates for earlier SolarWinds Platform versions, see SolarWinds Platform release history.
End of support
This version of SolarWinds Platform no longer supports the following platforms and features.
Microsoft Collaboration Data Objects (CDO) schema for High Availability emails and alerts
CDO schema used for handling emails and alerts is no longer supported for SolarWinds High Availability due to the obsolete .NET standard 2.0. Consider using the native SMTP client for High Availability emails and alerts.
Deprecation notice
The following platforms and features are still supported in the current release. However, they will be unsupported in a future release. Plan on upgrading deprecated platforms, and avoid using deprecated features.
Network Atlas
Network Atlas is deprecated as of Orion Platform 2020.2. It is still available and supported in the current release, but will be removed in a future release. Deprecation is an indication that you should avoid expanded use of this feature and formulate a plan to discontinue using the feature. SolarWinds recommends that you start using Intelligent Maps in the SolarWinds Platform Web Console to display maps of physical and logical relationships between entities monitored by the SolarWinds Platform products you have installed.
Starting with 2024.2, you can import Network Atlas maps to Intelligent Maps. See Import maps.
Legal notices
© 2025 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.