Netsweeper is pleased to announce the Netsweeper 8.2.14 GA Release. This release continues to improve and stabilize the Netsweeper 8.2 product. All customers are strongly encouraged to upgrade to the 8.2.14 GA release in their test environments and proceed to upgrading their production deployments. The 8.2.14 GA release only fixes critical variances that impact customer production environments.
Moving forward, Netsweeper does not plan to create any future 8.2 GA releases; as the 9.1 release is expected to achieve the GA milestone soon. After upgrading production environments to this release, customers should start using the 9.1 EA release in their test environments and begin to plan the migration of their production environments to the new Netsweeper 9.1 platform. For an ongoing list of the new features and improvements in the 9.1 release, please refer to our 9.1 New Features documentation.
If you have any questions or concerns about planning an upgrade to this release, please contact Netsweeper Technical Support (support@netsweeper.com).
See Also
8.2 New Features Combined and Summary of 8.2 New Features
Downloads
https://repo.netsweeper.com/releases/centos/iso/netsweeper-el8-x86_64-8.2.14-1.iso (8.2.14 md5 checksum) (8.2.14 sha256 signature)
Chagnelog 8.2.14
| Issue | Ticket | Summary |
|---|---|---|
| Bug | NS-2585 | An empty server_guid.php file coule result in a '500 Internal Server Error' on both the Services and Status windows in the 8.2 release. |
| Bug | NS-2594 | Advanced Filters were unable to be shared with other Accounts in the 8.2 and 9.1 releases. |
| Bug | NS-2597 | Stopping the nginx daemon on a remote server would result in the Status window showing the NSUp2d service as 'not responding'. We now use SNMP to check the status of the NSUp2d service and no longer rely on nginx. |
| Bug | NS-2612 | The NSRoutes service would not cleanup expired IP addresses when the DNS response returned completely new IP addresses. New log entries have been added to improve debugging. |
| Bug | NS-2620 | We did not remotely log the 'orgid' with the default Policy Service config and would not unless the remote logger fields were set. |
| Bug | NS-2623 | If a single log field was larger then the log entry buffer, we would flush to disk and overwrite memory, causing the Logger server to abort and restart. |
| Bug | NS-2625 | The MySQL Database password could get printed in the output when saving changes to Webadmin Settings. |
| Bug | NS-2626 | The Policy Service configuration (nsd.conf) would fail to dump merged fields into the 'Running Config' (nsd.nsd.conf). |
| Bug | NS-2683 | Multiple WebAdmin users could inadvertantly share the same Request Log session if the sessions were created in the same second, from versions 3.1 to 9.1.10. This can potentially leak Log information from one Account to another while changing Filters. |
| Bug | NS-2684 | SysOp Accounts with access to System Wide, Filter Bypass and Category Lists could remove Lists from the Processing Steps they did not have access to. |
| Bug | NS-2699 | The Netsweeper 8.2 to 9.1.10 releases would display the 'Lists' status as failed with the NSProxyKWScan List showing as version 0 if the Serial did not have that List enabled. |
| Bug | NS-2708 | Directory Sync was using the 'log4j 2.17.2' package, which was impacted by CVE-2026-34480. We have upgraded log4j to version 2.26.0. |
| Bug | NS-2720 | The 'Lets Encrypt' Certificate did not deploy the Full Chain for nginx, NSD, and other services, deploying the Cert manually would not regenerate the default Certificate. |
Copyright © 2026 Netsweeper Inc. All rights reserved.
Confidential and Private information. Distribution of the information contained herein is strictly prohibited.