# CVE-2026-12758: Multiple security vulnerabilities are addressed with IBM Cloud Pak for Business Automation iFixes for August 2026.

> Remote attackers can bypass authorization to invoke restricted endpoints in IBM Cloud Pak for Business Automation due to improper HTTP header validation.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-v72p-h53q-g7f7

## What is CVE-2026-12758?

CVE-2026-12758 is a medium-severity missing authorization vulnerability in IBM Cloud Pak for Business Automation, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Cloud Pak for Business Automation could allow a remote attacker to bypass authorization and invoke restricted endpoints due to improper validation of HTTP headers.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-12758 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12758 is a medium-severity missing authorization vulnerability in IBM Cloud Pak for Business Automation, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12758 in the wild and no public exploit code.

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

## Sources

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

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