# CVE-2025-26381: OpenBlue Mobile Web Application configuration issue for optional for OpenBlue Workplace (formerly FM Systems)

> Attackers can gain unauthorized access to sensitive information due to a configuration issue in the OpenBlue Workplace mobile web application.

- **Severity:** Medium 6.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Dec 2025
- **Updated:** 17 Dec 2025
- **Also known as:** GHSA-wv84-fc78-m2qm

## What is CVE-2025-26381?

CVE-2025-26381 is a medium-severity missing authorization vulnerability in Johnson Controls OpenBlue Workplace (formerly FM Systems), published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Successful exploitation of this vulnerability could allow an attacker to gain unauthorized access to sensitive information.

Weakness: CWE-425 (Direct Request)

## Which versions are affected by CVE-2025-26381?


## How do I fix CVE-2025-26381?

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

## Is CVE-2025-26381 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26381 and fix it if it is affected.

What it is: CVE-2025-26381 is a medium-severity missing authorization vulnerability in Johnson Controls OpenBlue Workplace (formerly FM Systems), published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26381 in the wild and no public exploit code.

Affected product: Johnson Controls OpenBlue Workplace (formerly FM Systems). 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-2025-26381/ (Markdown: https://insights.sbomify.com/CVE-2025-26381/index.md)
```

## Sources

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

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