# CVE-2026-70413: Hardcoded credentials in Live Optics Collector

> A local low-privileged attacker can exploit hard-coded credentials in Dell Live Optics Collector to expose sensitive information.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-gfqq-cvw7-p496

## What is CVE-2026-70413?

CVE-2026-70413 is a medium-severity vulnerability in Dell Live Optics Collector, published on 28 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Dell Live Optics Collector, versions prior to 27.2.13.310, contain(s) a Use of Hard-coded Password vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Information exposure.

Weakness: CWE-259 (Use of Hard-coded Password)

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


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

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

## Is CVE-2026-70413 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70413 is a medium-severity vulnerability in Dell Live Optics Collector, published on 28 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-70413 in the wild and no public exploit code.

Affected product: Dell Live Optics Collector. 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-70413/ (Markdown: https://insights.sbomify.com/CVE-2026-70413/index.md)
```

## Sources

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

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