Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-28324 – Unauthenticated Remote Code Execution – SolarWinds Observability Self-Hosted (versi

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-28324 is a critical unauthenticated remote code execution vulnerability affecting SolarWinds Observability Self-Hosted. The flaw is caused by insufficient integrity checks and can be exploited by an attacker without credentials or user interaction to execute arbitrary code, but only when the affected component is running in a non-default, non-secure configuration. The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: SolarWinds classifies the flaw as CWE-345 (Insufficient Verification of Data Authenticity) — the affected component fails to adequately validate the integrity/authenticity of data or code it processes before acting on it.
  • Trigger conditions: Exploitation requires the SolarWinds Observability Self-Hosted deployment to be running in a "non-default and non-secure configuration." The vendor’s guidance points specifically to unsecured WPM (Web Performance Monitor) Player agent communication as a relevant exposure — deployments that have not configured a Player Password for WPM Player agent traffic are at greater risk.
  • Attack vector: Network-based (AV:N); the vulnerability requires low attack complexity, no privileges, and no user interaction to exploit.
  • Impact: Successful exploitation results in unauthenticated remote code execution, with high impact to confidentiality, integrity, and availability of the affected system (C:H/I:H/A:H) — potentially giving an attacker full control of the host.

Affected software

  • SolarWinds Observability Self-Hosted — all versions 2026.2.2 and below (fixed in 2026.2.3)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade SolarWinds Observability Self-Hosted to version 2026.2.3 or later, which resolves the insufficient integrity check issue.
  • If immediate patching is not possible: Ensure the deployment is not running in the non-default, non-secure configuration described by the vendor — specifically, configure and enforce a Player Password to secure WPM Player agent communication, and review all Observability Self-Hosted components for default or unauthenticated communication channels. These interim steps reduce exposure but do not fully remediate the vulnerability; patching remains the only complete fix.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge