basicsecurity.net
Proof, not just disclosure.
Threats / SolarWinds / CVE-2025-40551
CVE-2025-40551 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

SolarWinds Web Help Desk vulnerability

SolarWinds Web Help Desk contains a deserialization vulnerability allowing unauthenticated remote code execution on affected hosts.

Verdict

Today item — known-exploited.

An attacker can exploit unsafe deserialization of untrusted data in Web Help Desk to execute arbitrary commands without authentication. Active exploitation in the wild increases risk.

CISA KEV Yes · 2026-02-033EPSS 0.8413 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-02-03).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.8413 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: SolarWinds, Web Help Desk. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-502 Deserialization of Untrusted Data — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious serialized object and send it to the Web Help Desk application without credentials.
Business
The organization's Help Desk system is exposed to attack from any network-connected user.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
The application deserializes my untrusted payload, instantiating malicious code during object reconstruction.
Business
Deserialization flaws bypass application logic and security controls designed for normal operation.
3

Lateral reach — past segmentation narrative 3

Attacker
My payload executes arbitrary commands with the privileges of the Web Help Desk process on the host.
Business
The attacker gains direct command execution on critical support infrastructure.
4

Data at risk — exfiltration narrative 4

Attacker
I establish persistence, exfiltrate data, or pivot to other systems on the network.
Business
The breach expands beyond Help Desk to compromise customer data, internal systems, and business continuity.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 3 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by SolarWinds (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by SolarWindsCNA