# CVE-2026-50641: Plaintext password storage in Streamsoft Business Intelligence

> Streamsoft Business Intelligence stores user passwords in plaintext, allowing attackers with database access to steal credentials and compromise accounts.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-v8g3-5gq5-j8gw

## What is CVE-2026-50641?

CVE-2026-50641 is a high-severity vulnerability in Streamsoft Business Intelligence, published on 29 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Streamsoft Business Intelligence (BI) stores users' passwords in plaintext form in the database

This issue was fixed in version 6.8.0.0, users were also requested to change their password on the first login.

Weakness: CWE-256 (Plaintext Storage of a Password)

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


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

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

## Is CVE-2026-50641 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50641 is a high-severity vulnerability in Streamsoft Business Intelligence, published on 29 Jul 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-50641 in the wild and no public exploit code.

Affected product: Streamsoft Business Intelligence. 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-50641/ (Markdown: https://insights.sbomify.com/CVE-2026-50641/index.md)
```

## Sources

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

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