# CVE-2026-18058: Missing authorization in Smart Connect Application

> Attackers can manipulate the Smart Connect dashboard via third-party apps to escalate privileges within the system.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-pc3c-j2xg-m4h6

## What is CVE-2026-18058?

CVE-2026-18058 is a high-severity missing authorization vulnerability in Motorola Smart Connect Application, published on 2 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

The mobile Smart Connect dashboard UI was subject to manipulation
by 3rd party apps. When paired with a phishing attack, this manipulation could
result in escalated privileges of an attacker within the system.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-18058 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18058 is a high-severity missing authorization vulnerability in Motorola Smart Connect Application, published on 2 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-18058 in the wild and no public exploit code.

Affected product: Motorola Smart Connect Application. 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-18058/ (Markdown: https://insights.sbomify.com/CVE-2026-18058/index.md)
```

## Sources

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

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