Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.1%top 98%

CVE-2026-39031: n/a

0
Medium
VulnerabilityCVE-2026-39031cvecve-2026-39031
Published: 06/26/2026 (06/26/2026, 00:00:00 UTC)
Source: CVE Database V5

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.

CVSS v3.1

Score 5.5medium

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/03/2026, 22:27:06 UTC

Technical Analysis

The Lansweeper lsrunase 2.0 and lsencrypt 2.0 components employ RC4 encryption with a fixed 142-byte static key array to protect credentials. Because the encryption key is hardcoded and an 8-character prefix is stored in plaintext, an attacker with local access can decrypt any stored password by performing a single SHA-1 hash and RC4 decryption operation, bypassing the need for brute force. This vulnerability is identified as CWE-321 (Use of Hard-coded Cryptographic Key). There is no available vendor advisory or patch information at this time.

Potential Impact

An attacker with local access can recover plaintext passwords from encrypted credentials without requiring brute force, potentially leading to credential compromise. The confidentiality of stored credentials is directly impacted. There is no indication of impact on integrity or availability. No known exploits are reported in the wild.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict local access to trusted users only and monitor for unauthorized access attempts. Avoid relying on the affected encryption method for sensitive credential storage.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2026-04-06T00:00:00.000Z
Cvss Version
null
State
PUBLISHED
Remediation Level
null

Threat ID: 6a3ee65a27e9c79719e9ee31

Added to database: 06/26/2026, 20:51:38 UTC

Last enriched: 07/03/2026, 22:27:06 UTC

Last updated: 08/10/2026, 00:41:15 UTC

Views: 89

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses