# CVE-2026-92680: Araxis Merge insufficiently protected credentials

> An authenticated local attacker can retrieve and decrypt stored remote server credentials from the Windows registry due to insufficient cryptographic protection.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 26 Sep 2026
- **Also known as:** GHSA-hfv3-23j2-3cp6

## What is CVE-2026-92680?

CVE-2026-92680 is a medium-severity vulnerability in Araxis Merge, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Araxis Merge for Windows version 2011.4074 through 2026.0 stores user-configured credentials for remote servers in the Windows registry and does not apply sufficient cryptographic protection. An authenticated, non-administrative attacker could retrieve and unencrypt all credentials the target user has stored in Merge.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-92680 being exploited?

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

Public exploit code:

- Proof-of-Concept for CVE-2026-92680, the insecurely protected credentials vulnerability affecting Araxis Merge. (github_poc): https://github.com/grepstrength/CVE-2026-92680

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92680 is a medium-severity vulnerability in Araxis Merge, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92680 in the wild and no public exploit code.

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

## Sources

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

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