# CVE-2026-111629: IoTSharp through 3.6.1 Cross-Tenant Data Exposure via Customers and Devices APIs

> Authenticated users can access other tenants' customer and device data due to missing tenant scoping in API handlers.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-42g8-wcwc-865r

## What is CVE-2026-111629?

CVE-2026-111629 is a medium-severity missing authorization vulnerability in IoTSharp, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IoTSharp through 3.6.1 contains an insecure direct object reference vulnerability that allows any authenticated user to read other tenants' data because Customers and Devices API handlers do not scope queries to the caller's tenant. Attackers can self-register through the anonymous AccountController.Create endpoint and supply other tenants' GUIDs to read customer contact details, device inventories and device attribute telemetry.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-111629 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111629 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111629 is a medium-severity missing authorization vulnerability in IoTSharp, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111629 exists.

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

## Sources

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

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