# CVE-2026-27874: Hardcoded credentials in EasyIO FS32

> Attackers can exploit hard-coded credentials in Johnson Controls EasyIO FS32 to gain unauthorized access and control over the building automation system.

- **Severity:** Medium 5.0 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-x8cv-cg58-3683

## What is CVE-2026-27874?

CVE-2026-27874 is a medium-severity vulnerability in Johnson Controls EasyIO FS32, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

: Use of Hard-coded Credentials vulnerability in Johnson Controls EasyIO FS32 allows : Exploitation of Default or Hard-coded Credentials.

This issue affects EasyIO FS32: before 3.0b63.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-27874 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27874 is a medium-severity vulnerability in Johnson Controls EasyIO FS32, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-27874 in the wild and no public exploit code.

Affected product: Johnson Controls EasyIO FS32. 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-27874/ (Markdown: https://insights.sbomify.com/CVE-2026-27874/index.md)
```

## Sources

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

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