SEM 2025.2.1 release notes
Release date: July 2, 2025
Security Event Manager 2025.2.1 is a service release providing bug and security fixes for release 2025.2. For information about the 2025.2 release, including EOL notices and upgrade information, see Security Event Manager 2025.2 Release Notes.
New features and improvements in SEM
Last updated:
Other improvements
- Implemented upgrades for improved security.
Fixes
Last updated:
| Case number | Description |
|---|---|
| 01931103 | Offline license activations for new templates can now be done through the customer portal. |
| N/A | SWIP certificate now works across all existing SEM instances. |
| 01901593 | All CPUs are now able to deploy the SEM appliance. |
| 01930712 | Java has been updated on SEM Agent and SEM Manager, so scans against the appliance or agents are no longer reported as vulnerable. |
| 01897353, 01947364 | The connector update process now automatically updates connectors as intended. |
CVEs
Last updated: 6/30/2025
Third Party CVEs
| CVE-ID | Vulnerability Title | Description | Severity |
|---|---|---|---|
| CVE-2024-7348 | Debian Security Advisory DSA-5745-1 | https://lists.debian.org/debian-security-announce/2024/msg00157.html | |
| CVE-2024-10976, CVE-2024-10977, CVE-2024-10978, CVE-2024-10979, | Debian Security Advisory DSA-5812-1 | https://lists.debian.org/debian-security-announce/2024/msg00226.html | |
| CVE-2024-56406 | Debian Security Advisory DSA-5902-1 | https://lists.debian.org/debian-security-announce/2025/msg00064.html | |
| CVE-2023-52857, CVE-2023-52927, CVE-2024-24855, CVE-2024-26656, CVE-2024-26767, CVE-2024-26982, CVE-2024-27056, CVE-2024-35866, CVE-2024-38611, CVE-2024-40973, CVE-2024-42129, CVE-2024-43831, CVE-2024-46772, CVE-2024-47753, CVE-2024-47754, CVE-2024-50056, CVE-2024-50246, CVE-2024-53166, CVE-2024-57977, CVE-2024-58002, CVE-2024-58005, CVE-2024-58079, CVE-2024-58090, CVE-2025-21702, CVE-2025-21712, CVE-2025-21721, CVE-2025-21756, CVE-2025-21838, CVE-2025-21844, CVE-2025-21846, CVE-2025-21848, CVE-2025-21855, CVE-2025-21858, CVE-2025-21859, CVE-2025-21862, CVE-2025-21864, CVE-2025-21865, CVE-2025-21866, CVE-2025-21867, CVE-2025-21871, CVE-2025-21875, CVE-2025-21877, CVE-2025-21878, CVE-2025-21881, CVE-2025-21887, CVE-2025-21891, CVE-2025-21898, CVE-2025-21899, CVE-2025-21904, CVE-2025-21905, CVE-2025-21909, CVE-2025-21910, CVE-2025-21912, CVE-2025-21913, CVE-2025-21914, CVE-2025-21916, CVE-2025-21917, CVE-2025-21918, CVE-2025-21919, CVE-2025-21920, CVE-2025-21922, CVE-2025-21924, CVE-2025-21925, CVE-2025-21926, CVE-2025-21928, CVE-2025-21934, CVE-2025-21935, CVE-2025-21936, CVE-2025-21937, CVE-2025-21938, CVE-2025-21941, CVE-2025-21943, CVE-2025-21944, CVE-2025-21945, CVE-2025-21947, CVE-2025-21948, CVE-2025-21950, CVE-2025-21951, CVE-2025-21956, CVE-2025-21957, CVE-2025-21959, CVE-2025-21960, CVE-2025-21962, CVE-2025-21963, CVE-2025-21964, CVE-2025-21968, CVE-2025-21970, CVE-2025-21971, CVE-2025-21975, CVE-2025-21978, CVE-2025-21979, CVE-2025-21980, CVE-2025-21981, CVE-2025-21986, CVE-2025-21991, CVE-2025-21992, CVE-2025-21993, CVE-2025-21994, CVE-2025-21996, CVE-2025-21997, CVE-2025-21999, CVE-2025-22004, CVE-2025-22005, CVE-2025-22007, CVE-2025-22008, CVE-2025-22010, CVE-2025-22014, CVE-2025-22015 | Debian Security Advisory DSA-5900-1 | https://lists.debian.org/debian-security-announce/2025/msg00062.html | |
| CVE-2023-53034, CVE-2024-36908, CVE-2024-46733, CVE-2024-46742, CVE-2024-46753, CVE-2024-46774, CVE-2024-46816, CVE-2024-46823, CVE-2024-50063, CVE-2025-21853, CVE-2025-22025, CVE-2025-22027, CVE-2025-22033, CVE-2025-22035, CVE-2025-22038, CVE-2025-22040, CVE-2025-22041, CVE-2025-22042, CVE-2025-22044, CVE-2025-22045, CVE-2025-22049, CVE-2025-22050, CVE-2025-22054, CVE-2025-22055, CVE-2025-22056, CVE-2025-22058, CVE-2025-22060, CVE-2025-22063, CVE-2025-22066, CVE-2025-22071, CVE-2025-22072, CVE-2025-22073, CVE-2025-22075, CVE-2025-22079, CVE-2025-22081, CVE-2025-22086, CVE-2025-22088, CVE-2025-22089, CVE-2025-22093, CVE-2025-22095, CVE-2025-22097, CVE-2025-22126, CVE-2025-23136, CVE-2025-23138, CVE-2025-37785, CVE-2025-37838, CVE-2025-38152, CVE-2025-38575, CVE-2025-38637, CVE-2025-39728, CVE-2025-39735 | Debian Security Advisory DSA-5907-1 | https://lists.debian.org/debian-security-announce/2025/msg00069.html | |
| CVE-2025-32728 | In sshd in OpenSSH before 10.0, the DisableForwarding directive does not adhere to the documentation stating that it disables X11 and agent forwarding. | https://security-tracker.debian.org/tracker/CVE-2025-32728 |
We were not affected by the current Java and Open JDK issues. See SolarWinds Products and Oracle Java SE and OpenJDK Vulnerabilities
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.