# CVE-2026-64635: Open redirect in Service Provider Console

> An unauthenticated attacker can manipulate the password reset link domain to steal reset codes and take over user accounts.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-r6vm-r9vq-cmwh

## What is CVE-2026-64635?

CVE-2026-64635 is a medium-severity vulnerability in Veeam Service Provider Console, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper handling of the returnUrl parameter in the Forgot Password function of Veeam Service Provider Console allows an unauthenticated attacker to control the domain of the generated password reset link. When the targeted user clicks the link delivered by email, the reset code is transmitted to an attacker-controlled host, allowing the attacker to take over the account.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2026-64635?


## How do I fix CVE-2026-64635?

No fix has been published for CVE-2026-64635 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-64635 being exploited?

There is no known exploitation of CVE-2026-64635 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64635 and fix it if it is affected.

What it is: CVE-2026-64635 is a medium-severity vulnerability in Veeam Service Provider Console, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-64635 in the wild and no public exploit code.

Affected product: Veeam Service Provider Console. 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-2026-64635/ (Markdown: https://insights.sbomify.com/CVE-2026-64635/index.md)
```

## Sources

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

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