# CVE-2026-15929: SQL injection in SmartShare

> An SQL injection vulnerability in LG SmartShare allows attackers to manipulate database queries, potentially leading to unauthorized data access or modification.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-g2xh-vghf-6g4h

## What is CVE-2026-15929?

CVE-2026-15929 is a high-severity SQL injection vulnerability in LG Electronics SmartShare, published on 30 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in LG Electronics SmartShare allows SQL Injection.

This issue affects SmartShare: through 2.3.1712.1202, which is supported on Microsoft Windows 10 and earlier versions.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-15929 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15929 is a high-severity SQL injection vulnerability in LG Electronics SmartShare, published on 30 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15929 in the wild and no public exploit code.

Affected product: LG Electronics SmartShare. 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-15929/ (Markdown: https://insights.sbomify.com/CVE-2026-15929/index.md)
```

## Sources

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

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