# CVE-2026-116184: OpenRemote before 1.31.0 Cross-Realm Gateway Impersonation via Websocket


- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 25 Oct 2026
- **Also known as:** GHSA-2j4x-qh6q-q8mm, GHSA-jrwj-grf5-9fv3

## What is CVE-2026-116184?

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

### Official description

OpenRemote before 1.31.0 contains an authorization bypass vulnerability that allows realm admins to impersonate gateways in other realms because GatewayService only checks the gateway ID, not the realm. Attackers with WRITE:ADMIN in one realm can create a service user named after another realm's gateway ID to overwrite its descendant assets and open SSH tunnels into its local network.

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

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


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

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

## Is CVE-2026-116184 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116184 is a low-severity vulnerability in openremote core, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116184 in the wild and no public exploit code.

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

## Sources

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

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