Database Management

Why SolarWinds Database Performance Analyzer (DPA) is not affected by CVE-2026-22741

This article explains why SolarWinds Database Performance Analyzer (DPA) is not affected by CVE-2026-22741.

First published date

9/8/2026 5:36 PM

Last published date

9/8/2026 5:43 PM

Overview

In 2026, the National Institute of Standards and Technology (NIST) published a security bulletin about CVE-2026-22741.

NVD-CVE-2026-22741

Product section

Database Performance Analyzer

Cause

CVE-2026-22741 is related to Spring MVC and WebFlux applications being vulnerable to cache poisoning when resolving static resources. More precisely, an application can be vulnerable when all the following are true: * the application is using Spring MVC or Spring WebFlux * the application is configuring the  resource chain support https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title  with caching enabled * the application adds support for encoded resources resolution * the resource cache must be empty when the attacker has access to the application When all the conditions above are met, the attacker can send malicious requests and poison the resource cache with resources using the wrong encoding. This can cause a denial of service by breaking the front-end application for clients.

Resolution

SolarWinds Database Performance Analyzer (DPA) is not affected by CVE-2026-22741.

This vulnerability requires the application to support encoded resource resolution using EncodedResourceResolver. SolarWinds Database Performance Analyzer (DPA) does not use EncodedResourceResolver within the application.