# CVE-2026-3161: IBM Cloud Pak System Risky Cryptographic Algorithm

> Attackers can decrypt sensitive information due to weak cryptographic algorithms in IBM Cloud Pak System.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 19 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-2pff-h2q8-4jc4

## What is CVE-2026-3161?

CVE-2026-3161 is a medium-severity vulnerability in IBM Cloud Pak System, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Cloud Pak System 2.3.6.0, and 2.3.6.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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


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

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

## Is CVE-2026-3161 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3161 is a medium-severity vulnerability in IBM Cloud Pak System, published on 19 Oct 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-3161 in the wild and no public exploit code.

Affected product: IBM Cloud Pak System. 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-3161/ (Markdown: https://insights.sbomify.com/CVE-2026-3161/index.md)
```

## Sources

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

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