# CVE-2026-85147: Lightstar｜SmartIT Desktop Manager - Use of Hard-coded Credentials

> Unauthenticated attackers can extract hard-coded credentials from the source code to retrieve AES keys, compromising communication security.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-fq5x-c72w-p2cq

## What is CVE-2026-85147?

CVE-2026-85147 is a high-severity vulnerability in Lightstar SmartIT Desktop Manager, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SmartIT Desktop Manager developed by Lightstar has a Use of Hard-coded Credentials vulnerability. Unauthenticated remote attackers can obtain a specific password from the source code, which can be used to retrieve the AES encryption key used for communication.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-85147 being exploited?

There is no known exploitation of CVE-2026-85147 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85147 is a high-severity vulnerability in Lightstar SmartIT Desktop Manager, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85147 in the wild and no public exploit code.

Affected product: Lightstar SmartIT Desktop Manager. 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-85147/ (Markdown: https://insights.sbomify.com/CVE-2026-85147/index.md)
```

## Sources

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

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