CVE-2026-111629: IoTSharp IoTSharp

IoTSharp through 3.6.1 Cross-Tenant Data Exposure via Customers and Devices APIs

CVSS 5.3 MediumEPSS 0.0032 · 24th percentile

Published by the CVE Program (CNA: VulnCheck) at 16 Oct 2026, 17:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

Affected products, as the CNA wrote them
Vendor	Product	Versions
IoTSharp	IoTSharp pkg:github/IoTSharp/IoTSharp	affected 3.6.1 and earlier custom Other versions: unaffected

Identifiers

CVE-2026-111629

CNA

VulnCheck

Weakness (CWE)

CWE-639

Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

Severity and exploitation

Score	Rating	CVSS	Vector	Source
5.3	Medium	4.0	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	CNA (VulnCheck)Used for this record
4.3	Medium	3.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N	CNA (VulnCheck)

CISA KEV Not listed.
EPSS 0.0032, the 24th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the CVE Program, published 16 Oct 2026. New records show when each source confirmed them.

Sources

References from the CNA

hackmd.io/@hieuPenguinnn/iotsharp-devices-customers-cross-tenant-idor third-party-advisory
github.com/IoTSharp/IoTSharp/blob/v3.6.1/IoTSharp/Controllers/CustomersController.cs#L164-L177 technical-description
github.com/IoTSharp/IoTSharp/blob/v3.6.1/IoTSharp/Controllers/DevicesController.cs#L490-L507 technical-description
www.vulncheck.com/advisories/iotsharp-through-3.6.1-cross-tenant-data-exposure-via-customers-and-devices-apis third-party-advisory

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.