SolarWinds Observability 2026.2.3 Fixes Two Remote Code Execution Flaws
Quick Answer
The authority published CVE-2026-28324 for SolarWinds Observability Self-Hosted. SolarWinds fixed insufficient integrity checking and an unauthenticated remote-code-execution path that apply under the advisory's non-default or specific communication modes. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory SolarWinds Observability Self-Hosted, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-09-23 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | SolarWinds Observability Self-Hosted |
|---|---|
| Advisory | CVE-2026-28324 / CVE-2026-28325 |
| CVEs | CVE-2026-28324, CVE-2026-28325 |
| Authoritative release date | 2026-09-22 19:11:33.997 UTC |
| Authority revision date | 2026-09-22 19:12:44.576 UTC |
| Affected versions | SolarWinds Observability Self-Hosted 2026.2.2 and earlier; exploitability depends on the communication configuration described by SolarWinds |
| Fixed version | SolarWinds Observability Self-Hosted 2026.2.3 |
| CVSS base score | 8.8 / 9.8 (CVSS v3.1) |
| CVSS severity | High to Critical |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
SolarWinds fixed insufficient integrity checking and an unauthenticated remote-code-execution path that apply under the advisory's non-default or specific communication modes.
What To Validate Now
- Inventory. Locate SolarWinds Observability Self-Hosted deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: SolarWinds Observability Self-Hosted 2026.2.2 and earlier; exploitability depends on the communication configuration described by SolarWinds Do not infer applicability from product family or severity alone.
- Remediate. Apply SolarWinds Observability Self-Hosted 2026.2.3 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

