# CVE-2026-10839: Open redirection vulnerability in Password Manager

> Attackers can redirect authenticated users to malicious sites via manipulated X-Forwarded-Host headers in the Password Manager authentication system.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA: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:** 17 Jun 2026
- **Updated:** 17 Jun 2026
- **Also known as:** GHSA-f2w7-fcqj-g66g

## What is CVE-2026-10839?

CVE-2026-10839 is a medium-severity vulnerability in Password Manager, published on 17 Jun 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

Open redirection vulnerability in the authentication system allows an attacker to use manipulated values in the X-Forwarded-Host header to alter the URLs generated by the application. A successful exploit could redirect authenticated users to malicious sites following login procedures or interaction with the interface, resulting in limited impact on confidentiality and integrity.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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


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

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

## Is CVE-2026-10839 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10839 is a medium-severity vulnerability in Password Manager, published on 17 Jun 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-10839 in the wild and no public exploit code.

Affected product: Password Manager. 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-10839/ (Markdown: https://insights.sbomify.com/CVE-2026-10839/index.md)
```

## Sources

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

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