# CVE-2026-17262: IBM i is Affected By Denial of Service and Security Restriction Bypass Vulnerabilities in FTP [, ]

> A local attacker can cause a denial of service and bypass security restrictions in IBM i FTP due to improper validation of authentication commands.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-mr8w-j3pv-4wm8

## What is CVE-2026-17262?

CVE-2026-17262 is a medium-severity command injection vulnerability in IBM i, published on 18 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM i 7.6, 7.5, 7.4, and 7.3 could allow a local attacker to cause a denial of service due to improper validation of FTP authentication commands.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-17262 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17262 is a medium-severity command injection vulnerability in IBM i, published on 18 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-17262 in the wild and no public exploit code.

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

## Sources

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

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