Database Management

Why SolarWinds Database Performance Analyzer (DPA) is not affected by multiple Apache Tomcat vulnerabilities

This article explains why SolarWinds Database Performance Analyzer (DPA) is not affected by the following Apache Tomcat vulnerabilities: CVE-2026-68525 CVE-2026-68569 CVE-2026-68763 CVE-2026-73180 CVE-2026-66299

First published date

9/15/2026 3:14 PM

Last published date

9/15/2026 3:14 PM

Overview

In 2026, the National Institute of Standards and Technology (NIST) published security bulletins about the following vulnerabilities:

Product section

Database Performance Analyzer

Cause

CVE-2026-68525 is an incorrect Authorization vulnerability in the Apache Tomcat FORM authentication process allows the bypassing of a security constraint that limits user has access to a resource POST but not GET. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.0.M1 through 9.0.120.

CVE-2026-68569 is an improper Authentication vulnerability in Apache Tomcat meant that in some circumstances (e.g. CLIENT-CERT, SPNEGO) that a user would be authenticated even if the user did not exist in the DataSourceRealm. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.0.M1 through 9.0.120.

CVE-2026-68763 is an uncontrolled Resource Consumption vulnerability in Apache Tomcat via an allocation leak in the HTTP/2 backlog tracking when a stream is reset This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.39 through 9.0.120.

CVE-2026-73180 is an insufficient Session Expiration vulnerability in Apache Tomcat meant that if the session ID for an authenticated HTTP session was changed after a WebSocket connection had been established under that authenticated HTTP session, the WebSokcet session would not be closed as required by the Jakarta WebSocket specification when the HTTP session ended. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.0.M1 through 9.0.120.

CVE-2026-66299 is an uncontrolled Resource Consumption vulnerability in the Apache Tomcat WebSocket chat example. This issue affects Apache Tomcat: from 11.0.0-M20 through 11.0.24, from 10.1.24 through 10.1.57, from 9.0.89 through 9.0.120.

Resolution

SolarWinds Database Performance Analyzer (DPA) is not affected by CVE-2026-68525, CVE-2026-68569, CVE-2026-68763, CVE-2026-73180, and CVE-2026-66299.

CVE-2026-68525: DPA does not use the Apache Tomcat built-in FORM authentication. The application implements its own authentication/authorization entirely via Spring Security filter chain, therefore DPA is not impacted with this vulnerability.

CVE-2026-68569: DPA does not use container-managed authentication; it uses its own Spring Security-based authentication.

CVE-2026-68763: This vulnerability requires an application to have HTTP/2 enabled via Http2Protocol/upgradeProtocol on a connector in server.xml file. The HTTP/2 protocol is not enabled in DPA's Tomcat configuration.

CVE-2026-73180: This vulnerability requires an application to use Jakarta WebSocket endpoints established under an authenticated HTTP session. DPA does not implement any WebSocket endpoints.

CVE-2026-66299: DPA is not affected by this vulnerability as it does not bundle the Apache Tomcat WebSocket chat example application as part of the product.

While the component’s presence is flagged by dependency scanning tools, our analysis shows there is no associated security risk.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.