{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39031 exists.","fix":"No fix has been published for CVE-2026-39031 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-39031 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39031 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-39031/ (Markdown: https://insights.sbomify.com/CVE-2026-39031/index.md)","id":"CVE-2026-39031","markdown":"https://insights.sbomify.com/CVE-2026-39031/index.md","name":"CVE-2026-39031","record":{"aliases":["GHSA-22h8-g6qj-g2g4"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Lansweeper asset management","requires_auth":"low_privilege","summary":"Local attackers can recover encrypted credentials to plaintext due to hardcoded RC4 keys in Lansweeper utilities, compromising stored secrets.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-06-22","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-06-22T17:02:25Z","kind":"github_poc","ref":"https://github.com/user6400/cve-2026-39031-lansweeper-lsrunase2-lsencrypt2","stars":0,"title":"CVE-2026-39031 — offline plaintext password recovery for Lansweeper lsrunase 2.0 / lsencrypt 2.0 via a hardcoded RC4 key. PoC + technical advisory."}],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2026-39031","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2026-39038"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2026-39020"},"products":["n/a"],"published":"2026-06-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-29","vendors":["n/a"]},"summary":"Local attackers can recover encrypted credentials to plaintext due to hardcoded RC4 keys in Lansweeper utilities, compromising stored secrets.","url":"https://insights.sbomify.com/CVE-2026-39031/"}