# CVE-2026-17472: Multiple Vulnerabilities in IBM Concert Software

> Remote authenticated attackers can access or modify unauthorized resources due to wildcard RBAC permissions in IBM Concert.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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:** 22 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-vx8r-47x6-wfh9

## What is CVE-2026-17472?

CVE-2026-17472 is a critical missing authorization vulnerability in IBM Concert, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Concert 1.0.0 through 3.0.0 could allow a remote authenticated attacker to access or modify unauthorized resources due to the use of wildcards in RBAC permission definitions.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-17472 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17472 is a critical missing authorization vulnerability in IBM Concert, published on 22 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-17472 in the wild and no public exploit code.

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

## Sources

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

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