# CVE-2026-39031: Hardcoded credentials in n/a

> Local attackers can recover encrypted credentials to plaintext due to hardcoded RC4 keys in Lansweeper utilities, compromising stored secrets.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A: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:** 26 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-22h8-g6qj-g2g4

## What is CVE-2026-39031?

CVE-2026-39031 is a medium-severity vulnerability in n/a, published on 26 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Lansweeper lsrunase 2.0 and lsencrypt 2.0 use RC4 encryption with a hardcoded 142-byte static key array to encrypt credentials. An 8-character prefix is stored in cleartext alongside the ciphertext. This allows an attacker with local access to recover any encrypted password to plaintext using a single SHA-1 hash and RC4 decryption operation, with no brute force required.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2026-39031 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39031 exists.

Public exploit code:

- CVE-2026-39031 — offline plaintext password recovery for Lansweeper lsrunase 2.0 / lsencrypt 2.0 via a hardcoded RC4 key. PoC + technical advisory. (github_poc): https://github.com/user6400/cve-2026-39031-lansweeper-lsrunase2-lsencrypt2

## Fix prompt for AI coding agents

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

What it is: CVE-2026-39031 is a medium-severity vulnerability in n/a, published on 26 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39031 exists.

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

## Sources

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

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