SolarWinds Patches Critical RCE Flaws in Observability Self-Hosted
SolarWinds patched two unauthenticated RCE flaws in Observability Self-Hosted, with no exploitation reported.
SolarWinds patched two unauthenticated remote code execution flaws in Observability Self-Hosted, affecting all versions through 2026.2.2 and fixed in 2026.2.3. CVE-2026-28324 (CVSS 9.8) is an insufficient integrity check on non-default, non-secure configurations, and CVE-2026-28325 (CVSS 8.8) is deserialization of untrusted data when a specific communication mode is used. The company also recently fixed CVE-2026-28326 (CVSS 8.8), a hardcoded static key in Access Rights Manager through version 2026.2. SolarWinds said none of these defects are known to be exploited and credited Kai Huang of Armadin for the Observability reports.
- CVE-2026-28324 scores 9.8 and can yield unauthenticated RCE on non-secure configs.
- CVE-2026-28325 scores 8.8 and is unsafe deserialization in a specific communication mode.
- Both affect Observability Self-Hosted through 2026.2.2 and are fixed in 2026.2.3.
- SolarWinds reports no in-the-wild exploitation of these flaws or of ARM bug CVE-2026-28326.
Vulnerabilities mentionedAll →
- CVE-2026-283249.8—SolarWinds Observability Self-Hosted was found to be affected by an unauthenticated remote code execution vulnerability due to the insufficient integrity checkspublished
- CVE-2026-283258.8—SolarWinds Observability Self-Hosted was found to be affected by an unauthenticated remote code execution vulnerability stemming from deserialization of…published
Full article353 words · extracted from securityweek.com · click to collapse
SolarWinds has released patches for two severe vulnerabilities in Observability Self-Hosted that could be exploited for remote code execution (RCE).
Observability Self-Hosted is an on-premises and hybrid IT monitoring solution that provides organizations with unified monitoring across environments, configuration management, and control over operational data and security compliance.
The first flaw, tracked as CVE-2026-28324 (CVSS score of 9.8), is an insufficient integrity check issue leading to RCE on deployments that run non-default and non-secure configurations.
Tracked as CVE-2026-28325 (CVSS score of 8.8), the second bug is described as a deserialization of untrusted data weakness affecting installations configured to use a specific communication mode.
Both security defects, SolarWinds says, can be exploited by remote attackers without authentication.
The vulnerabilities impact all Observability Self-Hosted versions up to 2026.2.2 and were addressed in version 2026.2.3. SolarWinds credited Kai Huang from Armadin for reporting both flaws.
Advertisement. Scroll to continue reading.
Last week, the company patched another unauthenticated RCE bug reported by the security researcher.
Tracked as CVE-2026-28326 (CVSS score of 8.8) and affecting SolarWinds’s Access Rights Manager (ARM), it exists because ARM versions up to 2026.2 contain a hardcoded static key.
SolarWinds makes no mention of any of these security defects being exploited in the wild. Additional information is available on the company’s security advisories page.
Related: Critical WordPress Vulnerability Exploited Immediately After Disclosure
Related: Critical F5 BIG-IP Vulnerability Exploited as Zero-Day
Related: Check Point Patches Exploited Management Server Zero-Day
Related: Nightmare Eclipse Drops New Microsoft Defender Exploit After Revealing Identity
Ionut Arghire is an international correspondent for SecurityWeek.
Daily Briefing Newsletter
Subscribe to the SecurityWeek Email Briefing for the latest cybersecurity threats, trends, and expert insights.
Daily Briefing Newsletter
Subscribe to the SecurityWeek Email Briefing to stay informed on the latest threats, trends, and technology, along with insightful columns from industry experts.
Join as speakers examine the various components of ASM strategy, the push to mandate continuous asset visibility and inventory tools, and the use of red-teaming, bug bounties and pen-tests in modern security programs.
Explore what it takes to operationalize continuous authorization at scale, including the technical, organizational, and cultural changes required.