Skip to content
Fencer Vulns
high 8.1

CVE-2025-40536 kev in the critical feed json

SolarWinds Web Help Desk Security Control Bypass Vulnerability

published 2026-01-28 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-206418

cvss
8.1
version 3.1, CNA
cisa kev
Exploited
added 2026-02-12
epss
73.6%
EPSS 73.6% chance of exploitation in 30 days, percentile 99.4%
public exploits
1
Metasploit, plus a Nuclei check

Summary

SolarWinds Web Help Desk was found to be susceptible to a security control bypass vulnerability that if exploited, could allow an unauthenticated attacker to gain access to certain restricted functionality.

Patch / fix

cisa required action Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

  • solarwinds web_help_desk 2026.1

Timeline

  1. First public exploit (Metasploit exploit/multi/http/solarwinds_webhelpdesk_rce)
  2. Published
  3. Added to CISA KEV
  4. CISA SSVC: exploitation active
  5. CISA patch deadline

Known exploited

Added
8 mo ago
Patch by
2026-02-15 (8 mo ago)
Ransomware
Not known
Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor, product
SolarWinds, Web Help Desk
CISA name
SolarWinds Web Help Desk Security Control Bypass Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
8 mo ago

Exploit prediction

73.56% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • SolarWinds Web Help Desk

Classification

Weakness
  • CWE-693 Protection Mechanism Failure

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.