Database Management

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

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

First published date

5/7/2026 8:20 PM

Last published date

5/7/2026 8:20 PM

Overview

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

Product section

Database Performance Analyzer

Cause

CVE-2026-34480 is due to Apache Log4j Core’s XmlLayout failing to sanitize characters forbidden by XML 1.0 specification, producing an invalid XML output whenever a log message or MDC value contains such characters. The impact of this vulnerability will depend on the StAX implementation.

Resolution

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

SolarWinds Database Performance Analyzer (DPA) is not affected by CVE-2026-34480 because the attack vector, Log4j XmlLayout, does not exist in DPA’s deployment.

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.