Threats / SolarWinds / CVE-2024-28986
CVE-2024-28986
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
SolarWinds Web Help Desk vulnerability
SolarWinds Web Help Desk contains a deserialization of untrusted data vulnerability enabling remote code execution. The flaw has been exploited in the wild.
Verdict
Today item — known-exploited.
An unauthenticated or low-privileged attacker can exploit unsafe deserialization in Web Help Desk to execute arbitrary code on affected systems. Active exploitation in the wild elevates risk despite the absence of a CVSS score.
01
Is it exploitable?
— the evidence, ranked above the scoreReported 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 2024-08-15).
Probability (EPSS)
EPSS 0.84446 — 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.
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.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious serialized object and send it to the vulnerable deserialization endpoint in Web Help Desk.
Business
The organization's help desk infrastructure becomes a beachhead for lateral movement and data exfiltration.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger deserialization of my payload, achieving code execution with the privileges of the Web Help Desk service.
Business
Attackers gain persistent access to internal support systems and customer-facing ticketing data.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish a reverse shell or deploy additional malware to maintain persistence and expand my foothold.
Business
The organization faces operational disruption, potential data breach, and reputational damage from compromised support infrastructure.
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’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by SolarWindsCNA
Credited with finding itInmarsat Government / Viasatfinder