CVE-2026-39031

Lansweeper Credential Storage RC4 Key Exposure

Published Jun 26, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

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 next to the ciphertext. This flaw lets an attacker with local access recover any stored password to plaintext using a single SHA‑1 hash and an RC4 decryption operation, with no brute‑force effort required.

Affected Systems

The affected products are Lansweeper lsrunase 2.0 and lsencrypt 2.0, as referenced in the advisory sources. No further vendor or version details are available beyond the version numbers provided.

Risk and Exploitability

The CVSS score of 5.5 indicates moderate severity. The exploit can be carried out by any local user who has read access to the credentials file. Only a single SHA‑1 hash compute and RC4 decryption are needed, which can be performed in milliseconds, so the attack is trivial for a local attacker. The EPSS score is below 1%, indicating a very low probability that a non‑commercial attack will occur in the near term, and the vulnerability is not listed in the CISA KEV catalog. However, successful exposure of passwords could still allow further privilege escalation or unauthorized access.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Check the Lansweeper vendor site or support portal for an updated release that replaces the RC4 encryption and removes hardcoded key usage.
  • If no patch is available, disable or remove local credential storage from the lsrunase and lsencrypt components, or reconfigure the application to use a secure OS‑managed keystore.
  • Restrict local file‑system access to the Lansweeper installation directories to limit privilege escalation risks.

Generated by OpenCVE AI on June 29, 2026 at 17:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Lansweeper
Lansweeper lsencrypt
Lansweeper lsrunase
Vendors & Products Lansweeper
Lansweeper lsencrypt
Lansweeper lsrunase
Type Values Removed Values Added
Title Lansweeper Credential Storage RC4 Key Exposure
Type Values Removed Values Added
Title Local Credential Disclosure via Hardcoded RC4 Key in Lansweeper lsrunase 2.0 and lsencrypt 2.0
Weaknesses CWE-327
CWE-330
Type Values Removed Values Added
Weaknesses CWE-321
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Local Credential Disclosure via Hardcoded RC4 Key in Lansweeper lsrunase 2.0 and lsencrypt 2.0
Weaknesses CWE-327
CWE-330
Type Values Removed Values Added
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.
References
Weaknesses
  • CWE-321

    Use of Hard-coded Cryptographic Key

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Jun 29, 2026, 1:37 PM
Reserved
Apr 6, 2026, 12:00 AM
Status
Deferred
Published
Jun 26, 2026, 9:16 PM
Modified
Jun 29, 2026, 7:27 PM