# CVE-2026-17203: Auth bypass in Administration Runtime Expert for i

> Remote authenticated attackers can bypass authentication to gain elevated privileges and access sensitive information in IBM Administration Runtime Expert for i.

- **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:** 28 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-w47h-p6px-82qf

## What is CVE-2026-17203?

CVE-2026-17203 is a high-severity authentication bypass vulnerability in IBM Administration Runtime Expert for i, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Administration Runtime Expert for i 1R1M0 could allow a remote authenticated attacker to obtain sensitive information due to improper authentication enforcement.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-17203 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17203 is a high-severity authentication bypass vulnerability in IBM Administration Runtime Expert for i, published on 28 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-17203 in the wild and no public exploit code.

Affected product: IBM Administration Runtime Expert for i. 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-17203/ (Markdown: https://insights.sbomify.com/CVE-2026-17203/index.md)
```

## Sources

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

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