# CVE-2026-116186: OpenRemote before 1.31.0 Gateway Authorization Bypass via Reversible mapAssetId


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-8pjc-wq2p-3xr4, GHSA-pqvx-525p-jf88

## What is CVE-2026-116186?

CVE-2026-116186 is a low-severity vulnerability in openremote core, published on 25 Oct 2026. 

### Official description

OpenRemote core (openremote-manager) before 1.31.0 does not perform realm or gateway-descendant authorization on inbound edge gateway events and maps event asset IDs only through the reversible GatewayConnector.mapAssetId transform. An attacker controlling a registered gateway can craft pre-image IDs in AttributeEvent or DELETE AssetEvent messages to overwrite attributes on, or delete, assets in any realm, breaking tenant isolation.

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

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


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

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

## Is CVE-2026-116186 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116186 is a low-severity vulnerability in openremote core, published on 25 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116186 exists.

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

## Sources

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

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