# CVE-2026-112250: Cleartext Storage of Windows Service Account Password in BRAIN2 Setup Log Files


- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-p6ch-jxpp-q2jv

## What is CVE-2026-112250?

CVE-2026-112250 is a medium-severity vulnerability in Bizerba SE & Co. KG BRAIN2, published on 26 Oct 2026. 

### Official description

A vulnerability has been identified in
BRAIN2 versions up to and including version 3.09. Under specific installation
conditions, the password of a Windows service account may be written in
cleartext to a setup log file. The issue occurs when Microsoft SQL Server
access is configured using Integrated Security and the Windows account intended
to run the BRAIN2 MainService is specified during execution of the BRAIN2
installation wizard. The setup log file is stored in the
temporary directory of the Windows administrator performing the installation.
This directory is not accessible to standard Windows users and can generally
only be accessed by users with administrative privileges. Successful exploitation could result in the
disclosure of credentials belonging to the configured BRAIN2 service account.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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


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

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

## Is CVE-2026-112250 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112250 is a medium-severity vulnerability in Bizerba SE & Co. KG BRAIN2, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112250 in the wild and no public exploit code.

Affected product: Bizerba SE & Co. KG BRAIN2. 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-112250/ (Markdown: https://insights.sbomify.com/CVE-2026-112250/index.md)
```

## Sources

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

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