Is CVE-2026-28324 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-28324 being exploited in the wild.

How severe is CVE-2026-28324?

Critical severity, with a CVSS score of 9.8, published 22 September 2026.

Which products and versions are affected?

SolarWinds Observability Self-Hosted <2026.2.3.

Is there a fix for CVE-2026-28324?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-28324 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-28324?

Check whether you run SolarWinds Observability Self-Hosted at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-28324: SolarWinds Observability Self-Hosted unauthenticated remote code execution

Q: Is there a fix for CVE-2026-28324?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-28324 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-28324?

Check whether you run SolarWinds Observability Self-Hosted at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-28324 · Severity: critical · CVSS 9.8 · Published 2026-09-22

SolarWinds Observability Self-Hosted is a monitoring and observability platform that provides visibility into hybrid cloud environments and infrastructure. An unauthenticated attacker can achieve remote code execution on affected systems due to insufficient integrity checks, affecting only non-default and non-secure configurations. This vulnerability allows an attacker to take complete control of the monitoring infrastructure and the systems it oversees.

Technologies: SolarWinds Observability Self-Hosted. Vendors: SolarWinds.

Quick answers

Is CVE-2026-28324 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-28324 being exploited in the wild.
How severe is CVE-2026-28324?: Critical severity, with a CVSS score of 9.8, published 22 September 2026.
Which products and versions are affected?: SolarWinds Observability Self-Hosted <2026.2.3.
Is there a fix for CVE-2026-28324?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-28324 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-28324?: Check whether you run SolarWinds Observability Self-Hosted at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability stems from insufficient integrity checks in SolarWinds Observability Self-Hosted, enabling unauthenticated remote code execution. The attack requires network access and specifically targets installations running in non-default, non-secure configurations. Successful exploitation grants the attacker arbitrary code execution with the privileges of the application, compromising the entire monitoring platform.

Affected products

SolarWinds Observability Self-Hosted <2026.2.3

Timeline

2026-09-22: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.