# CVE-2025-40536: SolarWinds Web Help Desk Security Control Bypass

> Unauthenticated attackers can bypass security controls to access restricted functionality in SolarWinds Web Help Desk.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 12 Feb 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-m83h-48rr-jcrh

## What is CVE-2025-40536?

CVE-2025-40536 is a high-severity vulnerability in SolarWinds Web Help Desk, published on 28 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2025-40536?

It affects 1 product.


Products: Solarwinds Web Help Desk.

## How do I fix CVE-2025-40536?

No fix has been published for CVE-2025-40536 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Feb 2026.

## Is CVE-2025-40536 being exploited?

Yes. Attackers have exploited CVE-2025-40536 in the wild since at least 12 Feb 2026.

Public exploit code:

- SolarWinds Web Help Desk unauthenticated RCE (metasploit)
- CVE analysis of CVE-2025-40536, SolarWinds Web Help Desk security control bypass (CVSS 8.1). Covers vulnerability mechanics, attack chain with companion RCE CVEs, Storm-2603 threat actor attribution, MITRE ATT&CK mapping, and detection/remediation guidance for DoD and government environments. (github_poc): https://github.com/victoriaalicex/CVE-2025-40536-Analysis
- SolarWinds Web Help Desk < 12.8.8 Hotfix 1 (HF1) - Security Control Bypass (nuclei): http/cves/2025/CVE-2025-40536.yaml

## Other vulnerabilities in SolarWinds Web Help Desk

- [CVE-2025-40551](https://insights.sbomify.com/CVE-2025-40551/): SolarWinds Web Help Desk Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2025-26399](https://insights.sbomify.com/CVE-2025-26399/): SolarWinds Web Help Desk Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2024-28986](https://insights.sbomify.com/CVE-2024-28986/): SolarWinds Web Help Desk Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2024-28987](https://insights.sbomify.com/CVE-2024-28987/): SolarWinds Web Help Desk Hardcoded Credential (critical 9.1, exploited in the wild)
- [CVE-2026-28323](https://insights.sbomify.com/CVE-2026-28323/): SolarWinds Web Help Desk SAML Authentication Bypass Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40536 and fix it if it is affected.

What it is: CVE-2025-40536 is a high-severity vulnerability in SolarWinds Web Help Desk, published on 28 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-40536 in the wild since at least 12 Feb 2026.

Affected product: SolarWinds Web Help Desk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-40536/ (Markdown: https://insights.sbomify.com/CVE-2025-40536/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-40536
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-40536
- OSV: https://osv.dev/vulnerability/CVE-2025-40536

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-40536/
Summaries are generated and may contain mistakes; the official description above is the record.