# CVE-2025-10538: Authentication Bypass in LG Innotek Camera

> Attackers can bypass authentication to access sensitive camera and user account information on LG Innotek camera models.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/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:** 1 Oct 2025
- **Updated:** 1 Oct 2025
- **Also known as:** GHSA-g79r-wqxw-xp7q

## What is CVE-2025-10538?

CVE-2025-10538 is a high-severity authentication bypass vulnerability in LG Innotek Camera Model LND7210, published on 1 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability exists in LG Innotek camera models LND7210 and LNV7210R. The vulnerability allows a malicious actor to gain access to camera information including user account information.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2025-10538?


## How do I fix CVE-2025-10538?

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

## Is CVE-2025-10538 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10538 and fix it if it is affected.

What it is: CVE-2025-10538 is a high-severity authentication bypass vulnerability in LG Innotek Camera Model LND7210, published on 1 Oct 2025. 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-2025-10538 in the wild and no public exploit code.

Affected product: LG Innotek Camera Model LND7210. 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-2025-10538/ (Markdown: https://insights.sbomify.com/CVE-2025-10538/index.md)
```

## Sources

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

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