# CVE-2026-18611: Data-science-pipelines-operator: dspo: cryptographically weak secret generation (math/rand) for db and s3 credentials

> An unauthenticated attacker can predict database and storage credentials due to weak random number generation, leading to unauthorized access to pipeline artifacts.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-5qmg-pgg7-3rjj

## What is CVE-2026-18611?

CVE-2026-18611 is a high-severity vulnerability in Red Hat OpenShift AI 2.25, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in the Data Science Pipelines Operator. This vulnerability allows an unauthenticated attacker to derive sensitive credentials, such as MariaDB root/user passwords and MinIO access/secret keys, if they can access the MinIO Route or MariaDB Service. The flaw occurs because the operator uses a cryptographically weak pseudo-random number generator (PRNG) to generate these credentials, making them predictable. Successful exploitation could lead to unauthorized access to all pipeline artifacts and metadata, resulting in significant information disclosure.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

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


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

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

## Is CVE-2026-18611 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18611 is a high-severity vulnerability in Red Hat OpenShift AI 2.25, published on 10 Aug 2026. 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-2026-18611 in the wild and no public exploit code.

Affected product: Red Hat OpenShift AI 2.25. 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-18611/ (Markdown: https://insights.sbomify.com/CVE-2026-18611/index.md)
```

## Sources

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

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