# CVE-2026-124436: OpenRemote before 1.32.2 Improper Authorization Allows Realm Admins to Modify Global Resources


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-cm8m-mhv8-9v9v, GHSA-gf33-2772-8gw3

## What is CVE-2026-124436?

CVE-2026-124436 is a high-severity vulnerability in openremote core, published on 8 Nov 2026. 

### Official description

OpenRemote before 1.32.2 contains an improper authorization vulnerability that allows realm administrators to access and modify global resources by calling admin endpoints lacking super administrator checks. Attackers can change the global keycloakUrl via /configuration/manager to redirect other realms' console authentication for credential phishing, inject CSS, replace map tiles, and delete logs.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-124436 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124436 is a high-severity vulnerability in openremote core, published on 8 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124436 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-124436/ (Markdown: https://insights.sbomify.com/CVE-2026-124436/index.md)
```

## Sources

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

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