Skip to main content

Lansweeper lsrunase CVE-2026-39031

MEDIUM
Use of Hard-coded Cryptographic Key (CWE-321)
2026-06-26 mitre
5.5
CVSS 3.1 · Vendor: mitre
Share

Severity by source

Vendor (mitre) PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
vuln.today AI
5.5 MEDIUM

Local filesystem read with low privileges deterministically recovers credentials; no integrity or availability impact applies.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
Analysis Generated
Jul 22, 2026 - 20:10 vuln.today
CVE Published
Jun 26, 2026 - 00:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

AnalysisAI

Trivial credential recovery is possible against Lansweeper lsrunase 2.0 and lsencrypt 2.0 due to RC4 encryption with a hardcoded 142-byte static key embedded in the binaries. Any local attacker who can read the encrypted credential store can recover plaintext passwords using a single SHA-1 hash computation followed by RC4 decryption - no brute force, dictionary attack, or key material theft required. A public proof-of-concept exists on GitHub (no public exploit identified as confirmed actively exploited at time of analysis), and SSVC classifies this as non-automatable with partial technical impact, making it a targeted but deterministic threat to environments that rely on these utilities for credential storage.

Technical ContextAI

CWE-321 (Use of Hard-coded Cryptographic Key) governs this flaw. RC4 (Rivest Cipher 4) is a stream cipher long considered cryptographically broken; its use here is compounded by a static 142-byte key compiled into the lsrunase 2.0 and lsencrypt 2.0 binaries, meaning the key is identical across every deployment worldwide. An additional design flaw stores an 8-character prefix alongside the ciphertext in cleartext, providing known-plaintext material that would further facilitate decryption. The decryption procedure requires only a SHA-1 hash operation and one pass of RC4 - both trivially implemented in any scripting language. Lansweeper is an IT asset management and network discovery platform; lsrunase and lsencrypt appear to be credential-handling utilities within that ecosystem. The NVD CPE entry is listed as 'n/a', indicating the affected product has not been formally catalogued, which limits automated scanner coverage of this vulnerability.

RemediationAI

No vendor-released patch identified at time of analysis. Organizations should immediately audit whether lsrunase 2.0 or lsencrypt 2.0 are in use and what credentials they protect. As a primary compensating control, discontinue use of these utilities for credential storage and migrate to a supported secrets management solution (e.g., a password vault or OS credential store). If immediate migration is not feasible, restrict filesystem read access to any encrypted credential files produced by these utilities to the minimum necessary accounts, reducing the pool of potential low-privilege attackers who can exploit the flaw - note this does not eliminate the risk if any authorized local user is a threat actor. Additionally, rotate any passwords that may have been encrypted by these tools, since there is no way to determine retrospectively whether an attacker has already decrypted them. Monitor the VulDB advisory at https://vuldb.com/vuln/374417 and the researcher disclosure at https://usermode.net/cve/lansweeper_lsrunase2_lsencrypt2_cve.pdf for any vendor response or patch release.

More in N A

View all
CVE-2024-51092 CRITICAL POC
9.1 May 08

LibreNMS before 24.10.0 allows a remote attacker to execute arbitrary code via OS command injection involving AboutContr

CVE-2025-15684 MEDIUM POC
5.5 Aug 12

Reachable assertion in Open5GS up to version 2.7.6 allows remote unauthenticated attackers to crash the Diameter CER han

CVE-2024-45257 HIGH POC
7.3 May 08

A Command Injection issue in the payload build page in BYOB (Build Your Own Botnet) 2.0 allows attackers to execute arbi

CVE-2025-15687 LOW POC
2.1 Aug 12

Denial of service in Open5GS 2.7.6 and earlier allows network-adjacent attackers with low-privilege Diameter Gx peer acc

CVE-2025-15686 LOW POC
2.1 Aug 12

Denial of service in Open5GS HSS (Home Subscriber Server) versions 2.7.0 through 2.7.6 is triggered remotely by manipula

CVE-2025-67888 HIGH POC
7.3 May 08

Remote command injection in Control Web Panel allows unauthenticated attackers to execute arbitrary OS commands as root

CVE-2024-53326 HIGH POC
7.3 May 08

LINQPad before 5.52.01 Pro edition is vulnerable to Unsafe Deserialization in LINQPad.AutoRefManager::PopulateFromCache(

CVE-2026-38360 CRITICAL POC
9.8 May 08

Remote code execution in dash-uploader (Python package for Plotly Dash) versions 0.1.0 through 0.7.0a2 allows unauthenti

CVE-2026-30623 CRITICAL POC
9.8 Jul 15

Command injection in LiteLLM 1.18.10 lets attackers who can configure MCP (Model Context Protocol) servers supply arbitr

CVE-2026-67917 CRITICAL POC
9.8 Aug 17

SQL injection in AzuraCast's backup restore flow (versions up to and including 0.23.7) lets an attacker achieve privileg

CVE-2026-75337 CRITICAL POC
9.8 Aug 27

Arbitrary file read in Yu AI Code Mother v4.3 lets anonymous, remote attackers retrieve files outside the intended previ

CVE-2026-31072 CRITICAL POC
9.8 May 19

Remote code execution in APScheduler (all versions through 3.10.x and 4.0.0a5) is achievable when applications deseriali

Share

CVE-2026-39031 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy