SolarWinds Observability 2026.2.3 Fixes Two Remote Code Execution Flaws
Tech GuruQuick Answer
SolarWinds Observability Self-Hosted 2026.2.3 fixes two unauthenticated code-execution flaws affecting 2026.2.2 and earlier under specific configurations. CVE-2026-28324 concerns insufficient integrity checks in a non-default, non-secure configuration; CVE-2026-28325 concerns untrusted-data deserialization in a particular communication mode. Do not assume every installation has either prerequisite.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory Self-Hosted versions and communication settings, obtain SolarWinds' configuration-specific guidance, and deploy 2026.2.3 through the supported update path.
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 |
| SolarWinds advisory publication | 2026-09-22 (both advisories) |
| Recorded source timestamp (historical snapshot) | 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
The vendor assigns 28324 a network attack vector and a 9.8 score; 28325 has an adjacent-network vector and an 8.8 score. Both are described as unauthenticated, but the public summaries do not name the relevant non-secure setting or communication mode. An absent setting name is not evidence that a deployment is unaffected.
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. Verify 2026.2.3 is active across the deployment, then check data collection, component communication, alerting and authentication using approved workflows. Preserve relevant logs and configuration evidence before disruptive maintenance.
- 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
Ask SolarWinds to confirm the configuration prerequisites and supported upgrade procedure for the actual installation. Do not enable an insecure mode to test exposure or infer safety solely from default-configuration expectations. No exploit or production upgrade was tested here.
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.
